> As far as how to proceed with some version of ohci-hcd for 2.4.x, that
> issue should be discussed on the usb mailing list. rmk and David
> Brownell undoubtedly will have opinions about how to go about this.
I'd been thinking of applying the same kind of updates to 'ohci-hcd'
that have been applied to 'ehci-hcd' (*), and merging those into 2.5
at some point. The idea would be identical driver source code in both
kernels ... 2.5 could still change in ways that'd prevent that, but
it's achievable for 2.5.39. Fewer differences == better, usually.
I really wouldn't recommend 2.5.30, that's missing a lot of updates.
Try 2.5.40 instead; I think all the main updates there are done, too.
(Except removing interrupt automagic!)
Seems to me that merging "ohci-hcd" into 2.4.20 would be fine, but
transitioning to that "new ohci" from the "old ohci" (let's avoid any
"alt" vs. ? confusion) would necessarily need time. I'd rather see
that not be an ARM-specific backport (of an older version) but I'd
be all in favor of someone else making the patches happen!
- Dave
(*) Marcelo hasn't yet applied the ehci-hcd patches. I understand
that 2.4.20-pre8-ac2 has them ... syncing 2.4 ehci with 2.5.39.
So for the moment, ac2 would be the best release to integrate
against, it's got most of the relevant "hcd" framework updates.
-------------------------------------------------------
This sf.net email is sponsored by: DEDICATED SERVERS only $89!
Linux or FreeBSD, FREE setup, FAST network. Get your own server
today at http://www.ServePath.com/indexfm.htm
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
