On Wed, 1 Feb 2006, Dmitry Torokhov wrote: > FWIW I just had another example where i8042 is half alive/sane > (reports supporting active multiplexing revision 1.9 but touchpad does > not work). Using "usb-handoff" cures it (multiplexor revision 1.1 and > everything is fine). BTW it's a SIS with EHCI/OHCI.
In the other bug report example you mentioned, the controllers needing usb-handoff were all UHCI. I'm glad to see other types need it too. > > Maybe the best answer will be to add back the boot parameter, in a > > "no-usb-handoff" form. Then people with buggy BIOSes would be able to > > suppress the normal pre-i8042 handoff; the handoff wouldn't take place > > until the USB host controller drivers were loaded. That ought to work if > > those drivers are built as modules; I'm not sure it would work if they > > were compiled into the kernel. > > > > Having an option to disable handoff is a good idea. (It won't disable handoff completely; it will just delay it until the host controller driver initializes the controller. Obviously the driver needs to take control of the hardware away from the BIOS before using it.) Okay, I'll write it. Until the BIOS people get their act together, we don't have much choice. I wonder how this is handled by Windows? Alan Stern ------------------------------------------------------- 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&kid=103432&bid=230486&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
