Date: Sat, 16 Jan 1999 01:01:26 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Q <q@fan.net.au> Cc: freebsd-hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Console driver mouse support chewing cycles/interrupts Message-ID: <199901151601.BAA26821@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Fri, 15 Jan 1999 23:58:26 %2B1000." <Pine.BSF.4.05.9901152358001.18367-100000@kermit.fan.net.au> References: <Pine.BSF.4.05.9901152358001.18367-100000@kermit.fan.net.au>
next in thread | previous 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. [...] >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 I am afraid yes ;-< The current version of syscons draws the mouse pointer by manipulating font data. This takes time and may cause interrupt delay. Kazu >is >there something missing from the mouse support portion of the console >driver that should handle things better? 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?199901151601.BAA26821>