Hi, I succeeded in reproducing the reverse engineering steps for the Dell E6230 touchpad.
Here is an updated version of Dave's dkms module which is **ONLY** for the E6230. Starting from the init sequenced captured via qemu, I have tried to make some sense out of the commands. It seems that this init sequence is in fact quite different from that on the E6430 (which reports 73 03 0a on E7 report as well). At some point I thought that difference was related to the presence of a touchstick on 6430/6530 and not on 6230, but it seems to be more than that. Do not use this if you do not have the same hardware as me. I do not, at the moment, know how to distinguish between the dell E6430 and dell E6230 models. Using the newly built psmouse module, I can use the rightmost area of the pad to scroll, which is all I need. I don't know about other useful features, probably I would need to enable them from my windows VM before being able to see how they get initialized. This is something I can do, if deemed useful. It would be nice to tidy up this set of patches, in particular: (1) make the v5 and v6 init sequences more readable (2) differentiate between the various models (this applies to the models whose E7 report says 0x73 0x03 00x0a). Doing (1) is easy, but a test host is needed. Doing (2) requires some interaction with a user of such a platform. Volunteers ? Best, E. ** Attachment added: "updated dkms module for Dell E6230 ONLY" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238/+attachment/3450457/+files/psmouse-alps-dst-1.1.dell-e6230.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
