Thanks for your efforts on this. Yes, I made mistake(s) converting the V5 init sequence, which you debugged and successfully fixed. I have added your changes to a new patch candidate at [1]
Please test. If I hear nothing in a couple days I will resubmit the E6430/E6530 patch to ubuntu.
To answer your questions:
Q1) Yes, I think it is the same thrice PSMOUSE_CMD_RESET_WRAP sequence. This is the indicator to enter "command mode", where the touchpad can be configured. I have added this to the code. Ben and I have not figured out what is being configured when in command mode, just that it works.
Q2) PSMOUSE_CMD_GETINFO returns a three-byte status code in the param field. It is important to determine the alps touchpad version for the so-called "E6" and "E7" code fragments . I could not figure out what the three-byte value indicates at other times.
@malte skoruppa
Thanks for your efforts on this. Yes, I made mistake(s) converting the V5 init sequence, which you debugged and successfully fixed. I have added your changes to a new patch candidate at [1]
Please test. If I hear nothing in a couple days I will resubmit the E6430/E6530 patch to ubuntu.
To answer your questions:
Q1) Yes, I think it is the same thrice PSMOUSE_ CMD_RESET_ WRAP sequence. This is the indicator to enter "command mode", where the touchpad can be configured. I have added this to the code. Ben and I have not figured out what is being configured when in command mode, just that it works.
Q2) PSMOUSE_CMD_GETINFO returns a three-byte status code in the param field. It is important to determine the alps touchpad version for the so-called "E6" and "E7" code fragments . I could not figure out what the three-byte value indicates at other times.
[1]: http:// www.dahetral. com/public- download