** 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 situation
> >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 stores
> >it in /lib/modules/<kver>/device.map.
>
> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:21 EST