Enrique Zanardi <[EMAIL PROTECTED]> writes: > On Thu, Jun 11, 1998 at 11:45:56AM -0500, Martin Alonso Soto Jacome wrote: > > Dale Scheetz <[EMAIL PROTECTED]> wrote: > > > I have wondered why we didn't try this once the kernel supported initrd. > > > To be honest I haven't figured out yet how to do the device selection, > > > other than going through a list of drivers, trying to insmod each one > > > until you are successful. > > > > Wouldn't PCI and ISA PnP support help here? Standard 2.0.x kernels support > > /proc/pci since a long time, so it should be possible to check the device > > names on /proc/pci against a table in order to load the apropriate modules. > > > > That's what Red Hat does, and what I plan to implement for slink. It > doesn't work for ISA cards though, therefore I plan to implement a method > for manually selecting modules at install time as well (probably a > modified "modconf").
You should boot the FreeBSD install disk once for ideas too. > > It should also be possible to deal with PnP just the same way, > Yes, but we will have to create the "device -> module" table from > scratch, as I don't know of anyone that maintains such a table. The only isapnp devices I know of are audio. Are there any SCSI or enet devices? (If so a table would be necessary as they are discovered.) Digging through INF files in windows 95 would be a start. This is something that should be closely coordinated with the ISApnp utilities. > > although I > don't know what the status of the PnP support in the > kernel is right now. > None AFAIK. PnP devices are configured with user-space tools (pnpdump and > isapnp). There is a kernel patch to initialize them, and I have a patch to GRUB to pass the right magic to the kernel patch, but I don't use it right now. (Not necessary, since my only ISApnp device is not critical to booting.) Steve [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]