Date: Wed, 11 Mar 1998 21:06:28 +0000 From: freebsd@isvara.net To: FreeBSD Hackers <hackers@FreeBSD.ORG> Subject: Re: userconfig data -> linker set -> ELF segment Message-ID: <3506FCD4.7F0A0BD@challenge.isvara.net> References: <199803111011.CAA22528@dingo.cdrom.com> <199803111444.HAA10346@narnia.plutotech.com> <19980311162228.43166@follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Eivind Eklund wrote:
> > Exactly. Don't use a linker set at all. Convert all drivers to
> > LKMs, load they "probe" section of all LKMs, have an entry point
> > in the probe section register the driver with userconfig.
Just an idea I had:
would it not be possible to load a word (or list of words) at a know offset
in the LKM specifying the PCI Vendor ID and PCI Device IDs the device driver is
interested in? That way the OS can handle all the probing is a much faster
manner, and before the drivers load, such that so lurky probe code gets called.
This would seem much more efficient, but [in this simplified model,] would not
handle cases where one device driver could handle multiple Vendor IDs and Device
IDs (which is where lists come in). OK, and also you couldn't execute any other
code in the probe section, as there wouldn't be one (there could be a post-probe
function). There would also have to be a list of device names to match the Device
IDs. This may not be too hard to implement, and IMHO it makes sense (perhaps only
for PCI).
Thanks,
Dan
_____________________________________
Daniel J Blueman
BSc Computation, UMIST, Manchester
Email: blue@challenge.isvara.net
Web: http://www.challenge.isvara.net/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3506FCD4.7F0A0BD>