After finding out that ps2lib came from reversing irx and elf files from retail games I decided to pop a few into the PC to see what all was there (and to see if I could find some of the elusive leftover debug info).
At length I am seeing some of the info that _may_ have been used to reverse these into the lib source code, but I also keep seeing IOPRPxxx.IMG files along with the mod files.
I noticed some are simply blank (zeros in hex at least) and some ps2dis into libraries like the bios does. I am curious if anyone here has found what they are for and if they pose any use to homebrew coding (like a premade custom img of what you want for the basic modules perhaps? - instead of default ones from bios?).
Im going to keep reading in the old mailing list (Topica list) to see if it was discussed, but I figure I'd ask here too just to be sure there would be a searchable answer on the forum (answer pending of course).
IOPRPxxx.IMG - another whachamahoodlit?
It's an image of iop modules. It's useful for official dev, but no, it's not really any use for homebrew.
Shoot Pixels Not People!
Makeshift Development
Makeshift Development
Well, can't we build a set of new modules that way ? For example, ps2link needs a bunch of irxes. Can't it just reboot the IOP with a custom ioprp image containing only the irxes it need ? Or does the ioprp image have to contain ALL the modules, for example CDVDMAN, MCMAN, etc... ?
pixel: A mischievous magical spirit associated with screen displays. The computer industry has frequently borrowed from mythology. Witness the sprites in computer graphics, the demons in artificial intelligence and the trolls in the marketing department.
You can load more afterwords, but you can't load more before... so It'd have to contain all the dependencies of everything inside of it. We can't distribute the rom irx images so it doesn't do any good.
Shoot Pixels Not People!
Makeshift Development
Makeshift Development