From: Gunther.Mayer@t-online.de (Gunther Mayer)
To: James Simmons <jsimmons@linux-fbdev.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: mouse problems in 2.4.2 -> lost byte
Date: Wed, 28 Mar 2001 20:21:31 +0200 [thread overview]
Message-ID: <3AC22BAB.6C500DAC@t-online.de> (raw)
In-Reply-To: Pine.LNX.4.31.0103280722310.948-100000@linux.local
James Simmons wrote:
>
> >Where can I get your driver?
>
> I attach it to the other posting to this thread. I also have it in CVS at
> http://linuxconsole.sourceforge.net with a bunch of other input drivers.
>
> >> Section "Pointer"
> >> Protocol "ImPS/2"
> >> Device "/dev/input/mice"
> >
> >What is better in using /dev/input/mice than /dev/psaux
> >on this problem exactly?
>
> The reason to use /dev/input/mice is the PS/2 mouse driver itself has not
^^^^^^^^^^^^^^^
So you recommend to connect the mouse to USB (instead of psaux) because
psaux+Xfree86 are losing bytes under circumstances (e.g. some load pattern).
This is a fine solution for users with dual protocol mice, but doesn't
resolve the problem for other poor ps/2 mouse owners !
> been ported over to the input suite for 2.4.X. You can use the above for
> the USB mouse now. Now if you have a USB mouse plus a PS/2 mouse then
> having both use /dev/psaux would require a reworking of the PS/2 driver.
> I rather port over the PS/2 mouse to use /dev/input/mice. I have done this
> for my CVS but since the PS/2 mouse shares the same chipset as the PS/2
> keyboard you have to use both input drivers. It would be better if XFree86
> would have a /dev/eventX driver but we would wait a long time for that to
> happen :-(
Even with PS/2 mouse support in the "new input" driver I wouldn't expect the
psaux-byte-lost bug to disappear magically.
-
Gunther
next prev parent reply other threads:[~2001-03-28 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-28 15:32 mouse problems in 2.4.2 -> lost byte James Simmons
2001-03-28 18:21 ` Gunther Mayer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-29 4:43 James Simmons
2001-03-29 3:47 James Simmons
2001-03-28 15:22 James Simmons
2001-03-27 20:29 James Simmons
2001-03-27 20:48 ` Gunther Mayer
2001-03-27 20:50 ` linas
2001-03-25 22:33 mouse problems in 2.4.2 linas
2001-03-27 20:15 ` mouse problems in 2.4.2 -> lost byte Gunther Mayer
2001-03-27 20:45 ` linas
2001-03-28 18:31 ` Gunther Mayer
2001-03-28 21:59 ` Vojtech Pavlik
2001-03-28 23:19 ` linas
2001-03-29 5:45 ` Vojtech Pavlik
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=3AC22BAB.6C500DAC@t-online.de \
--to=gunther.mayer@t-online.de \
--cc=jsimmons@linux-fbdev.org \
--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