@Kevin Cernekee
I have been asked to submit my patchset directly to the linux-input
newgroup. My patchset incorporates Ben's reverse-engineering for the
alps signature 0x73, 0x03, 0x0a and mine for 0x73, 0x03, 0x50. Your
patchset for 0x73, 0x03, 0x0a is very different, and has a lot of code
cleanup (which is a good thing.) Comments/Questions:
1) Where did you get the device names ("Dolphin", "Pinnacle", "Mercury",
etc.) and how did you figure out the protocols? Neither Ben nor I got
any kind of response from ALPS so we reverse engineered the protocol
under a virtual Windows environment. Did ALPS provide you information
on the devices?
2) All the existing EC responses are of the form 0x88, 0x07, 0xXX,
except for the signature 0x73, 0x03, 0x50, which has EC responses of
0x73, 0x01, {0x0d | 0x02}. Your patch #2 has the following assumption:
'It is presumed (hoped) that anything that isn't in the Pinnacle series
will not return "88 07 xx" or "88 08 xx".' This may break some existing
touchpad interfaces.
Any way you could provide your psmouse dkms as a tarball? Esp. because
there are a number of Fedora and Arch Linux users running my psmouse
dkms.
@all
Can people test Kevin's patch? If it works, then I'll layer the Dell
I15R, I17R, 13z on top of it and submit a patch to linux-input.
--
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
