From: Rafi Rubin <rafi@seas.upenn.edu>
To: linux-input@vger.kernel.org
Subject: Re: Touchpad on Dell Latitude XT (alps 73 00 14)
Date: Tue, 03 Mar 2009 16:09:31 -0500 [thread overview]
Message-ID: <49AD9C8B.1000009@seas.upenn.edu> (raw)
In-Reply-To: <20090111235407.ZZRA012@mailhub.coreip.homeip.net>
>> { { 0x73, 0x00, 0x14 }, 0xf8, 0xf8, 0 }
>>
>> How can I determine what values to use for those last three fields?
>>
>
> f your touchpad works (you don't see any messages from psmouse in dmesg
> and every button works fine) then these are correct values.
I took another look at it and would appreciate a little more advice.
First off, it seems that regardless of which flags I use (except for
ALPS_PASS), the first byte is 0xff for all packets. So those masks
don't seem to do anything useful for my device.
The touchpad does work fine. And with ALPS_DUALPOINT, packet[5] always
comes out as 127. However those 4 bytes in the middle act a little
weird. It looks to me like they are just rotating as if the packet size
is incorrect.
[ 1325.709029] alps packet: ff 02 00 00 08 7f
[ 1325.722834] alps packet: ff 00 08 02 02 7f
[ 1325.737028] alps packet: ff 08 02 00 00 7f
[ 1325.760152] alps packet: ff 01 00 00 08 7f
[ 1325.773963] alps packet: ff 00 08 01 00 7f
[ 1325.824228] alps packet: ff 00 01 00 08 7f
[ 1325.838144] alps packet: ff 01 08 00 00 7f
Where do the first and last bytes come from? Are they being sent by the
device, or added by a driver?
Any thoughts?
Rafi
prev parent reply other threads:[~2009-03-03 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 23:51 Touchpad on Dell Latitude XT (alps 73 00 14) Rafi Rubin
2009-01-12 7:58 ` Dmitry Torokhov
2009-01-12 8:43 ` Rafi Rubin
2009-03-03 21:09 ` Rafi Rubin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49AD9C8B.1000009@seas.upenn.edu \
--to=rafi@seas.upenn.edu \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).