Roman,
Thanks for posting that!
> Patch 2: replaces the 'old fashioned' roothub process with a
> virtual root hub and also uses the bus wires to detect new devices
> (this makes it more conform with how other Linux USB-host-driver
> like OHCI and UHCI manages the root-hub
> and the detection of devices is more USB spec. conform)
This is interesting. So by my count we now have five publicly
available USB Host Controller Drivers (hcds) in various stages,
not sharing much code at all:
- ohci (and patches for at least ARM/PPC)
- 2 uhci drivers
- mpc823/850
- ehci (early usb 2.0 support, limps; [1])
I don't know how much you looked at the "hcd" layer in my
EHCI code, but as I recall you liked the basic premise of
sharing more code. Basically, more sharing means fewer
places that hcd-specific behaviors (bugs) can happen, and
better testing/tuning/reliability in the shared code.
Have you looked at using the root hub code in that framework?
I think you're not going to care about the pci support, but that's
optional anyway. The root hub code is based on yours, but it
it's split into generic vs hcd-specific parts and doesn't provide
analogues for "hub.h" or "usb.h" already handle.
I'd like to see the new host controller drivers sharing as
much code as possible. Do you agree? If so, got any
suggestions about how to move forward? One idea is
to have a development tree in cvs at sourceforge. Or
just to add a new "linux/drivers/usb/hcd.c" that could be
used by newer drivers; maybe it could just provide more
functionality in an enlarged "usb_bus" layer rather than
creating an more functional version of the same abstraction.
- Dave
[1] http://marc.theaimsgroup.com/?l=linux-usb-devel&m=98384579217143&w=2
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
