On Tuesday 02 January 2007 7:16 am, Alan Stern wrote: > On Mon, 1 Jan 2007, Andrey Borzenkov wrote:
> > Is the original problem (OHCI constantly attempting and failing to suspend > > root hub) supposed to be fixed in 2.6.20? > > No. It can't be fixed in the kernel because it is a hardware bug. I'm curious though: did older kernels, say 2.6.18, have such issues? If not, it may still be a software issue ... if you had to use the sysfs based workaround before, I'm happy to call it a hardware issue. > > Currently in rc3 I have > ... > > ohci_hcd 0000:00:02.0: auto-stop root hub > > ohci_hcd 0000:00:02.0: auto-wakeup root hub > > ohci_hcd 0000:00:02.0: auto-stop root hub > > ohci_hcd 0000:00:02.0: auto-wakeup root hub > > ... > > > > and it goes on and on until I stop it manually by usual method: > > > > usb usb1: remote wakeup needed for autosuspend > > The patch mentioned above allows the manual method to work. Not just that ... it also fixed the problem where quirk entries saying "don't even try using remote wakeup" stopped working. Once some pending PPC-related OHCI patches merge (support for PS3 and other CELL systems), there will be infrastructure that makes it easier to add quirk entries that say "this board can't do remote wakeup properly". At that point, we can start to collect quirks for boards like this one. - Dave ------------------------------------------------------------------------- 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-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
