Well I searched through all of the usb code, and plugged a few devices in
that I had around here and came up with the following list of drivers and
what devfs mapping they had.
If anyone has any fixes for this list, or if I have left anything out,
please let me know. I want to find all of this information out for the
devfs documentation (and the USB documentation might also benefit too.)
Also, if anyone can answer the questions below, please do.
About the drivers that are listed as 'none'. These devices use USB
major/minor device nodes. Should the USB core code register them with devfs
(somewhere like usb/devicename/{0,1,...} where devicename can be provided
by the usb device driver to the usb core)?
I can make this change if others think it is a good idea.
--------------------------------------------------------------------------
acm.c usb/acm/{0,1,...}
audio.c none (does the audio subsystem handle devfs for it?)
dabusb.c none
dc2xx.c none
dsbr100.c none (video device, does the video subsystem handle devfs?)
evdev.c input/event{0,1,...}
ibmcam.c none (video device, does the video subsystem handle devfs?)
joydev.c input/joy{0,1,...}
keybdev.c unsure
mdc800.c none
mousedev.c input/mouse{0,1,...} and input/mice
ov511.c none (video device, does the video subsystem handle devfs?)
pegasus.c none (network drivers don't use devfs)
plusb.c none (network drivers don't use devfs)
printer.c none
rio500.c none
scanner.c none
usb-storage.c unsure (handled by normal SCSI devfs code?, if so any special names?)
usb-serial.c usb/tts/{0,1,...}
uss720.c none (parallel port, does the pp subsystem handle devfs?)
wacom.c unsure
wmforce.c unsure
--------------------------------------------------------------------------
Thanks,
greg k-h
greg@(kroah|wirex).com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
