From: Jiri Kosina <jkosina@suse.cz>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Barton C Massey <bart@cs.pdx.edu>,
linux-input <linux-input@atrey.karlin.mff.cuni.cz>,
"Antonio-M. Corbi Bellot" <antonio.corbi@ua.es>
Subject: Re: [PATCH] don't invert mightymouse hwheel
Date: Mon, 23 Apr 2007 16:07:43 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0704231555570.5138@jikos.suse.cz> (raw)
In-Reply-To: <1177335818.3528.8.camel@johannes.berg>
On Mon, 23 Apr 2007, Johannes Berg wrote:
> > This is strange, I have a bugreport in our bugzilla which states that
> > BT version of the mightymouse needs the very same quirk as USB
> > version. Recent kernels contain a duplication of the USB quirk for
> > Bluetooth version of the mouse, in order to make the scrollwheel work.
> > But 2.6.20.4+bluez patches don't provide this quirk yet.
> Same problem I had maybe with X or GTK or something flipping the axis?
Hi Johannes,
no, that's not the case, the bugreport states that scrolling the wheel
produces no input events at all, i.e. mapping of HID_GD_Z to REL_HWHEEL
(HID_QUIRK_MIGHTYMOUSE quirk) is needed.
--
Jiri Kosina
next prev parent reply other threads:[~2007-04-23 14:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 0:21 [PATCH] don't invert mightymouse hwheel Barton C Massey
2007-04-13 6:45 ` Johannes Berg
2007-04-13 7:43 ` Jiri Kosina
2007-04-13 9:30 ` Johannes Berg
2007-04-23 10:27 ` Barton C Massey
2007-04-23 13:13 ` Jiri Kosina
2007-04-23 13:43 ` Johannes Berg
2007-04-23 14:07 ` Jiri Kosina [this message]
2007-04-23 14:13 ` Johannes Berg
2007-04-26 8:24 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2007-04-13 0:32 Barton C Massey
2007-04-11 22:23 Johannes Berg
2007-04-12 16:04 ` Jiri Kosina
2007-04-12 21:25 ` Barton C Massey
2007-04-13 6:40 ` Johannes Berg
2007-04-25 20:06 ` Zephaniah E. Hull
2007-04-25 23:09 ` Barton C Massey
2007-04-26 0:00 ` Zephaniah E. Hull
2007-04-26 18:35 ` Barton C Massey
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=Pine.LNX.4.64.0704231555570.5138@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=antonio.corbi@ua.es \
--cc=bart@cs.pdx.edu \
--cc=johannes@sipsolutions.net \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
/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).