On Thu, Mar 30, 2000 at 08:46:16AM -0800, Greg KH wrote:
> The usb-serial driver, when loaded, creates 16 nodes (ttyUSB0 - ttyUSB15)
> in the main devfs directory. Namespace question: Is this the proper place
> to put them? There isn't a usb subdirectory yet, and I don't think we
> really need one (the input patches of Vojtech put the input devices in the
> root devfs directory.)
No, my input drivers put them in an /dev/input/ subdirectory.
> And there's the issue that the usb-serial driver creates these nodes _when
> the driver is loaded_ not when the device is plugged in. I had been looking
> at changing this for a while now (only registering the node with the tty
> layer when a device is actually found), but had not seen a good reason to.
> Now it looks like this is necessary. Does anyone else think that this
> should be changed? (if so, I suppose the acm driver should also be
> changed.) That way, the ttyUSB?? nodes would only show up when a device was
> found, and only those nodes that were actually connected would show up
> (which I thought was the reason for devfs in the first place.)
>
> And since the tty layer already does devfs_register_chrdev, why should the
> individual serial driver also have to do a tty_register_devfs? (only a very
> few serial drivers actually call tty_register_devfs: console, pty, and
> serial)
Yes, I'm considering updating acm to use devfs as well, but it's getting
weird together with the tty layer. If I find a nice solution, I'll do
it. The same is valid for the devices on the USB major ...
--
Vojtech Pavlik
SuSE Labs
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
