forums.ps2dev.org

Thanks ^^;

Yep, exactly, for now, the older gcc should still be used. I'm now looking at gcc's sources in order to produce a patch for it.

Hello, I've end up creating a Work In Progress patch against binutils-2.14 in order to regroup and merge all the previous EE, IOP and DVP patches. The patch is here: http://www.nobis-crew.org/~pixel/binutils-2.14-ps2-20040208-WIP-patch.diff.gz You have to apply it of course on a vanilla binutils-2.1...

Errrr, this is the 3rd possibility I told you before.

Because it requires time :-)

Well, I actually read that about the specs of the DTL-10000, I don't own one ^^; So I do not know the details.

You messed up the iso file as well :-P

Just burn the basic iso, it will work. The gateway won't be necessary for you. And 192.168.0.10 should be enough.

(Anyway, having a gateway != .1 is nasty...)

You mess up things :-) There is actually three ways for the PC and the PS2 to communicate. -) The official sony method, which uses a firewire cable, alvailable only for the official developpers, and is bundled with the whole devkit package -) The official Action Replay method, which uses a PL-2301 U...

Well... depending on the situation of course. But even there, you might find easier to write them by hand. In all cases, I think you'll have more problems about size than anything else. I'm not sure, but, I don't think that compiling 1500 source files into one single monolith elf file would give you...

For "big sized" projects, one could use the automake/autoconf system. But I don't think this suit PS2 projects at all. Yes, do them by hand. It's not that hard :)

Errr....

"make" ? :-)

I think you'd better change the

asm ("j\t%0" : : "i" (0xa0001000));

into:

asm ("li\t$31, %0\njr\t$31" : : "i" (0xa0001000));

Well, it seems to have more sense to me :)

Hum, I just created an account. I'll try to help :)

I'm actually sure that we might get benefits by having "unified" packages, ie, having only two source packages that can build several (ee, iop and dvp) targets. That would mean getting rid of the old "iop-binutils" and "iop-gcc". Especially iop-gcc, since it's based on ...

^^ Well, I think I have to get this as a compliment, thanks :) And of course, I think it's clearly the right thing to do. That's even what I tried to start by creating these debian packages (since all the packages compile and work together) Why not having a wiki somewhere? That would be easier to bu...

Okay, I updated my packages to reflect the following changes: -) fixed a small conflict problem on the two ee-gcc* packages (you could install both) -) added the 4 missing instructions to the ee-binutils -) changed the path /usr/local/ps2 to /usr/local/ps2dev -) backported DVP assembler from the gnu...

The repository is yet not updated actually. I'm working on a "clean" DVP assembler right now. I'll update all the packages right after, changing things like the /usr/local/ps2 into /usr/local/ps2dev etc.

According to their site, it seems so:

http://www.thethirdcreation.net/competitions.php

Mini roundup #22 deadline: February the 6th at 23:59 GMT

I know I don't answer directly to your questions, but those 4 instructions were added lately to the binutils-2.13.2.1's mips r5900 instruction set patch: cfc2.i cfc2.ni ctc2.i ctc2.ni Here is the patch to apply on your binutils's source in order to provide those instructions: http://www.nobis-crew.o...

Well, first, it's binutils you want, not gcc (since you want to produce the ee-dvp-as, not a C compiler for the DVP) And, no, you just can't. The EE patches for binutils-2.13.2.1 does not contain any of the DVP instructions. So, for now, you have to follow the compilation of gas for the dvp using th...

Well, we quite don't have the same policy about file positions in the system tree, but it really doesn't matter actually ;) I just don't have any PS2DEV environment variable, only PS2LIB, and I do not modify the path. Well, you can have a look at the tgz files I just provided so you can see by yours...

Okay, ooPo, here is the ee-binutils's patch: http://www.nobis-crew.org/~pixel/tc-mips.c.diff (I quickly extracted it...) blackdroid: you can find some tgz out of my deb files at http://www.nobis-crew.org/ps2-tgzs but please, just try them, do not spread them right now, as they do not contain the lat...

blackdroid: the patch I'm using right now comes from the http://ps2dev.sf.net website, and it doesn't seem to contain those cfc2.i/ni instructions. I'll upgrade then. Too bad the patches doesn't have version numbers :) I'm actually putting some things into /usr/local/ps2, not /usr/local/ps2dev, sorr...

Err, I had no problem at all with iop-gcc actually ^^; I had some with iop-binutils, which leaded me to patch a bit the provided libiberty, but that's all. It compiled fine using my gcc-3.x. What problem should be there exactly? And I forget to mention: I patched iop-binutils and ee-binutils in orde...

Hello, I'm quite new over PS2 homebrew developpment, and I spent quite a hard time compiling the toolchain for unix. I eventually came up building some debian packages from my work, and I saw somewhere on a thread somebody asking for more binary distributions. Well, I know it's quite not the same, b...