Hi Vasily, Thanks for your mail & information. We would start the investigation and give you feedback later. Please wait.
> The issues occurs on every kernel after > 1302bac33d9e88cd43e482191a806998f3ed43cc commit. Before the commit, this > touchpad device was detected as PS/2 mouse and "cat /dev/input/mice" shows > data when the touchpad is used. > After the commit, there are no events from the touchpad in /dev/input/mice or > /dev/input/mouseX files anymore. > > According to drivers/input/mouse/alps.c source file, all devices with > signatures "ec[0] == 0x88 && ec[1] == 0x08" are treated as "Rushmore > touchpads". This touchpad has E7 signature of "73-03-0A" and EC signature of > "88-08-22", and it looks like that V5 protocol (not > "Rushmore") should be used here. If V5 protocol is forced to use for this > device then everything works fine. > > The patch is trivial, but I'm not sure how to properly separate "Rushmore" > and "V5" devices. Are there any datasheets or experts to help me with it? > I checked the E7 & EC information and think it should be a Rushmore device. Could you please let me know after you use V5 protocol, if touchpad still be recognized as "AlpsPS/2 ALPS DualPoint TouchPad" or returns to "PS/2 Generic Mouse" ? Thanks -- Best Regards, Tommy -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
