On 2/1/06, Alan Stern <[EMAIL PROTECTED]> wrote: > Dmitry: > > These two bug reports appear to be the same problem: > > http://bugzilla.kernel.org/show_bug.cgi?id=4791 > http://bugzilla.kernel.org/show_bug.cgi?id=5932 > > My feeling is that there's no way to change the OHCI usb-handoff code so > that it will work with these buggy BIOSes. The reason the problem is > showing up now is probably an order-of-execution thing. Previously the > i8042 would be initialized before the USB handoff, so it worked okay. Now > the i8042 initialization occurs after the USB handoff, so it fails. > > I don't know what we can do about this. Perhaps you could somehow force > the i8042 initialization to run earlier when it's not built as a module? >
[Adding Vojtech to CC as he may remember more about handoff business] Alan, Unfortunately for some boxes we _need_ to perform USB handoff before initializing i8042 to avoid getting "Can't read CTR" condition, as you can see from this bug: http://bugzilla.kernel.org/show_bug.cgi?id=2935 I also remember reports outside bugzilla that were cured with "usb-hanoff". So it is kind of "damned if you do, damned if you don't" scenario. Could you ask guys having problems with OHCI handoff try older kernel (like 2.6.13) with "usb-handoff" on the command line? Maybe there is still a way to get OHCI handoff going... -- Dmitry ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
