> - do you want me to add this to the main kernel tree?  It should
>   probably go somewhere like drivers/usb/device.

Well, parts of it.  I had half thought about drivers/usb/dcd
for the Device Controller Driver parts (matching 'hcd' for
the Host Controller Drivers :), but some of those would
best belong in the architecture-specific trees (SA-1110
as one example).

Might be worth thinking about whether more rework of
the USB tree layout would be a good thing.  Assuming
we keep getting more drivers, I think adding subdirs
would help make things more manageable.  Ones for
network and webcame (host side) drivers would seem
like a good start.  And "device side drivers" might live
in their own directories ... for all that I've suggested the
network stack as the preferred interop solution for smart
Linux devices and their hosts (any kind).

Before it goes there, I thought I'd request some discussion
and convergence of the API with what's already there.
Easier to achieve that before integration than after.

Different terminology for the same thing would just be
confusing, for example... a USB "interface" should be
called the same thing everywhere, but seems like it's
become a "function" in this USBD code, while the
word "interface" is used to describe controllers
(host and device).


> - it looks like your usbd api is close to the same as the
>   existing usb api.  Why not make it even closer to help provide
>   some "familiarity" when writing drivers for both sides of the
>   wire?  For example, usbd_alloc_urb() takes 4 parameters, while
>   usb_alloc_urb() takes 2.

Exactly: API convergence.  Constants and structure defs
(for descriptors etc) should be the same (common header?),
there should NOT be two conflicting definitions of "URB",
and so on.

Maybe we can use this API to finally shrink and simplify the
URB model in the host side drivers ... convergence would
more naturally involve changes on _both_ sides.

Plus think that if, as Stuart said, he thinks it's a bit "over elaborated",
incremental integration (in simpler chunks) would be a good way
way to address some of those issues.

- Dave




_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to