Menu
▾
▴
ps2hacking-devel
|
From: James S. <jsi...@tr...> - 2001-09-16 03:07:58
|
> However I think you must be unaware that you are repeating the work that > other people have done before. > the ps2dev.sourceforge.net site has the fixed unix sources for iop and > ee. they have been there for some time. > > Also the ps...@to... list has been running for over 18 months or > so, i sugest you join up, there are over 400 members so you have more > chance of making progress quicker. Or at least CC it to both lists, > because atm, no one gets this info about your work. I dont think there > are >400 members on ps2hacking yet are there? Yet another group here. Of course they look like they do mostly userland developement. I know this group does kernel developement and some of this code has been intergarted into the SF mips tree and will soon be intergrated into the main mips tree. So it looks like it might be a good idea for both to join forces. BTW is the PS2 dev group working with the default Sony stuff? I know this group is working to improve the crap sony put out. |
|
From: M. R. B. <mr...@0x...> - 2001-09-16 03:43:44
|
* James Simmons <jsi...@tr...> on Sat, Sep 15, 2001: > > Yet another group here. Of course they look like they do mostly userland > developement. I know this group does kernel developement and some of this > code has been intergarted into the SF mips tree and will soon be > intergrated into the main mips tree. So it looks like it might be a good > idea for both to join forces. > Actually I think the ps2dev group is more concerned with homebrew/hobbyist development than Linux development (the name would indicate so), although there are probably those with the ps2linux kit out there as well. At LWE, NIIBE implied that Sony gave their blessing for the "external" 2.4 port, Yaegashi would you care to clarify? > BTW is the PS2 dev group working with the default Sony stuff? I know this > group is working to improve the crap sony put out. Good question, now3d indicated fixed (the sources from SN Systems won't build without modifications) sources at ps2dev.sourceforge.net. I would assume that most ps2dev people are using either the Linux or win32 versions of these tools ...? I'm more concerned with getting the modifications into binutils and gcc mainline (esp. integrated with the flurry of recent Linux/MIPS changes in those tools). Exciting stuff. M. R. |
|
From: now3d <n3...@an...> - 2001-09-16 13:24:58
|
Hello, I have not CC'd this as you are all authorised on ps2dev now, I will answer your questions in one email -------------- Other people are trying to get these sources into the binutils and gcc mainline? If so, then yes, I am repeating someone's else "work", other than that I'm not doing anything to the sources except cleaning them up. If they're in binutils and gcc proper, then they're already build-ready :P. ---- Please continue this work, others have not got the patches integrated in GCC 3 etc, this would be VERY useful if you are successful, its very annoying having to install different binaries when a target of --enable-targets=all would suffice. ------ Right, Cygnus wrote it for GNUPro for Sony. At the top of each Cygnus source file, is a FSF copyright statement, which means the FSF owns the sources. I seriously doubt that the FSF would withhold sources, so it seems to be an issue of Cygnus just not bothering to merge with the FSF binutils and gcc. Hopefully it's that simple, let me know if I'm missing something. -------- This was mentioned once, but as I said, the patches need to be "found", i did not get them when snsys released the source to me. Also it is hard to extract the patches from the GNUPro sources from snsys as there are not sufficient comments. you get the odd mention but not much. mind u there really is not so much different, after dvp etc, its mainly mdmx and other new stuff, and the design changes. --------- > Actually I think the ps2dev group is more concerned with homebrew/hobbyist > development than Linux development (the name would indicate so), although > there are probably those with the ps2linux kit out there as well. At LWE, > NIIBE implied that Sony gave their blessing for the "external" 2.4 port, > Yaegashi would you care to clarify? > > > BTW is the PS2 dev group working with the default Sony stuff? I know this > > group is working to improve the crap sony put out. > > Good question, now3d indicated fixed (the sources from SN Systems won't > build without modifications) sources at ps2dev.sourceforge.net. I would > assume that most ps2dev people are using either the Linux or win32 versions > of these tools ...? I'm more concerned with getting the modifications into > binutils and gcc mainline (esp. integrated with the flurry of recent > Linux/MIPS changes in those tools). Exciting stuff. yes, some people are using normal GNU stuff with no ps2 support, others are using the binaries made from GNUPro on win32 or linux there are other ps2 assembler projects as well. (i have not used these though) now3d ICQ: #11122941 IRC: EFnet #PS2Dev PS2-Anarchists Dev site http://www.anarchists.co.uk/ |
|
From: now3d <n3...@an...> - 2001-10-21 12:49:33
|
"M. R. Brown" wrote: > Good question, now3d indicated fixed (the sources from SN Systems won't > build without modifications) sources at ps2dev.sourceforge.net. I would > assume that most ps2dev people are using either the Linux or win32 versions > of these tools ...? I'm more concerned with getting the modifications into > binutils and gcc mainline (esp. integrated with the flurry of recent > Linux/MIPS changes in those tools). Exciting stuff. > > M. R. There are some custom assemblers around for ps2, but most ppl have moved over to linux/cygnus for using the fixed snsys compiler now now3d |
|
From: now3d <n3...@an...> - 2001-10-21 12:48:42
|
> There doesn't need to be. You can combine the iop and ee/dvp patches into > one binutils and gcc source that you can use to build all toolsets. > AFAICT, you could even use the *same* compiler for the IOP and EE by using > custom gcc specs and options. > > In a few days I'll be asking the binutils and gcc folks why these patches > never made it in and if there is any objection to them being included into > mainline binutils and gcc. But the patches do need to be cleaned up and > rewritten (to an extent) for the current binutils and gcc stock (the > patches are over 2 years old). > > If anyone else (Sony or Cygnus/Redhat) has any other insight into these > tools I'd appreciate hearing them. > > M. R. Did you hear anything from the binutils guys? or sony..? now3d |
|
From: Joseph P. <pa...@mc...> - 2001-09-10 21:59:59
|
Allright!!! I'm able to compile the snsys ee source to produce dvp-as and dvp-gasp binaries that work! I just needed to add a dvp entry in config.sub and configure target=dvp and all works well! Thanks, Joe On Mon, 10 Sep 2001, M. R. Brown wrote: > * Joseph Paris <pa...@mc...> on Mon, Sep 10, 2001: > > > the ee-binutils from snsys, i believe was configured for a win32 build, > > and as such there doesn't seem to be an esy way to configure for linux. > > At least, i'm receiving errors on running configure alone. i.e. > > ./configure generates ./configure: command not found. It is in each > > sepereate directory... > > > > I guess the quick and dirty way to get things done is to do a diff against > stock binutils-2.9.1 and gcc-2.95.2 and the ee/iop custom tools. Then you > simply apply that patch against stock and you should be good to go - except > for the toplevel config.sub. You still have to hand-edit this AFAICS. > Without these modifications, binutils and gcc won't know what the hell a dvp > or iop is :). > > When diff'ing, every directory except gcc belongs to binutils. > > M. R. > > |
|
From: now3d <n3...@an...> - 2001-09-15 06:28:04
|
I sugest you contact su...@sn... for the answer to that one cc: gn...@gn... or they will not reply though now3d "M. R. Brown" wrote: > > * Joseph Paris <pa...@mc...> on Mon, Sep 10, 2001: > > > Great, i'll check that out... Has there been any progress on a unix port > > of the snsys binutils dists? What's the difference between IOP and the > > regular ee? > > > > Why wouldn't binutils and gcc compile normally under Unix? Clarify. > > The IOP stands for "I/O Processor" - it's the same CPU used in the original > PSX and is used in the PS2 for "coordinating" actions between perhiperals, > etc. as well as providing backwards compatibility with the PSX. > > The EE is the MIPS R5900 core and related coprocessors. > > M. R. -- ICQ: #11122941 IRC: EFnet #PS2Dev PS2-Anarchists Dev site http://www.anarchists.co.uk/ |
|
From: M. R. B. <mr...@0x...> - 2001-09-15 20:43:58
|
* now3d <n3...@an...> on Sat, Sep 15, 2001: > I sugest you contact su...@sn... for the answer to that one > cc: gn...@gn... or they will not reply though > Why? Cygnus wrote the code, so they're the only ones worth talking to. SN Systems has never really been useful to hobbyists anyway... The fact that they distribute a busted src/ directory even reinforces that :P. M. R. |
|
From: Joseph P. <pa...@mc...> - 2001-09-06 23:21:42
|
I was wondering if there was an easy way of executing ee-dvp-as on an intel machine. It's the assembler for the vector processing unit. Thanks, Joe |
|
From: now3d <n3...@an...> - 2001-09-07 14:31:39
|
All the PS2 source was kindly provided by su...@sn... its the GNUPro version with r5900 stuff, you can compile it with cgywin on windows or run in linux etc. now3d Joseph Paris wrote: > > I was wondering if there was an easy way of executing ee-dvp-as on an > intel machine. It's the assembler for the vector processing unit. > > Thanks, > Joe > > _______________________________________________ > ps2hacking-devel mailing list > ps2...@li... > https://lists.sourceforge.net/lists/listinfo/ps2hacking-devel -- ICQ: #11122941 IRC: EFnet #PS2Dev PS2-Anarchists Dev site http://www.anarchists.co.uk/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X