> > A less fundamental one is how to package that sharable/common
> > chunk of code. I've already structured EHCI so there's a line
> > between that sharable stuff (richer "struct usb_bus" level support)
> > and the main driver. That particular line will have to evolve from
> > what was in my March 5 snapshot ... but, how?
>
> Well, are you thinking the new code will require much change in
> the other drivers? I have been thinking that the differences
> would be hidden to the device drivers.
Basically invisible. There's a possible exception for iso scheduling,
which could arguably be requested at the microframe (1/8 frame,
frames still taking 1 millisecond). Perhaps webcam and audio
drivers would want to take advantage of that; or, perhaps not.
Oh, and the hub code needs to evolve past what's already in the
current AC series; or maybe that's also "just" scheduling.
- Dave
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
