--8t9RHnE3ZwKMSgU+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Dec 28, 2003 at 05:59:29PM -0500, Perry E. Metzger wrote:
>=20
> True enough, but imagine someday we'd like to load drivers at run time
> based on the IDs. For that, we can't leave all the information in the
> driver itself because then we'd have to load and unload every driver
> we have...

This is getting a bit off-topic (of the original thread).

For LKMs, I can envision one of two solutions.

1) Each LKM includes some sort of info (PCI IDs, etc.) indicating what the=
=20
driver (may) support. So if we find unconfigured PCI IDs, we know what=20
LKMs to try.

2) We compile in "Module" support, which would be a stub driver that=20
matches, then on attach calls out for the right driver to be loaded.

So you're right, we don't want to try _every_ driver. But we can figure=20
out how not to. :-)

Take care,

Bill

--8t9RHnE3ZwKMSgU+
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQE/8edOWz+3JHUci9cRAippAJ49oGIOTrsZP17FV/AEaTHf1E+GXwCcCY64
BXr5vVmJWJ39/gFjU2w5Yg0=
=9mnk
-----END PGP SIGNATURE-----

--8t9RHnE3ZwKMSgU+--