Date: Mon, 2 Sep 1996 00:35:03 +0200 (MET DST) From: sos@FreeBSD.org To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Cc: sos@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/i386/isa syscons.c syscons.h Message-ID: <199609012235.AAA00230@DeepCore.dk> In-Reply-To: <199609011940.XAA00804@nagual.ru> from "[______ ______]" at "Sep 1, 96 11:40:16 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to [______ ______] who wrote:
> > sos 96/09/01 11:16:08
> >
> > Branch: sys/i386/isa 1.100
> > Modified: sys/i386/isa syscons.c syscons.h
> > Log:
> > Fixed a couple of bugs in the mousepointer code.
>
> Is it work now with X?
Well, as good as it did before :), there still is the problem with
both moused & X using the same mouse device. This will only be
fixed when we move to a generic mouse interface that "knows" who
should be using the mouse of a given vty, or that I make syscons
mimic a mouse on a minor device that X could use (that would be
a hack, but it would work and give us a generic mouseinterface).
Maybe its time for a mouse device driver (easy to do, just
make moused into a devicedriver and design an interface that
syscons can use).
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
Even more code to hack -- will it ever end
..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609012235.AAA00230>