Re: Suggestion for handling of boot-time driver options

Keith Owens (kaos@ocs.com.au)
Sun, 14 Dec 1997 09:55:10 +1100


On Sat, 13 Dec 1997 20:17:57 +0100,
Roderich Schupp <rsch@ExperTeam.de> wrote:
>This could be achieved more elegantly (and without cluttering init/main.c
>with entries for every setup function imaginable) with some ELF linking
>magic.
>Any suggestions, objections, flames?

You need to preserve the existing order of entries in main.c *AND* give
users the ability to tweak that order for their own unique
requirements. The existing order is important because the probe code
has to look at some cards before others.

As an example of a unique requirement, I have a box with two SCSI
adaptors, the second is only present to handle external disks which are
not normally present. The scan order has to be tweaked on this box so
the card for the internal disks (ncr53c8xx) is initialised before the
card for the external disks (aha1542). The default scan order does
aha1542 before ncr53cxx so plugging in an external disk creates sda and
changes the names of the internal disks from sda to sdb etc., not nice.

Possibly add an "order" flag to the BOOTSETUP macro and give every
setup code a unique order number. Start in increments of 1,000 to
leave room for future inserts. main.c sorts the entries before running
the setup code in "order". Preserves the existing sequence and users
can change order numbers to suit their own requirements.