From: Parag Warudkar <kernel-stuff@comcast.net>
To: Michael Hanselmann <linux-kernel@hansmi.ch>
Cc: debian-powerpc@lists.debian.org,
linux-kernel <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org
Subject: Re: PowerBook5,8 - TrackPad update
Date: Tue, 29 Nov 2005 11:11:03 -0500 [thread overview]
Message-ID: <2100B419-3498-4BAF-8186-3EC06A917DF6@comcast.net> (raw)
In-Reply-To: <20051129075047.GA26460@hansmi.ch>
On Nov 29, 2005, at 2:50 AM, Michael Hanselmann wrote:
> The mouse moves, but slowly. Maybe something isn't correct yet, but it
> works basically.
Yeah, mine works like that too - but sometimes it will go left->right
when you moved the finger
right->left and vice versa.
> I get 256 bytes in each transfer as well, but didn't look at the bytes
> behind 40. Maybe that'll help to make it more responsive.
Nope, if yours works with 80 bytes, it only sends 80. It will still
work with anything > 80 but that's superfluous data.
(E,g, Mine works even with 1024 - anything above 256 seems junk, but
with < 256 it dies with EOVERFLOW )
Right now I have detected that byte # 13 increases when moving finger
along the bottom from left corner to right,
and byte #11 changes when moved from bottom left corner to top left.
Gotta figure out the rest of the movement patterns
along with how many total sensors X and Y are there and how to relate
the data to something to report to the input device!
Hopefully Johannes will have a PowerBook with either of the 0x0214 or
0x0215 touchpads
and we will make some headway!
Parag
next prev parent reply other threads:[~2005-11-29 16:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 21:43 Parag Warudkar
2005-11-15 23:06 ` Benjamin Herrenschmidt
2005-11-15 23:12 ` Parag Warudkar
[not found] ` <111520052143.16540.437A5680000BE8A60000409C220076369200009A9B9CD3040A 029D0A05@comcast.net>
2005-11-16 12:02 ` Johannes Berg
2005-11-21 23:57 ` Parag Warudkar
2005-11-22 0:08 ` Parag Warudkar
2005-11-22 12:51 ` Johannes Berg
2005-11-29 0:06 ` Michael Hanselmann
[not found] ` <68465DDA-053F-4A85-9204-549E830B2269@comcast.net>
2005-11-29 7:50 ` Michael Hanselmann
2005-11-29 10:38 ` Johannes Berg
2005-11-29 16:11 ` Parag Warudkar [this message]
2005-11-30 11:17 ` Johannes Berg
2005-11-30 22:39 ` Michael Hanselmann
2005-11-30 23:46 ` Michael Hanselmann
2005-12-02 14:28 ` Stelian Pop
2005-12-04 22:42 ` Michael Hanselmann
2005-12-06 3:38 ` Andy Botting
2005-12-06 21:12 ` Michael Hanselmann
2005-12-09 23:33 ` Michael Hanselmann
2005-12-23 23:59 ` Benjamin Herrenschmidt
2005-12-24 11:52 ` René Nussbaumer
2005-12-24 20:17 ` Pavel Machek
2005-12-24 22:27 ` Benjamin Herrenschmidt
2005-12-24 23:19 ` Pavel Machek
2005-12-25 0:33 ` Benjamin Herrenschmidt
2005-12-25 0:52 ` Dmitry Torokhov
2005-11-16 15:40 Parag Warudkar
2005-11-16 15:43 Parag Warudkar
2005-11-16 15:49 ` Johannes Berg
2005-11-16 16:07 Parag Warudkar
2005-11-16 16:13 ` Johannes Berg
2005-11-29 6:17 Parag Warudkar
2005-12-02 17:02 Parag Warudkar
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=2100B419-3498-4BAF-8186-3EC06A917DF6@comcast.net \
--to=kernel-stuff@comcast.net \
--cc=debian-powerpc@lists.debian.org \
--cc=linux-kernel@hansmi.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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
all inboxes | Powered by JetHome®