@Emmanuel

"Kevin's patch do not properly take into account the fact that the e6230
has 16 and 12 bits for the MT slots, and not 15 and 11 (this is the
ALPS_BITMAP_X_BITS and ALPS_BITMAP_Y_BITS setting)."

I will check this out.  2-finger scroll worked for me but I didn't do
much else with MT.

Are you seeing incorrect readings when using MT, or is your comment just
based on the code?  It would not be too surprising if different
initialization sequences altered the data format (ala Dolphin's 8-byte
vs. 9-byte setting).

Along similar lines, it would be nice if we could adjust the Rushmore
trackstick sensitivity so that it used the existing V3 trackstick report
code as-is, with no special divisor.

Anyway, thanks for the feedback.


"In the ``seemingly different hardware category'', one could be mistaken into 
listing the Dell E6230/E6430. These do have identical hardware, except for the 
absence of the trackstick on the smaller E6230."

E6230 has:

 - touchpad (80mm x 40mm)
 - 2 lower buttons
 - no middle button :(

E6430 has:

 - touchpad (80mm x 45mm)
 - trackstick
 - 3 upper buttons
 - 2 lower buttons

I borrowed an E6530 earlier in the week to test my patches, but
unfortunately I didn't note the dimensions or layout.  IIRC it was the
same as the E6430.


"My reverse-engineering work and merge with bgamari's patches show this. These 
are differentiated by querying the 0xc2c8 register, which is not queried in 
Kevin's patch."

Do you feel comfortable making the statement that checking the 0xc2c8
register on Rushmore will unambiguously indicate whether the
configuration has a trackstick present (even if we're dealing with a
completely new, unknown PC)?

I did not see the ALPS driver checking this register, so if we don't
know for certain that this is the purpose of the 0xc2c8 register, it
might just be safer to always create the virtual trackstick device on a
Rushmore-equipped PC (even if we never send it any reports).


"Briefly put, I think we should work making all this stuff cleaner."

One thing that would probably make sense is to store the appropriate
function pointers + constants in the alps_data struct, so we do not need
case statements all over the code.

-- 
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to