public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Parag Warudkar <kernel-stuff@comcast.net>
Cc: debian-powerpc@lists.debian.org, linux-kernel@vger.kernel.org
Subject: Re: PowerBook5,8 - TrackPad update
Date: Wed, 16 Nov 2005 16:49:44 +0100	[thread overview]
Message-ID: <1132156185.4843.3.camel@localhost> (raw)
In-Reply-To: <111620051543.21656.437B53B5000EABF300005498220074818400009A9B9CD3040A029D0A05@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]

On Wed, 2005-11-16 at 15:43 +0000, Parag Warudkar wrote:
> Ah and yes I forgot about the dual finger scrolling function - newer
> trackpads allow you to use 2 fingers to slide up and down to achieve
> scrolling. I don't see any code in current appletouch.c which handles
> this. We might be able to live without it for some time but maybe we
> can't as it might screw up the reporting if not handled. (PPC assembly
> is fun to work with :)

That's a pure driver function, and we didn't implement it because we
emulate synaptics. I think your erratically moving thing might be caused
by a relayout of the order, maybe you should try to observe the
interrupt transfers the device gives you in a systematic way like I did
with my python scripts? Those display the levels of each byte. Maybe
they changed to transmitting not bytes but words for each level?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  reply	other threads:[~2005-11-16 15:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 15:43 PowerBook5,8 - TrackPad update Parag Warudkar
2005-11-16 15:49 ` Johannes Berg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-02 17:02 Parag Warudkar
2005-11-29  6:17 Parag Warudkar
2005-11-16 16:07 Parag Warudkar
2005-11-16 16:13 ` Johannes Berg
2005-11-16 15:40 Parag Warudkar
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
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

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=1132156185.4843.3.camel@localhost \
    --to=johannes@sipsolutions.net \
    --cc=debian-powerpc@lists.debian.org \
    --cc=kernel-stuff@comcast.net \
    --cc=linux-kernel@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