From: Michael Poole <mdpoole@troilus.org>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH 6/6] HID: magicmouse: Adjust major / minor axes to scale
Date: Tue, 31 Aug 2010 00:28:08 -0400 [thread overview]
Message-ID: <1283228888.14419.65.camel@graviton> (raw)
In-Reply-To: <1283188858-4839-6-git-send-email-chase.douglas@canonical.com>
On Mon, 2010-08-30 at 13:20 -0400, Chase Douglas wrote:
> From: Henrik Rydberg <rydberg@euromail.se>
>
> By visual inspection, the reported touch_major and touch_minor axes
> are roughly a factor of four too small. The factor is approximate,
> since the protocol is not known and the HID report encodes touch size
> with fewer bits than positions. This patch scales the reported values
> by a factor of four.
>
> Signed-off-by: Henrik Rydberg <rydberg@euromail.se>
Acked-by: Michael Poole <mdpoole@troilus.org>
I never did figure out a more elegant or robust way to figure out this
scaling factor. Four seems like about the right number.
> ---
> 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 687dde4..b051f7d 100644
> --- a/drivers/hid/hid-magicmouse.c
> +++ b/drivers/hid/hid-magicmouse.c
> @@ -253,8 +253,8 @@ static void magicmouse_emit_touch(struct magicmouse_sc *msc, int raw_id, u8 *tda
> /* Generate the input events for this touch. */
> if (report_touches && down) {
> input_report_abs(input, ABS_MT_TRACKING_ID, id);
> - input_report_abs(input, ABS_MT_TOUCH_MAJOR, touch_major);
> - input_report_abs(input, ABS_MT_TOUCH_MINOR, touch_minor);
> + input_report_abs(input, ABS_MT_TOUCH_MAJOR, touch_major << 2);
> + input_report_abs(input, ABS_MT_TOUCH_MINOR, touch_minor << 2);
> input_report_abs(input, ABS_MT_ORIENTATION, orientation);
> input_report_abs(input, ABS_MT_POSITION_X, x);
> input_report_abs(input, ABS_MT_POSITION_Y, y);
next prev parent reply other threads:[~2010-08-31 4:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 17:20 [PATCH 1/6] HID: magicmouse: don't allow hidinput to initialize Chase Douglas
2010-08-30 17:20 ` [PATCH 2/6] HID: magicmouse: move features reports to static array Chase Douglas
2010-08-31 3:52 ` Michael Poole
2010-08-30 17:20 ` [PATCH 3/6] HID: magicmouse: simplify touch data bit manipulation Chase Douglas
2010-08-31 3:55 ` Michael Poole
2010-08-30 17:20 ` [PATCH 4/6] HID: magicmouse: remove axis data filtering Chase Douglas
2010-08-31 3:59 ` Michael Poole
2010-08-31 17:57 ` Chase Douglas
2010-08-30 17:20 ` [PATCH 5/6] HID: magicmouse: enable Magic Trackpad support Chase Douglas
2010-08-31 4:26 ` Michael Poole
2010-08-31 4:36 ` Michael Poole
2010-08-31 17:55 ` Chase Douglas
2010-08-31 17:54 ` Chase Douglas
2010-08-30 17:20 ` [PATCH 6/6] HID: magicmouse: Adjust major / minor axes to scale Chase Douglas
2010-08-31 4:28 ` Michael Poole [this message]
2010-08-31 3:46 ` [PATCH 1/6] HID: magicmouse: don't allow hidinput to initialize Michael Poole
2010-08-31 11:30 ` Michael Poole
2010-08-31 13:42 ` Chase Douglas
2010-08-31 17:49 ` Chase Douglas
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=1283228888.14419.65.camel@graviton \
--to=mdpoole@troilus.org \
--cc=chase.douglas@canonical.com \
--cc=jkosina@suse.cz \
--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).