From: brian@worldcontrol.com
To: linux-kernel@vger.kernel.org
Subject: Known bugs in 2.4.6 serial driver?
Date: Fri, 27 Jul 2001 02:43:41 -0700 [thread overview]
Message-ID: <20010727024341.A2169@top.worldcontrol.com> (raw)
I just found on my laptop that using the serial port interferes
with the mouse pointer.
My mouse is on /dev/psaux (PS/2 style) and my serial port is on
/dev/ttyS0.
At first I figure it was my app. But then I found similar behavior
while running a similar app in vmware under Windows 98. I.E.
when the windows app used the serial port via vmware, the mouse
pointer went all haywire whether its was focused in vmware or
elsewhere.
My PS/2 mouse is on irq 12, will the serial port is in irq 4
like it is supposed to be.
My app makes extensive use of tcdrain, read, and write while
more or less in raw mode on the serial port.
My app also works fine so long as I don't move the mouse while
it is running.
Anyone heard of something similar? Or is their an error in
the design of my laptop?
--
Brian Litzinger <brian@worldcontrol.com>
Copyright (c) 2000 By Brian Litzinger, All Rights Reserved
reply other threads:[~2001-07-27 9:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010727024341.A2169@top.worldcontrol.com \
--to=brian@worldcontrol.com \
--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