From: Vojtech Pavlik <vojtech@suse.cz>
To: dtor_core@ameritech.net
Cc: Christoph Pleger <Christoph.Pleger@uni-dortmund.de>,
linux-kernel@vger.kernel.org
Subject: Re: Serial Mouse in Kernel 2.6
Date: Mon, 30 May 2005 16:09:02 +0200 [thread overview]
Message-ID: <20050530140902.GA1012@ucw.cz> (raw)
In-Reply-To: <d120d5000504290903758bc9f2@mail.gmail.com>
On Fri, Apr 29, 2005 at 11:03:24AM -0500, Dmitry Torokhov wrote:
> Hi,
>
> On 4/29/05, Christoph Pleger <Christoph.Pleger@uni-dortmund.de> wrote:
> > Hello,
> >
> > When configuring Kernel 2.6.11.7, I found under Input Devices two
> > options which seem to have to do with serial mouse support:
> >
> > 1. Serial line discipline (module serport)
> > 2. Serial Mouse support (module sermouse)
> >
> > Ic compiled both these features as a module. But after rebooting with
> > the new kernel, the serial mouse is working well with gpm and with X11,
> > although none of the above modules are loaded.
> >
> > So, what for are the modules mentioned above needed?
> >
>
> If you load the modules and use input_attach program to set up your
> mouse then you can access it via /dev/input/mice together with the
> rest of you mice, PS/2, USB, etc. This way you have only one input
> device for you mouse and do not have to change millions of programs
> (actually 2) if you happen to install a new mouse.
>
> You seem to still using the mouse by accessing /dev/ttySx port and
> using serial mouse driver.
You also get a much better update rate for the mouse than with X/GPM, 4x
for MouseSystems, and 2x for Microsoft mice. This makes the serial mouse
finally usable.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
prev parent reply other threads:[~2005-05-30 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 12:52 Serial Mouse in Kernel 2.6 Christoph Pleger
2005-04-29 16:03 ` Dmitry Torokhov
2005-04-29 16:21 ` Wakko Warner
2005-04-29 16:29 ` Dmitry Torokhov
2005-05-30 14:09 ` 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=20050530140902.GA1012@ucw.cz \
--to=vojtech@suse.cz \
--cc=Christoph.Pleger@uni-dortmund.de \
--cc=dtor_core@ameritech.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.