@tnt: Good point. Only problem is to determine what basic functions would be needed, as RR ROM tools could be used for anything. I'm thinking of a system that allows for "plugging in" both programs and system-extensions.
The plug-in system would typically be a command line tool to be run on Windows or Unix that patches a "base-line" ROM to aquire a Kernel hook on start-up for listening to key-strokes for instance (i.e a "wedge"). The patcher creates a list in ROM of the selected plug-ins/programs and their addresses. This list will be parsed and used by the wedge.
A plug-in could be either a program or a system-extension. A system-extension is a package of subroutines (BIOS/whatever) so there must be a way to determine this. A program that requires a specific system-extension should be able to call a ROM function to verify if that plug-in is "installed" and has the right version, as well as getting the address of the plug-in in ROM. If the plug-in is a program, then just copy and execute it.
This combines the functionality of a "program flasher" as well as easily providing new system functions.
A future example of usage could be for instance a MMC64 user patching his RR-ROM to contain a MMC64-BIOS extension and since the user is a musician he has also put a few of his favorite music editors as ROM plug-ins.
Another user don't have a MMC64 but a RR-Net so apart from adding GuruTerm to his ROM, he's also included the fresh new GuruNet(tm) network stack plug-in to be used by the new IRC client he's coding on.
Well.. the idea is simple but allows for 100% modularity (?) and is fairly simple to implement I believe. What do you think?