From: "Zephaniah E. Hull" <warp@aehallh.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Barton C Massey <bart@cs.pdx.edu>, Jiri Kosina <jkosina@suse.cz>,
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: Wed, 25 Apr 2007 16:06:51 -0400 [thread overview]
Message-ID: <20070425200650.GE4831@aehallh.com> (raw)
In-Reply-To: <1176446418.7052.54.camel@johannes.berg>
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
On Fri, Apr 13, 2007 at 08:40:18AM +0200, Johannes Berg wrote:
> On Thu, 2007-04-12 at 14:25 -0700, Barton C Massey wrote:
>
> > > I unfortunately don't have the hardware in question to test with. This X
> > > configuration is of course perfectly valid.
>
> I copied it straight out of the manpage so I'd hope so :>
>
> > 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.
>
> I can do that (early next week), but I don't have any other devices to
> test with. Can provide a dump.
>
> > 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"
>
> No idea! I just copied it out of the manpage from evdev(4)
As the xf86-input-evdev maintainer, I can tell you quite firmly that the
answer is a solid no.
However I can also tell you that I may infact have the behavior
backwards in the driver. :)
Yell, scream, and shout if that's the case.
Zephaniah E. Hull.
--
1024D/E65A7801 Zephaniah E. Hull <warp@aehallh.com>
92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801
CCs of replies from mailing lists are requested.
If I have trouble installing Linux, something is wrong. Very wrong.
-- Linus Torvalds on l-k.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-25 20:06 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
2007-04-13 6:40 ` Johannes Berg
2007-04-25 20:06 ` Zephaniah E. Hull [this message]
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-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-13 9:30 ` 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=20070425200650.GE4831@aehallh.com \
--to=warp@aehallh.com \
--cc=antonio.corbi@ua.es \
--cc=bart@cs.pdx.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.