I doubt there's many people on this alias that will be able to answer your question with any great detail. I'm no OBP expert but have played around with it at times especially for debugging low-level hardware issues. It's extremely powerful and a lot of people forget that it can be used for much, much more than typing "boot".
As you know, SUN does use OBP on it's SPARC boxes. If you have a SPARC box, anything will do, you can play about with OBP yourself. The "sifting" command is your friend. It allows you to search for OBP commands. You're probably also interested in commands such as "cd", "ls", and ".properties". These will allow you to traverse the OBP device path and interact with the hardware at different levels. The ".properties" will show you parameters and values within the FCode on devices. The OBP Command reference guide can be found here: http://docs.sun.com/source/806-1377-10/index.html and is definitely worth a read. If you want to really understand how OBP ticks and interacts with FCode your best reference is the "Writing FCode 3.x Programs" located here: http://docs.sun.com/source/806-1379-10/index.html There's a sample OBP-FCode Driver example for the HME NIC in chapter 11: http://docs.sun.com/source/806-1379-10/sampldriver.html If you want to understand and interrogate the OBP/FCode/Firmware/OS interaction & behaviour look at OBP/Forth Debug. This blog entry is a good place to start - http://blogs.sun.com/code2blog/entry/obp_debug_1, although there's other documentation out there as well. Hope this helps. -- This message posted from opensolaris.org _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
