Date: Fri, 15 Jan 1999 23:58:26 +1000 (EST) From: Q <q@fan.net.au> To: freebsd-hackers@FreeBSD.ORG Subject: Console driver mouse support chewing cycles/interrupts Message-ID: <Pine.BSF.4.05.9901152358001.18367-100000@kermit.fan.net.au>
next in thread | raw e-mail | index | archive | help
I have written a driver under FreeBSD 3.0 for an Infra-Red receiver I
have, the receiver is serial port based, and the driver itself is
interrupt driven.
When receiving a signal, interrupts are generated quite rapidly
(20-30 ints @ 600-2400usec apart). When receiving a repeat code (from my
test remote) the interupts are at approx 9Hz. Timing is calculated in the
kernel driver the moment the interrupt handler is called.
All these signals are decoded by a daemon process and passed on to
socket connected clients. All this works perfectly under X and while the
remote is in signal range I haven't been able to fault the decoder. I have
written (and been using) a remote controlled mouse emulator that uses
the syscons mouse interface to control my X session. All fine so far.
The problem:
When I jump out of X to the console I have all sorts of problems (when the
mouse cursor is visible). I am using the default spiffy little mouse
pointer, not a square block. When controlling the mouse on the console
(remotely or with a real mouse), moving the mouse with no output going to
the console will cause some delayed interrupts with almost every movement
of the mouse, more if additional output is displayed on the console in the
process.
Is this the price you pay for having mouse support on the console or is
there something missing from the mouse support portion of the console
driver that should handle things better?
Seeya...Q
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
_____ / Quinton Dolan - q@fan.net.au
__ __/ / / __/ / / Systems Administrator
/ __ / _/ / / Fast Access Network
__/ __/ __/ ____/ / - / Gold Coast, QLD, Australia
_______ / Ph: +61 7 5574 1050
\_\ SAGE-AU Member
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9901152358001.18367-100000>