On Wednesday 04 April 2007 16:05, you wrote: > > I played with HUB_ROOT_RESET_TIME (default 50 ms) and found that 90 > > ms works. I booted three times to make sure. I also booted three > > times with 80 ms and I received the same read error every time. > > > > But the 40 ms apart can't be explained by the 10 ms to 1ms > > resolution step that you get when moving from CONFIG_HZ=100 to > > CONFIG_HZ=1000, can they? I figure 9ms apart would make sense, but > > nothing larger or equal than 10 ms would. > > I don't understand it either. > > The USB spec lists 50 ms as the minimum reset time with no maximum, > so increasing it won't hurt. On the other hand, maybe we don't > really need to. > > > Anyway, should I patch HUB_ROOT_RESET_TIME every time I compile a > > fresh kernel or is this read error superficial (because the device > > seems to work)? > > As long as the device works, it doesn't matter that the very first > reset fails. The driver retries multiple times. > > Alan Stern
Hi Alan, good to know it retries. I'll just let it be then. Thank you very much! Sebastian ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
