From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, Marko Macek <Marko.Macek@gmx.net>,
Jesper Juhl <juhl-lkml@dif.dk>, Eric Wong <eric@yhbt.net>
Subject: Re: KVM & mouse wheel
Date: Wed, 4 Aug 2004 09:18:42 +0200 [thread overview]
Message-ID: <20040804071842.GA705@ucw.cz> (raw)
In-Reply-To: <200408040025.20118.dtor_core@ameritech.net>
On Wed, Aug 04, 2004 at 12:25:19AM -0500, Dmitry Torokhov wrote:
> On Tuesday 03 August 2004 11:29 pm, Marko Macek wrote:
> > Jesper Juhl wrote:
> >
> > > <>I also had problems with my KVM switch and mouse when I initially
> > > moved to
> > > 2.6, but adding this kernel boot parameter fixed it, meybe it will help
> > > you as well : psmouse.proto=imps
> >
> > This doesn't help. Only the patch I sent helps me. The problem is that the
> > even with psmouse.proto=imps or exps, the driver still probes for
> > synaptics which I
> > consider a bug.
> >
>
> No it is not - Synaptics with a track-point on a passthrough port will have
> track-point disabled if it is not reset after probing for imps/exps.
Hmm, does the imps/exps probe succeed in this case?
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-08-04 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 15:26 KVM & mouse wheel Marko Macek
2004-08-03 17:53 ` Dmitry Torokhov
2004-08-03 19:36 ` KVM & mouse wheel [was PATCH] Marko Macek
2004-08-03 19:42 ` KVM & mouse wheel Marko Macek
2004-08-03 23:14 ` David Ford
2004-08-03 21:02 ` Jesper Juhl
2004-08-04 4:29 ` Marko Macek
2004-08-04 5:25 ` Dmitry Torokhov
2004-08-04 7:18 ` Vojtech Pavlik [this message]
2004-08-04 12:38 ` Dmitry Torokhov
2004-08-04 12:56 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2004-08-04 17:41 Dmitry Torokhov
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=20040804071842.GA705@ucw.cz \
--to=vojtech@suse.cz \
--cc=Marko.Macek@gmx.net \
--cc=dtor_core@ameritech.net \
--cc=eric@yhbt.net \
--cc=juhl-lkml@dif.dk \
--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