Date: Mon, 07 Dec 1998 23:09:03 -0800 From: Mike Smith <mike@smith.net.au> To: "Matthew N. Dodd" <winter@jurai.net> Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG Subject: Re: KLD - what's the idea? Message-ID: <199812080709.XAA00791@dingo.cdrom.com> In-Reply-To: Your message of "Mon, 07 Dec 1998 00:46:20 EST." <Pine.BSF.4.02.9812070045000.17054-100000@sasami.jurai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > I was kind of wondering how to avoid compiling in 20 to 60 Kb of firmware > > > image for support of RAM based TMS380 cards. In addition, some each > > > particular card may have specific firmware it wants loaded. I'm looking > > > for some way to load a really basic config file to let the driver know > > > which image goes with which card. > > > > > > Doing this from userland isn't good as I can't do much with the card until > > > the firmware is loaded. > > > > Are these PnP devices, ie. can you differentiate between them before > > running the probe? Are they ever likely to be critical to the boot > > process? > > ISA/ISA-PnP/EISA/PCI bards. The driver/firmware for the non-PnP ISA card will have to be loaded manually. Assuming that the PnP information for the other cards is enough to determine which firmware should be loaded for them, they should all be achievable with no user intervention. > How critical to the boot process are network cards? In the case of eg. network installs, or diskless booting, critical. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812080709.XAA00791>