Menu
▾
▴
ps2hacking-devel — Share information on the development
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(13) |
Aug
(17) |
Sep
(29) |
Oct
(9) |
Nov
(1) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(57) |
Feb
(15) |
Mar
(4) |
Apr
(1) |
May
|
Jun
(10) |
Jul
(4) |
Aug
(8) |
Sep
(5) |
Oct
(6) |
Nov
(3) |
Dec
(13) |
| 2003 |
Jan
(17) |
Feb
(12) |
Mar
(30) |
Apr
(31) |
May
(48) |
Jun
(51) |
Jul
(91) |
Aug
(42) |
Sep
(20) |
Oct
(32) |
Nov
(76) |
Dec
(97) |
| 2004 |
Jan
(85) |
Feb
(92) |
Mar
(104) |
Apr
(91) |
May
(104) |
Jun
(45) |
Jul
(46) |
Aug
(17) |
Sep
(7) |
Oct
(17) |
Nov
(38) |
Dec
(37) |
| 2005 |
Jan
(3) |
Feb
(8) |
Mar
(6) |
Apr
(3) |
May
(2) |
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(5) |
Oct
(8) |
Nov
(5) |
Dec
(1) |
| 2006 |
Jan
(8) |
Feb
(12) |
Mar
(27) |
Apr
(8) |
May
(10) |
Jun
(18) |
Jul
(8) |
Aug
(12) |
Sep
(3) |
Oct
(29) |
Nov
(23) |
Dec
(15) |
| 2007 |
Jan
(43) |
Feb
(33) |
Mar
(11) |
Apr
(9) |
May
(12) |
Jun
(21) |
Jul
(10) |
Aug
(7) |
Sep
(8) |
Oct
|
Nov
(3) |
Dec
(2) |
| 2008 |
Jan
|
Feb
(2) |
Mar
(4) |
Apr
(2) |
May
(5) |
Jun
(1) |
Jul
(13) |
Aug
(4) |
Sep
(10) |
Oct
(7) |
Nov
(23) |
Dec
(36) |
| 2009 |
Jan
(40) |
Feb
(25) |
Mar
(43) |
Apr
(44) |
May
(121) |
Jun
(94) |
Jul
(69) |
Aug
(32) |
Sep
(24) |
Oct
(42) |
Nov
(5) |
Dec
(13) |
| 2010 |
Jan
(7) |
Feb
(6) |
Mar
(41) |
Apr
(56) |
May
(66) |
Jun
(67) |
Jul
(50) |
Aug
(48) |
Sep
(13) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: now3d <n3...@an...> - 2001-10-21 12:19:22
|
<ps2...@li...> is one thats in english now3d ICQ: #11122941 IRC: EFnet #PS2Dev PS2-Anarchists Dev site http://www.anarchists.co.uk/ |
|
From: GOTO M. <go...@de...> - 2001-10-13 08:57:06
|
Hi,
I'm trying to make pure-debian chroot environment on ps2,
and got and extracted many packages from debian project archives.
It seems that binaries work fine, static library is ok.
But, only shared binaries do not work!
Below is the example of this situation.
I got packages:
`lv' (text viewer binary. You can find same
original ps2 package in /usr/bin/lv),
`libncurses' (it has /lib/libncurses.so.5.0),
`libncurses-dev' (it has /usr/lib/libncurses.a).
lv depends on libncurses (> 4.0) and libc.
I extracted lv in tmpdir, it required /lib/libncurses.5.0
and complained/exited (because debian's lv was compiled under with
libncurses.5.0 but original ps2 environment has only libncurses.4.0).
Then I extracted libncurses.5.0 into appropriate dir, but
lv did not work. Why? I used ldd and then got the result:
> ldd debian_libncurses.5.0.so
not a dynamic executable
??? Kondara PS2 original ldd and libc couldnot understand
it was shared library or not... Then I used readelf for both
PS2 original libncurses.so and debian's libncurses.so.
and found that the internal addresses of PS2 original share library
are very curious!
> readelf -a debian_libncurses.5.0.so
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Type: DYN (Shared object file)
Machine: MIPS R3000 big-endian
Version: 0x1
Data: ELFDATA2LSB (little endian)
*GOOD, Entry point address: 0x5180
but not Start of program headers: 52 (bytes into file)
work!* Start of section headers: 325296 (bytes into file)
Flags: 0x3, noreorder, pic, mips1
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 4
Size of section headers: 40 (bytes)
Number of section headers: 21
Section header string table index: 20
Section Headers:
[Nr] Name Type Addr Off Size ES Flg Lk Inf Al
[ 0] NULL 00000000 000000 000000 00 0 0 0
[ 1] .reginfo MIPS_REGINFO 000000b4 0000b4 000018 18 A 0 0 4
[ 2] .dynamic DYNAMIC 000000cc 0000cc 0000c8 08 A 5 0 4
[ 3] .hash HASH 00000194 000194 001110 04 A 4 0 4
[ 4] .dynsym DYNSYM 000012a4 0012a4 002390 10 A 5 16 4
[ 5] .dynstr STRTAB 00003634 003634 00161e 00 A 0 0 1
[ 6] .gnu.version VERSYM 00004c52 004c52 000472 02 A 4 0 2
[ 7] .gnu.version_r VERNEED 000050c4 0050c4 000030 00 A 5 1 4
[ 8] .init PROGBITS 000050f4 0050f4 00008c 00 AX 0 0 4
[ 9] .text PROGBITS 00005180 005180 033730 00 AX 0 0 16
[10] .fini PROGBITS 000388b0 0388b0 00004c 00 AX 0 0 4
[11] .rodata PROGBITS 00038900 038900 0075d0 00 A 0 0 16
[12] .rel.dyn REL 0003fed0 03fed0 007788 08 A 4 0 16
[13] .data PROGBITS 00087660 047660 007ac0 00 WA 0 0 16
[14] .eh_frame PROGBITS 0008f120 04f120 000004 00 WA 0 0 4
[15] .ctors PROGBITS 0008f124 04f124 000008 00 WA 0 0 4
[16] .dtors PROGBITS 0008f12c 04f12c 000008 00 WA 0 0 4
[17] .got PROGBITS 0008f140 04f140 0004bc 04 WA 0 0 16
[18] .sbss NOBITS 0008f5fc 04f5fc 000000 00 WA 0 0 1
[19] .bss NOBITS 0008f600 04f600 002d80 00 WA 0 0 16
[20] .shstrtab STRTAB 00000000 04f600 0000b0 00 0 0 1
[snip...]
> readelf -a ps2_original_libncurses.4.2.so
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Type: DYN (Shared object file)
Machine: MIPS R3000 big-endian
Version: 0x1
Data: ELFDATA2LSB (little endian)
*Broken, Entry point address: 0x5ffe5590
however Start of program headers: 52 (bytes into file)
work!* Start of section headers: 386888 (bytes into file)
Flags: 0x20920003, noreorder, pic, mips3
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 5
Size of section headers: 40 (bytes)
Number of section headers: 23
Section header string table index: 22
Section Headers:
[Nr] Name Type Addr Off Size ES Flg Lk Inf Al
[ 0] NULL 00000000 000000 000000 00 0 0 0
*Broken!* [ 1] .reginfo MIPS_REGINFO 5ffe0100 000100 000018 18 A 0 0 16
[ 2] .dynamic DYNAMIC 5ffe0120 000120 0000e0 08 A 5 0 16
[ 3] .hash HASH 5ffe0200 000200 00118c 00 A 4 0 16
[ 4] .dynsym DYNSYM 5ffe1390 001390 002580 10 A 5 17 16
[ 5] .dynstr STRTAB 5ffe3910 003910 001730 00 A 0 0 16
[ 6] .gnu.version VERSYM 5ffe5040 005040 0004b0 02 A 4 0 2
[ 7] .gnu.version_r VERNEED 5ffe54f0 0054f0 000030 00 A 5 1 4
[ 8] .init PROGBITS 5ffe5520 005520 000064 00 AX 0 0 8
[ 9] .text PROGBITS 5ffe5590 005590 02d7a0 00 AX 0 0 16
[10] .fini PROGBITS 60012d30 032d30 000058 00 AX 0 0 8
[11] .rodata PROGBITS 60012d90 032d90 0075c0 00 A 0 0 16
[12] .rel.dyn REL 6001a350 03a350 007780 08 A 4 0 16
[13] .data PROGBITS 60061ad0 041ad0 007ac0 00 WA 0 0 16
[14] .eh_frame PROGBITS 60069590 049590 000004 00 WA 0 0 4
[15] .ctors PROGBITS 60069594 049594 000008 00 WA 0 0 4
[16] .dtors PROGBITS 6006959c 04959c 000008 00 WA 0 0 4
[17] .got PROGBITS 600695b0 0495b0 000928 04 WA 0 0 16
[18] .sbss NOBITS 60069ed8 049ed8 000000 00 WA 0 0 1
[19] .bss NOBITS 60069ee0 049ee0 002d30 00 WA 0 0 16
[20] .compact_rel PROGBITS 6006cc10 049ee4 00d20c 00 0 0 4
[21] .rtproc PROGBITS 00000000 0570f0 007590 00 0 0 16
[22] .shstrtab STRTAB 00000000 05e680 0000c5 00 0 0 1
[snip]...
You can find easily that ps2 shared library entry point indicates bad
address "0x5ffe5590". Normally this address should be such a debian's
address "0x5180". This problem has occured on only shared libraries.
Elf binaries and static binaries are ok.
I investigated shared libraries with readelf on other architectures
like intel, sparc64, parisc, ..., but their entry point address never
started such a large address "0x5ffe5590". It means that current
shared libraries on original ps2linux have and run with *BAD
ADDRESS*. I recompiled libncurses.5.0.so, but it had also bad address
(and worked fine)... so I think it's toolchain problem, moreover
ps2linux loader/kernel/libc is designed with this bad address!
Do you know some information about it? I want to fix it (because of
keeping binary compatibility between other mips little endian
architectures). Any comments are welcomed.
-- gotom
|
|
From: bugo <bu...@or...> - 2001-10-09 19:23:50
|
Hi, Im curious to know if there are any developers in the US porting netbsd to the ps2. If so, what target setup is being used? Are there any other methods of interfacing with the US ps2 other than having a Japanese PS2 console? Thanks, NN |
|
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: 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: 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-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: M. R. B. <mr...@0x...> - 2001-09-15 20:40:35
|
* now3d <n3...@an...> on Sat, Sep 15, 2001: > Hello > It seems you are making good progress with the GNUPro sources released > by snsys. > > 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. > 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. > 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? > Thanks for the info. > On the subject of including the GNUPro patches for r5900, iop, dvp etc I > believe it is an issue of owner permission. eg they wrote it for GNUPro, > so the normal GNU tool chain may require the authorisation of the > origional author. I sugest you ask about this. (apparently all GNUPro > advancements get added into normal GNU after a while, but this has not > happened with ps2 specific stuff yet) > 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. > i sugest you email bin...@so... and enquire there. > I will as soon as I have more time to work on this. M. R. |
|
From: Alex R. <al...@sp...> - 2001-09-15 08:12:29
|
For whatever reason, GNOME seems to draw things incorrectly. For example, window titles are missing. Any ideas? +------------------------------------------------------------+ | Alexander M. Rosenberg <mailto:alexr@_spies.com> | | Nobody cares what I say. Remove the underscore to mail me. | |
|
From: now3d <n3...@an...> - 2001-09-15 06:28:09
|
Hello It seems you are making good progress with the GNUPro sources released by snsys. 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? On the subject of including the GNUPro patches for r5900, iop, dvp etc I believe it is an issue of owner permission. eg they wrote it for GNUPro, so the normal GNU tool chain may require the authorisation of the origional author. I sugest you ask about this. (apparently all GNUPro advancements get added into normal GNU after a while, but this has not happened with ps2 specific stuff yet) i sugest you email bin...@so... and enquire there. now3d for info on subscribing to ps2dev look on our site below "M. R. Brown" wrote: > > * Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > > > I put together a ps2-dvp-binutils package that one should be able to do a > > ./configure --target=dvp and have it produce the correct binutils... The > > build process may be a bit twichty, but i think i've resolved most of > > those problems.... This is built off the snsys ee-binutils source. If > > there is a need for it, i can send it. > > > > Can someone help explain why there needs to be so many different sets of > > binutils for ps2 dev? Is there a reasonable way to start combining these? > > > > 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. -- ICQ: #11122941 IRC: EFnet #PS2Dev PS2-Anarchists Dev site http://www.anarchists.co.uk/ |
|
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: Joseph P. <pa...@mc...> - 2001-09-11 20:46:19
|
Right, could you send the patches then? I can't find them on the website. Or do i need to generate my own? I don't see them in either the dists or on the website. --Joe On Tue, 11 Sep 2001, M. R. Brown wrote: > * Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > > > Are the patch files built and ready to go? Or do they still have to be > > generated off what we have now? > > > > Um, did you read my last post? I've included it here just in case. > > M. R. > > > --Joe > > > > On Tue, 11 Sep 2001, M. R. Brown wrote: > > > > > * Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > > > > > > > I put together a ps2-dvp-binutils package that one should be able to do a > > > > ./configure --target=dvp and have it produce the correct binutils... The > > > > build process may be a bit twichty, but i think i've resolved most of > > > > those problems.... This is built off the snsys ee-binutils source. If > > > > there is a need for it, i can send it. > > > > > > > > Can someone help explain why there needs to be so many different sets of > > > > binutils for ps2 dev? Is there a reasonable way to start combining these? > > > > > > > > > > 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. > > > > > > > > |
|
From: M. R. B. <mr...@0x...> - 2001-09-11 20:39:40
|
* Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > Are the patch files built and ready to go? Or do they still have to be > generated off what we have now? > Um, did you read my last post? I've included it here just in case. M. R. > --Joe > > On Tue, 11 Sep 2001, M. R. Brown wrote: > > > * Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > > > > > I put together a ps2-dvp-binutils package that one should be able to do a > > > ./configure --target=dvp and have it produce the correct binutils... The > > > build process may be a bit twichty, but i think i've resolved most of > > > those problems.... This is built off the snsys ee-binutils source. If > > > there is a need for it, i can send it. > > > > > > Can someone help explain why there needs to be so many different sets of > > > binutils for ps2 dev? Is there a reasonable way to start combining these? > > > > > > > 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. > > > > |
|
From: Joseph P. <pa...@mc...> - 2001-09-11 20:31:25
|
Are the patch files built and ready to go? Or do they still have to be generated off what we have now? --Joe On Tue, 11 Sep 2001, M. R. Brown wrote: > * Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > > > I put together a ps2-dvp-binutils package that one should be able to do a > > ./configure --target=dvp and have it produce the correct binutils... The > > build process may be a bit twichty, but i think i've resolved most of > > those problems.... This is built off the snsys ee-binutils source. If > > there is a need for it, i can send it. > > > > Can someone help explain why there needs to be so many different sets of > > binutils for ps2 dev? Is there a reasonable way to start combining these? > > > > 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. > > |
|
From: M. R. B. <mr...@0x...> - 2001-09-11 20:26:10
|
* Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > I put together a ps2-dvp-binutils package that one should be able to do a > ./configure --target=dvp and have it produce the correct binutils... The > build process may be a bit twichty, but i think i've resolved most of > those problems.... This is built off the snsys ee-binutils source. If > there is a need for it, i can send it. > > Can someone help explain why there needs to be so many different sets of > binutils for ps2 dev? Is there a reasonable way to start combining these? > 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. |
|
From: Joseph P. <pa...@mc...> - 2001-09-11 20:01:52
|
I put together a ps2-dvp-binutils package that one should be able to do a ./configure --target=dvp and have it produce the correct binutils... The build process may be a bit twichty, but i think i've resolved most of those problems.... This is built off the snsys ee-binutils source. If there is a need for it, i can send it. Can someone help explain why there needs to be so many different sets of binutils for ps2 dev? Is there a reasonable way to start combining these? --Joe On Mon, 10 Sep 2001, M. R. Brown wrote: > * Joseph Paris <pa...@mc...> on Mon, Sep 10, 2001: > > > I think i hit a pretty frustrating part. I compiled the snsys ee-binutils > > code under linux which produced the as,gasp,ld,etc... I still can't > > compile vpu asm files... I configured with --target=mipsel-scei-elfl, > > which i thought was what the iop was doing... Is this way off base? > > > > Yes. > > The iop tools should be compiled with "mipsel-scei-elfl", the ee tools > should be compiled with mipselr5900 or similar. > > How did you compile the tools .. can you supply configure/make lines > please? > > M. R. > > |
|
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: M. R. B. <mr...@0x...> - 2001-09-10 21:58:55
|
* Joseph Paris <pa...@mc...> on Mon, Sep 10, 2001: > I think i hit a pretty frustrating part. I compiled the snsys ee-binutils > code under linux which produced the as,gasp,ld,etc... I still can't > compile vpu asm files... I configured with --target=mipsel-scei-elfl, > which i thought was what the iop was doing... Is this way off base? > Yes. The iop tools should be compiled with "mipsel-scei-elfl", the ee tools should be compiled with mipselr5900 or similar. How did you compile the tools .. can you supply configure/make lines please? M. R. |
|
From: Joseph P. <pa...@mc...> - 2001-09-10 21:32:23
|
I think i hit a pretty frustrating part. I compiled the snsys ee-binutils code under linux which produced the as,gasp,ld,etc... I still can't compile vpu asm files... I configured with --target=mipsel-scei-elfl, which i thought was what the iop was doing... Is this way off base? 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: M. R. B. <mr...@0x...> - 2001-09-10 20:43:29
|
* 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: M. R. B. <mr...@0x...> - 2001-09-10 20:25:41
|
* 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... > Notice that the zip archives are in DOS CR/LF format. Use `unzip -a' to convert those files into the format that bash expects. Then `chmod +x' the configure scripts, and anything else bash bitches about. You may also want to make all files writeable as well. You still won't have much luck as there are key files missing in the toplevel directory. You'll have to copy those files from a binutils-2.9.1 and gcc-2.95.2 archive, just pay attention to the files that the individual configure's complain about. You'll also have to edit config.sub (once you copy it) and add the mipsel*r5900 and dvp entries so that your --target string will be properly recognized. Confused yet? Good. I'm going through this now to see what's all missing. But hey - at least now you know how to generate the ubiquitous "mpg" assembly instruction, eh? Have fun, M. R. |
|
From: Joseph P. <pa...@mc...> - 2001-09-10 19:05:48
|
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... Thanks, Joe On Mon, 10 Sep 2001, 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. > > |
|
From: M. R. B. <mr...@0x...> - 2001-09-10 18:15:44
|
* 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. |
|
From: Joseph P. <pa...@mc...> - 2001-09-10 17:04:48
|
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? Thanks, Joe On Sun, 9 Sep 2001, now3d wrote: > check ps2dev logs, this topic was discused approx 12months ago in > detail. > there are over 400 members, so more stuff gets mentioned. > see links below > > Joseph Paris wrote: > > > > What is AR2? Which cd-burning program did you use? A linux one, or a > > windows one? > > > > Thanks, > > Joe > > > > > ICQ: #11122941 IRC: EFnet #PS2Dev > PS2-Anarchists Dev site > http://www.anarchists.co.uk/ > > |
|
From: now3d <n3...@an...> - 2001-09-09 12:26:58
|
check ps2dev logs, this topic was discused approx 12months ago in detail. there are over 400 members, so more stuff gets mentioned. see links below Joseph Paris wrote: > > What is AR2? Which cd-burning program did you use? A linux one, or a > windows one? > > Thanks, > Joe > ICQ: #11122941 IRC: EFnet #PS2Dev PS2-Anarchists Dev site http://www.anarchists.co.uk/ |
1662 messages has been excluded from this view by a project administrator.
