Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
dev:devmanual [2006/07/16 09:44] stockholm |
dev:devmanual [2006/07/16 09:45] stockholm |
||
|---|---|---|---|
| Line 273: | Line 273: | ||
| ==== Rom naming rules ==== | ==== Rom naming rules ==== | ||
| + | Currently there is no official rom naming convention in etherboot. Use some descriptive name, but note that two ore more consecutive hyphens (like in "''my--rom''") are not allowed, since "--" is the delimiter sign for multiple-driver-roms. Sometimes it is difficult to find a sensible name, for example for "NICs" that are built in motherboard chipsets or if you don't know the model name. In this case we choose to name the corresponding roms "driver-deviceid", like "eepro100-1035". Of course you have to make sure that your rom name is unique in etherboot. | ||
| + | |||
| ==== Booting the code from a floppy ==== | ==== Booting the code from a floppy ==== | ||
| + | Use the rule for ''bin/driver.fd0'' to write another instance of the driver to the floppy for testing. Use lots of printf statements to track where execution has reached and to display the status of various variables and registers in the code. You should expect to do this dance with the development machine, floppy disk and target machine many many times. | ||
| + | |||
| ==== Booting the test code with another EtherBoot ROM ==== | ==== Booting the test code with another EtherBoot ROM ==== | ||
| ==== Writing the code ==== | ==== Writing the code ==== | ||
