From: linas@linas.org
To: jsimmons@linux-fbdev.org (James Simmons)
Cc: Gunther.Mayer@t-online.de (Gunther Mayer),
linas@linas.org,
linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: mouse problems in 2.4.2 -> lost byte
Date: Tue, 27 Mar 2001 14:50:21 -0600 (CST) [thread overview]
Message-ID: <20010327205021.291411B7A5@backlot.linas.org> (raw)
In-Reply-To: <Pine.LNX.4.31.0103271226140.847-100000@linux.local> from "James Simmons" at Mar 27, 2001 12:29:28 PM
It's been rumoured that James Simmons said:
>
>
> >This is easily explained: some byte of the mouse protocol was lost.
> >(Some mouse protocols are even designed to allow
> >easy resync/recovery by fixed bit patterns!)
> >
> >Write an intelligent mouse driver for XFree86 to compensate for
> >lost bytes.
>
> Or write a kernel input device driver. In fact I probable have a mouse
> driver for you. What kind of mouse do you have?
logitech trackman marble wheel.
send me the driver. Are you working on getting the thing incorporated
into xf86? should I pester someone over there about it? should I assume
that 'everything will be OK', if I wait long enough?
--linas
next prev parent reply other threads:[~2001-03-27 20:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 20:29 James Simmons
2001-03-27 20:48 ` Gunther Mayer
2001-03-27 20:50 ` linas [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:32 James Simmons
2001-03-28 18:21 ` Gunther Mayer
2001-03-28 15:22 James Simmons
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=20010327205021.291411B7A5@backlot.linas.org \
--to=linas@linas.org \
--cc=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
all inboxes | Powered by JetHome®