On Wed, 3 Apr 2002 15:09, Greg KH wrote: > Hi all, <snip> > drivers/usb will have the following subdirectories: > class/ all USB class drivers <snip> > net/ all USB network drivers <snip> > class: > acm.c audio.h hid-core.c hiddev.c hid-input.c usbkbd.c > audio.c bluetooth.c hid-debug.h hid.h printer.c usbmouse.c <snip> > misc: > auerswald.c dabusb.h emi26.c rio500.c tiglusb.h > dabfirmware.h dc2xx.c emi26_fw.h rio500_usb.h uss720.c > dabusb.c dsbr100.c mdc800.c tiglusb.c wacom.c > > net: > catc.c CDCEther.h kawethfw.h pegasus.h usbnet.c > CDCEther.c kaweth.c pegasus.c rtl8150.c <snip> > So, how does this look? Not very orthogonal. Can you explain the rationale for each directory?
What takes precedence? That the driver complies with a (currently defined) class, or the function that the driver performs? acm.c and CDCEther (that probably should be cdc-acm.c and cdc-ether.c if there is going to be a grand renaming patch :) are both basically networking drivers (although they don't both interface to the networking system), both comply with the same spec, and don't live in the same directory. If the "higher level interface" is important, why doesn't dsbr100 belong with the video stuff, since it uses V4L as well? Brad _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
