Re: devfs - why not ?

[Marek Habersack]

--lkTb+7nhmha7W+c3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

** On Apr 13, Keith Owens scribbled:

> >> No. How do you load a module for /dev/foo117, when /dev/foo117 doesn't
> >> currently exist? The kernel shouldn't have to know about each and every
> >That could be easily resolved by depmod. The modules can (in that situat=
ion
> >would _have_ to) use the MODULE_SUPPORTED_DEVICE doc string. That would
> >state what device(s) they are bound to. Depmod extracts that info and st=
ores
> >it in /lib/modules/<kver>/device.map.
>=20
> Already in progress.  Actually it is a little more complicated than
Why am I always late? :)

> that, depmod will be using MODULE_DEVICE_TABLE and creating
> /lib/modules/`uname -r`/modules_device_table.  We need the vendor and
So it will actually be possible to register a class of devices to one
driver, right?

> device codes, not just the device name.  Expect modutils 2.3.11 this
> weekend.
You mean like the PCI registered codes? Or Linux-specific ones?

marek

--lkTb+7nhmha7W+c3
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjj111kACgkQq3909GIf5uq4EQCfUaX4p3Pee7GrECRifVl71eTr
ausAnA6Rc0R+/qkvxf4NGpdUWSstUild
=Inzr
-----END PGP SIGNATURE-----

--lkTb+7nhmha7W+c3--