public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Erik Steffl <steffl@bigfoot.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: logitech mouseMan wheel doesn't work with 2.6.5
Date: Thu, 3 Jun 2004 01:39:18 +0200	[thread overview]
Message-ID: <20040602233918.GA1366@ucw.cz> (raw)
In-Reply-To: <4090A1FA.1070202@bigfoot.com>

On Wed, Apr 28, 2004 at 11:34:34PM -0700, Erik Steffl wrote:
> Dmitry Torokhov wrote:
> >On Wednesday 28 April 2004 01:47 pm, Erik Steffl wrote:
> >>Dmitry Torokhov wrote:
> >>
> >>>What protocol are you using in XFree?
> >>
> >>  that's irrelevant, I got the results above without X running (by 
> >
> >No, it is not. Please change protocol in XF86Config to ExplorerPS/2.
> ...
> >Kernel only provides emulation of 3 protocols via /dev/psaux: bare PS/2,
> >IntelliMouse PS/2 and Explorer PS/2. Since your program does not issue
> >Intellimouse or Explorer protocol initialization sequences it gets just
> >bare PS/2 protocol data - 2 axis, 3 buttons. Extra buttons are mapped onto
> >first 3. For exact mapping consult drivers/input/mousedev.c
> 
>   thanks, that makes sense, I tried ExplorerPS/2, it works better, the 
> wheel works but side button is still same as button 2.
> 
>   would it be different if I used /dev/input/mouse0? or 
> /dev/input/mice?  kernel Documentation/input/input.txt seems to be 
> fairly old (mentions  2.5/2.6 in future tense) and it says to use 
> "ExplorerPS/2 if you want to use extra (up to 5) buttons" when 
> discussing what /dev/input/mouse0 provides. Does that mean that there's 
> no way to use extra side button (which is the sixth button)?

Yes, at this time you can't use the sixth button in X with a 2.6 kernel.
An event driver for X would be needed instead of the ExplorerPS/2 one.

-- 

  reply	other threads:[~2004-06-02 23:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20 14:14 logitech mouseMan wheel doesn't work with 2.6.5 Erik Steffl
2004-04-20 15:22 ` Paul Rolland
2004-04-20 15:36   ` Craig Bradney
2004-04-20 18:14     ` Kim Holviala
2004-04-20 19:06     ` Erik Steffl
2004-04-20 20:18       ` Craig Bradney
2004-04-20 19:03   ` Erik Steffl
2004-04-20 20:26 ` Kim Holviala
2004-04-20 23:31   ` Erik Steffl
2004-04-20 23:41     ` Randy.Dunlap
2004-04-24  7:27   ` Erik Steffl
2004-04-24  8:41     ` Craig Bradney
2004-04-27 23:18     ` Erik Steffl
2004-04-27 23:29       ` Craig Bradney
2004-04-27 23:56         ` Erik Steffl
2004-04-28  7:13           ` Craig Bradney
2004-04-28  7:22             ` Kim Holviala
2004-04-28  8:21               ` Erik Steffl
2004-04-28  8:36                 ` Craig Bradney
2004-04-28 12:41                 ` Dmitry Torokhov
2004-04-28 18:47                   ` Erik Steffl
2004-04-28 23:24                     ` Dmitry Torokhov
2004-04-29  6:34                       ` Erik Steffl
2004-06-02 23:39                         ` Vojtech Pavlik [this message]
     [not found] <1N4qh-4Ct-13@gated-at.bofh.it>
2004-04-21 16:08 ` Frank Otto

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=20040602233918.GA1366@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steffl@bigfoot.com \
    /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