PS2 Input Core Support
Quoted 26 lines · Vojtech Pavlik
Quoted 25 lines · Petr Vandrovec
Quoted 11 lines · Vojtech Pavlik
drivers/input/mouse/psmouse.c Wed Jul 17 12:19:13 2002 line 148
Quoted 11 lines
drivers/input/mouse/psmouse.c Wed Jul 17 12:19:13 2002 +1
-1@@ -142,7 +142,7 @@ */ if (psmouse->type == PSMOUSE_IMEX) { - input_report_rel(dev, REL_WHEEL, (int) (packet[3] & 8) - (int) (packet[2] & 7)); + input_report_rel(dev, REL_WHEEL, (int) (packet[3] & 8) - (int) (packet[3] & 7)); input_report_key(dev, BTN_SIDE, (packet[3] >> 4) & 1); input_report_key(dev, BTN_EXTRA, (packet[3] >> 5) & 1); }Hi,
any plans to support A4Tech mouse? It uses IMEX protocol, butswitch(packet[3] & 0x0F) { case 0: /* nothing */ case 1: vertical_wheel--; break; case 2: horizontal_wheel++; break; case 0xE: horizontal_wheel--; break; case 0xF: vertical_wheel++; break; }
Quoted 4 lines
Quoted 1 line
and obviously it never reports wheel move > 1 in one sample.
Is there a way to detect whether it's an ImEx or A4? Or will we need a command line parameter ... ?
I'm not aware of any way. It behaves like proper ExPS/2 mouse: after reset it returns id0, after ImPS/2 sequence 3, and after ExPS/2 sequence 4. In both ImPS/2 and ExPS/2 modes it uses 2/0xE(0xFE) in fourth byte of packet for horizontal wheel.
Windows .INF talks about "A4M0004", but it looks to me like an internal .INF identifier and not as an identification string obtainable from mouse.
I'll try to write email to them, maybe they'll answer.
Thanks,
Petr Vandrovec [email protected]