On Sat, 14 Jan 2006, Walt H wrote: > OK. No lines reporting handoff problems in any of the boots. The only > boot in which I still have a keyboard is when I comment out the OHCI > handoff. I saved dmesg's of all boots, and ran diffs against them. The > uncommented handoffs and the EHCI commented handoff are essentially the > same (where the OHCI handoff code still executes in both). The relevant > (diff'd) sections are: > > @@ -153,3 +153,2 @@ > -i8042.c: Can't read CTR while initializing i8042. > -pnp: Device 00:09 does not supported disabling. > -pnp: Device 00:08 does not supported disabling. > +serio: i8042 AUX port at 0x60,0x64 irq 12 > +serio: i8042 KBD port at 0x60,0x64 irq 1 > @@ -219,0 +219 @@ > +input: AT Translated Set 2 keyboard as /class/input/input0 > @@ -234,0 +235 @@ > +input: PS/2 Generic Mouse as /class/input/input1 > @@ -268 +269 @@ > -input: Logitech USB Mouse as /class/input/input0 > +input: Logitech USB Mouse as /class/input/input2 > > Hope that helps,
That's good; you've narrowed it down to the OHCI handoff. Now try editing the quirk_usb_handoff_ohci() routine. There's the section enclosed in "#ifndef __hppa__" and the two writel() calls after it. Add printk statements to see which writes are taking place, try commenting out some of the writes -- in general, see what makes a difference. Unfortunately I can't give you any detailed suggestions because I don't know how the hardware is supposed to work. 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
