From: Vojtech Pavlik <vojtech@suse.cz>
To: Greg Stark <gsstark@mit.edu>
Cc: mljf@altern.org, Maciej Soltysiak <solt@dns.toxicfilms.tv>,
Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: No mouse wheel under 2.6.1 [Was: Re: Where are 2.6.x upgrade notes?]
Date: Sun, 18 Jan 2004 00:18:52 +0100 [thread overview]
Message-ID: <20040117231852.GA13418@ucw.cz> (raw)
In-Reply-To: <87fzee1fcq.fsf@stark.xeocode.com>
On Sat, Jan 17, 2004 at 03:37:25PM -0500, Greg Stark wrote:
> Joaquim Fellmann <mljf@altern.org> writes:
>
> > I had the same problem. Switching protocol from MousemanPlusPS/2 to
> > ImPS2 in XF86Config-4 fixed it.
>
> One Mr Pavlik solved the same issue on bugzilla:
>
> ------- Additional Comment #1 From Vojtech Pavlik 2004-01-14 09:35 -------
> Use protocol "ExplorerPS/2" in XFree86. This may not seem logical, but
> because 2.6 handles the Logitech mouse protocol itself and presents a more
> common Microsoft-like protocol to applications that don't know how to use
> its native event protocol.
>
> I wonder how the IM and Explorer protocols relate.
ExplorerPS/2 is a superset of ImPS/2. The kernel virtual mouse device
(/dev/input/mice) supports both protocols, and standard PS/2 as well.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
prev parent reply other threads:[~2004-01-17 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 7:55 Where are 2.6.x upgrade notes? Greg Stark
2004-01-13 10:58 ` Maciej Soltysiak
2004-01-13 19:59 ` Dave Jones
2004-01-14 7:45 ` No mouse wheel under 2.6.1 [Was: Re: Where are 2.6.x upgrade notes?] Greg Stark
2004-01-14 7:51 ` Ralf Hildebrandt
2004-01-14 23:57 ` Thomas Molina
2004-01-17 15:20 ` Joaquim Fellmann
2004-01-17 20:37 ` Greg Stark
2004-01-17 23:18 ` Vojtech Pavlik [this message]
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=20040117231852.GA13418@ucw.cz \
--to=vojtech@suse.cz \
--cc=gsstark@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mljf@altern.org \
--cc=solt@dns.toxicfilms.tv \
/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).