Date: Tue, 20 May 2003 10:20:06 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: freebsd-hackers@freebsd.org Subject: Re: cvs commit: src/release/alpha dokern.sh drivers.conf Message-ID: <20030520.102006.08403290.imp@bsdimp.com> In-Reply-To: <200305201733.43619.doconnor@gsoft.com.au> References: <200305192355.h4JNtx4e076037@khavrinen.lcs.mit.edu> <3EC986C6.5050800@btc.adaptec.com> <200305201733.43619.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200305201733.43619.doconnor@gsoft.com.au>
"Daniel O'Connor" <doconnor@gsoft.com.au> writes:
: Currently I don't see a way of extracting PCI IDs from module source in a
: standard way which means the lists would have to be maintained manually and
: that would _suck_. Perhaps some standard struct array could be used, and if
: it isn't present then you can't do a guess about whether to load the module
: or not, so you just prompt the user.
One of things on my list is to make it possible to have more than just
PCI id's extractable from drivers. It is needed for devd so it can
load the right things when it encounters devices for which there are
no drivers. If the loader wants to do it too, that would be fine, but
the only thing that I can think of that doing it in the loader would
buy you that doing it in devd wouldn't is the ability to kldload the
driver(s) necessary for the root device and not have them hard coded
in your /boot/loader.conf file.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030520.102006.08403290.imp>