public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Esben Stien <b0ef@esben-stien.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Logitech MX1000 Horizontal Scrolling
Date: Tue, 8 Mar 2005 21:52:10 +0100	[thread overview]
Message-ID: <20050308205210.GA3986@ucw.cz> (raw)
In-Reply-To: <87wtsjtii6.fsf@quasar.esben-stien.name>

On Mon, Mar 07, 2005 at 07:31:45PM +0100, Esben Stien wrote:
> Esben Stien <b0ef@esben-stien.name> writes:
> 
> > Hmm, I'm getting the same hash for evdev.c between 2.6.10 and
> > 2.6.11. I hope Vojtech Pavlik got the reports.
> 
> Ahh, I see he got lots of juicy patches lined up. I guess I'll try
> linux-2.6.11-mm1 then.

I don't think I have a patch for the MX1000 among them. I do have the
MX1000, though, and I'm still thinking about what to do with it.

The problem is that the mouse really does reports all the double-button
stuff and autorepeat, and horizontal wheel together with button press on
wheel tilt.

It has all that in the report descriptor, and the HID driver correctly
interprets it and passes it on.

It's annoying, though.

I could kill the extra buttons (via a HID quirk), which would leave us
with autoscroll up/down/left/right, but the wheel wouldn't be
distinguishable from the autoscroll anymore.

I can't kill the autoscroll alone and leave the buttons, because again
the driver can't easily tell if it's the wheel or not.

In the end I think the best option is to leave the filtering to
userspace, which will mean more configuration necessary in the X event
mouse driver.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2005-03-08 20:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 15:22 Logitech MX1000 Horizontal Scrolling Esben Stien
2005-02-03 14:42 ` Esben Stien
2005-02-04 19:54   ` Vojtech Pavlik
2005-02-11  7:11     ` Jeremy Nickurak
2005-02-15  2:45       ` Esben Stien
2005-02-15  4:14         ` Jeremy Nickurak
2005-02-15 20:01           ` Esben Stien
2005-02-16  7:10             ` Jeremy Nickurak
2005-03-05 12:56               ` Esben Stien
2005-02-15  2:40     ` Esben Stien
2005-03-05 12:52       ` Esben Stien
2005-03-05 21:09         ` Jeremy Nickurak
2005-03-07 11:48           ` Esben Stien
2005-03-07 18:31             ` Esben Stien
2005-03-08 20:52               ` Vojtech Pavlik [this message]
2005-03-08 23:01                 ` Jeremy Nickurak
2005-03-09 11:33                 ` Esben Stien
2005-03-26  1:54                 ` Esben Stien
2005-03-29  8:07                 ` Jeremy Nickurak
2005-04-02 23:44                   ` Esben Stien
2005-04-03 16:01                     ` Juergen Kreileder
2005-04-03 23:41                       ` Jeremy Nickurak
2005-04-05  3:14                         ` Esben Stien
2005-04-05  3:12                       ` Esben Stien
2005-04-05  3:48                         ` David A. Desrosiers
2005-04-05 14:58                           ` Esben Stien
2005-04-05 18:52                             ` Juergen Kreileder
2005-04-05 14:56                         ` Esben Stien
2005-04-05 18:47                           ` Juergen Kreileder
2005-04-05 22:32                           ` Jeremy Nickurak
2005-04-03 20:23                   ` Peter Osterlund
  -- strict thread matches above, loose matches on Subject: below --
2005-01-07 16:56 Aaron Gyes
     [not found] <3jlKa-2o0-29@gated-at.bofh.it>
     [not found] ` <3tQt7-cV-21@gated-at.bofh.it>
     [not found]   ` <3uhWj-6Tp-27@gated-at.bofh.it>
     [not found]     ` <3wDJ2-1jb-29@gated-at.bofh.it>
2005-03-05  7:16       ` Jeremy Nickurak
2005-03-06  6:01 Aaron Gyes
2005-03-06 20:32 ` Jeremy Nickurak

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=20050308205210.GA3986@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=b0ef@esben-stien.name \
    --cc=linux-kernel@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