On Thu, Apr 04, 2002 at 09:31:55AM +1000, Brad Hards wrote: > Not very orthogonal. Can you explain the rationale for each directory?
Um, didn't the descriptions of the directories help explain that? > What takes precedence? That the driver complies with a (currently defined) > class, or the function that the driver performs? class comes first. Then function. And then it goes into misc/ if it doesn't fit into any of the existing function directories. > 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. You're right, sorry. They should both be in class/ > If the "higher level interface" is important, why doesn't dsbr100 belong with > the video stuff, since it uses V4L as well? Because I messed up :) You're right, it should go into video. Does that help? thanks, greg k-h _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
