Kevin Lawton wrote:
> I see in host-linux.c, that the devfs mods I integrated awhile
> ago, call devfs_register/unregister in _addition_ to
> register_chrdev/unregister_chrdev.
>
> Is this correct? Do we need to call both pairs? I would
> think devfs would replace the old chrdev conventions.
No, that's two different things. register_chardev says that
a certain major number is to be associated with this device
driver, while devfs_register says that a certain *name* (i.e.
/dev entry) is to be associated with a major/minor number pair.
You have to have *both* the link name -> major/minor numbers
and the link major number -> device driver for things to work.
The difference between devfs or not is just that the name ->
major/minor link is hardcoded in the file system (without
devfs) or else dynamically created (with devfs). devfs does
not affect the major number -> device driver link in any way.
However, there's convenience functions devfs_register_chrdev
etc. that just do both calls in one ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
[EMAIL PROTECTED]
