On Wed, 1 Feb 2006, Dmitry Torokhov wrote: > > The older Red Hat code triggers the USB handoff setup from the i8042 > > setup at the point the i8042 appears to be talking through its backside. > > Seems to be no reason for the non modular case the same cannot be done > > now (or done for all cases if need be) > > > > Quite often we need handoff even if i8042 seems to be OK otherwise and > responds to basic queries - mostly on laptops where Synaptics/ALPS is > not recognized until we perform do handoff.
At the moment, it appears that there are some systems where you can't communicate with the i8042 until after doing the USB handoff, and there are other systems where you can't communicate with it before doing the handoff. So it's a problem. 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. In theory the i8042 driver can be built as a module also. Probably not too many people do it, though... 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
