forums.ps2dev.org

Folks; After reading these posts about DHCP I was greatly concerned. I've been revving our stack up to PS2IP and had worked my way down the the last item-- DHCP. However, all is fine. But you DO need to recompile ps2ip, ps2ip2, and smap, and your apps of course if they touch netif. This is because o...

Understood, I think you missed the point of having multiple IOP threads-- in effect multiple servers, one for each EE thread. A "simple lock" will defeat the usefulness of blocking recv*, accept and select calls thus forcing the application to do all the work to simulate multi-threading an...

I suspect we have a race condition in the usage of the static rpc buffers. Imagine two threads, both calling send. The first gets all the way through the code into sif, sends the request and blocks on the semaphore waiting for the rpc reply. Because its blocks, the second charges through a similar c...

perhaps, but the code in CVS says otherwise ;-) An excerp from ps2ips.c in send/sendto etc... ee_pos = pkt->ee_addr + pkt->malign; sendlen = MIN(BUFF_SIZE, pkt->length); r = SifRpcGetOtherData(&rdata, ee_pos, lwip_buffer + 16, sendlen - pkt->malign, 0); The SifRPC...

Folks;

I believe that the src/imports.lst file needs to move the import entry of I_sceSifGetOtherData from sifman to sifcmd (where it lives). I have no idea how send/recv from the EE to the IOP ever worked without this...

tjd

On the IOP, with GCC3.2.2 I've encountered [recently-- like last week] a set of strangeness related to -O2. When I backed off to -O0, the code worked as expected. -O1 didn't work either. Basically, the address of variables seemed to get lost. I'm suspecting a register allocation problem (or perhaps ...

Well, thanks. But objcopy to a raw file and zip/unzip works nicely too ;-)

yes, -S is what my fingers should have typed... It's been a long night. But we all digress. My point a while back is that an IRX produced from "gcc -s ..." and "strip ..." do not appear to create the same file. The results of the "strip" are garbage. (all this from gcc-...

yes gcc -s and gcc -Wl,-s are "supposed" to be different. Indeed, when you wsant to look at the assembler code, gcc -s foo.c is a good thing. But (isn't there always one?). 'Splain this: [broadq@mcv-1-1-1 poweroff]$ make ps2-gcc -o poweroff.irx -s -G0 -g -miop -nostdlib -no...

strip -s -S

yeah, but it doesn't work with gcc-3.2.2 (loads of error messages and the resulting file is trash), but -s does work with gcc/g++/ld... Go figure.

On the IOP, I found it easiest to install a new handler using excepman. If you don't have the library stub, I can post it. The call is: RegisterDefaultExceptionHandler(your-trap-handler); It's better to do this than install you own handler since the basic IOP has to keep running and I'd rather be ab...

-s in a link strips all the symbols, not just the debug info. This may be what you want, but renders an "nm" quite useless and makes debugging harder. You might also ensure that you don't use -g. Failing that, if you run a "size -Ax" and see all those tasty "debug_*" se...

Venerable Toolchain Gods: Environment: gcc-3.2.2 + binutils 2.14 Simple program on the IOP. After linking, the addresses in the symbol table for everything in the .data section are wrong (they appear to be off by a factor of two-- double relocations?). Needless to say, this makes debugging hard[er] ...

Hmm, not sure what you meant by TLB-protected. My recollection is that every exception on a Mips processor is routed through a single vector located at 0x80000080. I'm assuming that the low-low-low level code in the PS2 gets control and simply looks up to see if the "user" has set up a han...

Does anyone have any idea why you can use SetVCommonHandler for things like breakpoints, but it doesn't seem to work for exceptions like bad addresses, FPE etc.? I looked at the code in ps2gdb and it's pretty similar to mine. If I execute a breakpoint, my handler gets called. If I reference a bad ad...

Haven't used mcopen in this instance-- can't easily because of the nature of the code (higher layers don't know where the file may reside so they just issue an open...).

As for XMCMAN, where does one get one (the IRXs I mean).

Is it just me, or do others get wierd results sometimes when reading (::read, ::fioRead etc.) from files on a MC. The opens always seem to work, but some files just return 0 bytes on a read (although the directory has the correct length).

I'm using MCMAN if that makes any difference...

Before you guys go too far and take the entire car and engine apart, scattering the parts all over the garage floor, all the time hoping you can build an old DeSoto out of it.... It ain't all that broke is it? I scribbled some assembler to fix my calling conventions problem, fixed some broken protot...

Folks; Any good reason for O_RDONLY being 1 in PS2LIB-2.1 and 0 in newlib(1.11.0)? This causes some confusion for us poor filoe system driver writers. And another thing, the prototype on the IOP side for lseek (api and driver call) is wrong. The offset is typed as an unsigned long. (huh, how do nega...

Well, that's depressing... Is there a list of things that "don't work as intended"? At the moment, a fairly large piece of IOP code is running and I want to continue with 3.2.2 unless its hopeless. I can easily bridge around the function call problem by wriiting a bit of assembler, but if ...

Folks; In updating our stuff from compiled with 2.9xxx to 3.2.2, I've noticed that the function calling conventions are different. This affects any functions taking more than 4 arguments (sprintf anyone?) or lots of the USB functions. Old compiler stuffed args into $4-$7 then on the stack. The new o...

All that you need is there in usbd.irx. Its fairly straightforward to add functionality to provide generic SCSI/SFF support. We've got memory sticks, cards, flash drives, Apple iPods, ordinary USB mass storage devices etc. all running in our media player product. [quote="ole"]Well I though...

All that you need is there in usbd.irx. Its fairly straightforward to add functionality to provide generic SCSI/SFF support. We've got memory sticks, cards, flash drives, Apple iPods, ordinary USB mass storage devices etc. all running in our media player product. [quote="ole"]Well I though...