From: Chase Douglas <chase.douglas@canonical.com>
To: Michael Poole <mdpoole@troilus.org>
Cc: Jiri Kosina <jkosina@suse.cz>, linux-input@vger.kernel.org
Subject: Re: [PATCH] hid-magicmouse: Correct parsing of large X and Y motions.
Date: Mon, 05 Jul 2010 12:28:08 -0400 [thread overview]
Message-ID: <1278347288.2425.21.camel@cndougla> (raw)
In-Reply-To: <878w5qaspq.fsf@troilus.org>
On Mon, 2010-07-05 at 10:50 -0400, Michael Poole wrote:
> The X and Y values have two more significant bits in the same byte
> that contains click status. Include these in the reported value.
> Thanks to Iain Hibbert of NetBSD for pointing this out.
>
> Signed-off-by: Michael Poole <mdpoole@troilus.org>
> ---
> drivers/hid/hid-magicmouse.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/hid/hid-magicmouse.c b/drivers/hid/hid-magicmouse.c
> index 0b89c1c..7cdda23 100644
> --- a/drivers/hid/hid-magicmouse.c
> +++ b/drivers/hid/hid-magicmouse.c
> @@ -267,8 +267,8 @@ static int magicmouse_raw_event(struct hid_device *hdev,
> * to have the current touch information before
> * generating a click event.
> */
> - x = (signed char)data[1];
> - y = (signed char)data[2];
> + x = (int)(((data[3] & 0x0c) << 28) | (data[1] << 22)) >> 22;
> + y = (int)(((data[3] & 0x30) << 26) | (data[2] << 22)) >> 22;
> clicks = data[3];
> break;
> case 0x20: /* Theoretically battery status (0-100), but I have
Looks right to me.
Acked-by: Chase Douglas <chase.douglas@canonical.com>
-- Chase
next prev parent reply other threads:[~2010-07-05 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 14:50 [PATCH] hid-magicmouse: Correct parsing of large X and Y motions Michael Poole
2010-07-05 16:28 ` Chase Douglas [this message]
2010-07-11 21:07 ` Jiri Kosina
2010-07-05 19:54 ` Ping Cheng
2010-07-05 20:02 ` Chase Douglas
2010-07-05 20:33 ` Michael Poole
2010-07-05 20:51 ` Chase Douglas
2010-07-05 22:08 ` Michael Poole
2010-07-05 22:25 ` Chase Douglas
2010-07-06 11:23 ` ext-phil.2.carmody
2010-07-06 11:38 ` Datta, Shubhrajyoti
2010-07-06 11:55 ` Michael Poole
2010-07-06 13:05 ` ext-phil.2.carmody
2010-07-05 22:51 ` 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=1278347288.2425.21.camel@cndougla \
--to=chase.douglas@canonical.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=mdpoole@troilus.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).