On Sat, May 15, 2010 at 10:05 AM, Thomas Bächler <thomas@xxxxxxxxxxxxx> wrote:
> Am 15.05.2010 15:52, schrieb Thomas Bächler:
>> ---
>> drivers/input/mouse/alps.c | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
>> index 99d5876..0c83070 100644
>> --- a/drivers/input/mouse/alps.c
>> +++ b/drivers/input/mouse/alps.c
>> @@ -66,6 +66,8 @@ static const struct alps_model_info alps_model_data[] = {
>> { { 0x73, 0x02, 0x50 }, 0xcf, 0xcf, ALPS_FOUR_BUTTONS }, /* Dell Vostro 1400 */
>> { { 0x52, 0x01, 0x14 }, 0xff, 0xff,
>> ALPS_PASS | ALPS_DUALPOINT | ALPS_PS2_INTERLEAVED }, /* Toshiba Tecra A11-11L */
>> + { { 0x73, 0x02, 0x64 }, 0xff, 0xff,
>> + ALPS_PASS | ALPS_DUALPOINT }, /* Dell Latitude E6410 */
>> };
>>
>> /*
>
> Okay, never mind, we were too quick in thinking everything was correct,
> the parameters seem to be wrong. The touchpad is detected and seems to
> work, but in 'synclient -m', you see that actually nothing happens.
>
> Dmitry, do you know which parameters we need to tweak to fix this? Maybe
> the 0xff, 0xff mask is wrong? Or the flags? Sorry, my knowledge ends here.
Been there, done that. I originally pushed a patch with this signature
about a month ago. It was applied, but then reverted because it didn't
work right. It seems there's a new protocol for these alps touchpads
that will need to be figured out first.
-- Chase
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
