linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Barton C Massey <bart@cs.pdx.edu>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input <linux-input@atrey.karlin.mff.cuni.cz>,
	"Antonio-M. Corbi Bellot" <antonio.corbi@ua.es>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] don't invert mightymouse hwheel
Date: Thu, 12 Apr 2007 14:25:09 -0700	[thread overview]
Message-ID: <200704122125.l3CLP9aQ005277@wezen.cs.pdx.edu> (raw)
In-Reply-To: Your message of "Thu, 12 Apr 2007 18:04:07 +0200." <Pine.LNX.4.64.0704121800000.19492@jikos.suse.cz>

In message <Pine.LNX.4.64.0704121800000.19492@jikos.suse.cz> you wrote:
> On Thu, 12 Apr 2007, Johannes Berg wrote:
> 
> > This is not true. With this X configuration:
> > 
> >     Section "InputDevice"
> >         Identifier  "EvDev"
> >         Driver      "evdev"
> >         Option      "SendCoreEvents"    "true"
> >         Option      "evBits"            "+1-2"
> >         Option      "keyBits"           "~272-287"
> >         Option      "relBits"           "~0-2 ~6 ~8"
> >         Option      "Pass"              "3"
> >     EndSection
> > I can scroll up in a window by moving my finger up, and scroll left in a
> > window by moving my finger right. That makes no sense, this patch therefore
> > removes the INVERT_HWHEEL quirk from the USB mightymouse.
> 
> Johannes, Bart, 
> 
> I unfortunately don't have the hardware in question to test with. This X 
> configuration is of course perfectly valid.
> 
> Bart, as you wrote the original patch which inverted the wheel, could you 
> provide some more information please? It seems to me that you guys have 
> different versions of mightymouse ... but I wouldn't believe they would 
> have the same PID :)

Give me a day or so to check all this out.  I don't think
looking at the X behavior is too useful: too many place that
the direction can be swapped.  Instead, look which way the
bits coming directly out of evdev point.  IIRC I set things
up so that positive X was the same as on other evdev
devices.  Is the supplied X config swapping the X axis with
this line?

  > >         Option      "evBits"            "+1-2"

One possible source of confusion is that Iceweasel scrolls
backward by default (on all devices, not just MM).  You can
fix this by changing a setting in the Iceweasel config.

	Bart

  parent reply	other threads:[~2007-04-12 21:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11 22:23 [PATCH] don't invert mightymouse hwheel Johannes Berg
2007-04-12 16:04 ` Jiri Kosina
2007-04-12 21:25 ` Barton C Massey [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2007-04-13  0:21 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
2007-04-23 14:13         ` Johannes Berg
2007-04-26  8:24 ` Johannes Berg
2007-04-13  0:32 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=200704122125.l3CLP9aQ005277@wezen.cs.pdx.edu \
    --to=bart@cs.pdx.edu \
    --cc=antonio.corbi@ua.es \
    --cc=jkosina@suse.cz \
    --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).