On Fri, 26 Nov 2004 09:00:20 -0800, David Brownell <[EMAIL PROTECTED]> wrote:
> (Where you've got a hub at period 256 ms, > and the MCT wants both 1msec and 2msec periods ... there's > no way to pack a schedule according to that shortcut.) You're right, of course. Using an old 1.1 hub instead of 2.0 hub makes the problem to go away. > > Kernel 2.4.28-bk3. > > FWIW, when I dust off and debug my EHCI schedule tree patch, > I'm not planning on backporting it. [...] It's all right, as long as I have a good explanation to close bugs. -- Pete ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
