On Tue, Apr 02, 2002 at 05:24:53PM -0800, David Brownell wrote:
> > > > drivers/usb/bi device interfaces
> > >
> > > "bi"? Why not "di"?
> >
> > ...
> > You would also end up describing them as Linux USB Device device drivers
> > which is starting to get silly :-)
>
> Which is why I've talked about "Device Controller Drivers", by
> analogy to their corresponding "Host Controller Drivers". When
> someone says "bi di" I think of multi-lingual text layout ... :)
>
> A while back I concluded that "device driver" is a bad term
> to use in the USB world, since any given communication
> involves at least four drivers (!) for things that someone will
> want to call a "device driver", thereby confusing someone:
>
> - (host side) "interface driver", sometimes called "clients"
> "class" drivers, or "vendor-specific" drivers
> - (host side) "host controller driver" [HCD]
> - (device side) "device controller driver" or whatever (*)
> - (device side) "function driver"
I'm not really too hung up on nomeclature. If you want to move most
of what is currently in the toplevel of the drivers/usb directory
into sub-directories and add a few more for the device side that
will be fine.
> HCDs are quite often PCI device drivers, and both of those
> device side drivers might reasonably talk directly to some
> kind of hardware. The controller driver certainly does.
Except for what are showing up on all the new embedded processors like
Linkup, Hitachi, Xscale etc.
--
__O
Lineo - Where Open Meets Smart _-\<,_
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <[EMAIL PROTECTED]> www.lineo.com 604-461-7532
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
