On Fri, Apr 05, 2002 at 09:52:37AM +0200, Oliver Neukum wrote:
>
> > > Also, the class/input (if used) should be class/hid (because hiddev is
> > > not an input mechanism). Does wacom.c go in here (almost HID:)
> >
> > class/hid/ should be used. And no, I don't think wacom.c should go into
> > there, as it is not a HID driver. It should stay in the misc/ directory
> > until there gets to be enough input drivers and then they could move to
> > a input/ directory.
>
> Actually that defeats the purpose.
> Differentiating class and nonclass drivers is a good criterion as
> long as it does not interfere with things that matter to the programmer.
>
> In terms of code we care about relationships in drivers.
> The most basic similarity is the kernel API used.
>
> Eg. printer is a class driver as is storage. Their relatedness is zero.
> Their closest relatives would be say auersbach respectively hpusbscsi.
> If things that eg use the input layer (hid,wacom,iforce) are split in
> three directories the reorganisation hinders the coders.
>
> Furthermore subsubsystem deserve their own directories.
> serial and storage deserve their own directories independent of class.
> As do input, net and media. Actually scanner as a directory has little
> use, as there's little internal relationship. You'd be better of putting
> them into misc.
Argh, I'm not a librarian, I'm a programmer. There are a zillion
different ways these files can be split up. I just chose one :)
Can people take a look at:
bk://linuxusb.bkbits.net/dir_move-2.5/
and see if you like what's there?
It's based off of Linus's tree, not the usb-2.5 tree, as it has to
eventually get pushed to him, and I didn't feel like doing this twice.
I'll add a README tomorrow, it's late, and I've been spending too many
hours today hacking Makefiles :(
Constructive comments appreciated.
thanks,
greg k-h
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
