From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: random moving of cursor arrow
Date: Mon, 28 Jul 2003 07:26:59 +0200 [thread overview]
Message-ID: <20030728072659.B1666@cackle.proxima.alt.za> (raw)
In-Reply-To: <c63b4460a0a3df15255d0f743486c75e@plan9.bell-labs.com>; from David Presotto on Fri, Jul 25, 2003 at 10:22:10PM -0400
On Fri, Jul 25, 2003 at 10:22:10PM -0400, David Presotto wrote:
>
> I'll bang at serial ports tomorrow and see if I can figure out what's happening.
> With modern machines, I shouldn't get overruns even without the fifo. I used
> to avoid the fifo for mice because it made the mouse jerky.
>
Note that (in my recollection) the problem is more recent than the
switch to the new driver. I have only recently migrated to an
Intellimouse and then only on my workstation and the impression I
get is that there has been a slowdown in the very recent past. It
would be difficult for me to test this, but if we come up with no
other option, I can set up a test bench.
> Everything related has changed of course; uart driver, clock routine, and
> scheduler. Any could be at fault. I'll plug some machines back to back and
> see if I can cause overruns. A mouse really shouldn't be able to though,
> it's only 9600 baud or less. If we're missing, something is really
> screwed up. We only use ps2 mice these days but I can scrounge up some
> serial ones.
>
I have only examined the actual driver. I couldn't see anything
clearly suspicious in it.
> It is true that if the mouse is misidentified, it will cause exactly the
> behavior babic is seeing, i.e., if it guesses the wrong protocol.
Yes, but then echo i1 > /dev/eia0ctl wouldn't have any ameliorating
effect on it.
++L
next prev parent reply other threads:[~2003-07-28 5:26 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 8:52 [9fans] " sasa
2003-07-25 8:43 ` Lucio De Re
2003-07-26 15:59 ` David Presotto
2003-07-26 16:40 ` Dan Cross
2003-07-26 16:44 ` David Presotto
2003-07-26 17:10 ` Skip Tavakkolian
2003-07-26 17:14 ` Dan Cross
2003-07-26 17:19 ` rob pike, esq.
2003-07-26 17:23 ` boyd, rounin
2003-07-28 9:00 ` matt
2003-07-26 17:10 ` boyd, rounin
2003-07-28 5:48 ` Lucio De Re
2003-07-25 9:02 ` boyd, rounin
2003-07-25 9:01 ` Lucio De Re
2003-07-25 9:08 ` Fco.J.Ballesteros
2003-07-25 14:08 ` Scott Schwartz
2003-07-25 14:35 ` UART device driver (Was: [9fans] random moving of cursor arrow) Lucio De Re
2003-07-25 14:56 ` boyd, rounin
2003-07-26 5:50 ` jmk
2003-07-28 5:36 ` Lucio De Re
2003-07-25 9:17 ` [9fans] Re: random moving of cursor arrow sasa
2003-07-25 9:24 ` sasa
2003-07-25 9:25 ` sasa
2003-07-25 9:27 ` boyd, rounin
2003-07-26 2:22 ` David Presotto
2003-07-26 8:37 ` C H Forsyth
2003-07-26 8:51 ` boyd, rounin
2003-07-28 8:47 ` Douglas A. Gwyn
2003-07-26 15:37 ` David Presotto
2003-07-26 9:59 ` Enache Adrian
2003-08-07 13:52 ` David Presotto
2003-07-26 19:01 ` Richard Miller
2003-07-28 5:26 ` Lucio De Re [this message]
2003-07-28 6:18 ` Lucio De Re
2003-07-29 3:11 ` David Presotto
2003-07-25 10:27 ` sasa
2003-08-07 14:35 David Presotto
2003-08-08 21:14 ` Enache Adrian
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=20030728072659.B1666@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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).