Can you describe the PCI FCode PROM Header Format?
PCI FCode PROM Header Format is as follows: ————————————————— a.out header 32 bytes (Needed by some utilities) ————————————————— PCI expansion PROM Header 28 bytes ————————————————— PCI data struct. 24 bytes ————————————————— FCode (8 Byte FCode header + FCode code bytes) ————————————————— The above a.out header is also needed if you want to download your FCode image (e.g. during test/development of your FCode driver you may not want to use a physical PROM) using “dload” or “boot” on a Solaris 1.x (SunOS 4.x) system. In case you are “dload”ing or “boot”ing your FCode image on a Solaris 2.x system, you need to replace the a.out header with an ELF header. The fakeboot utility can add either an a.out or an ELF header, based on parameters you pass to fakeboot. The add_hdr utility can also add either an a.out or an ELF head
Related Questions
- In the past Ive used tokenizer version 2.3 for SBus FCODE development - is it OK to use that same tokenizer for PCI FCode PROM development, or do I need new tokenizer?
- Can you provide device driver software for PCI and CardBus? What kind of software format and which type of OS is supported?
- When the configuration software probes my PCI slot, does it read my PROM 32-bits at a time, or one byte at a time?
