Date: Mon, 24 Jun 1996 11:14:06 +0200 (MET DST) From: sos@freebsd.org To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: current@freebsd.org (FreeBSD current) Subject: Re: moused conflicts with X11 Message-ID: <199606240914.LAA06110@ra.dkuug.dk> In-Reply-To: <199606240851.SAA21550@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jun 24, 96 06:21:48 pm
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Michael Smith who wrote:
>
> Either we need a 'mouse' line discipline that allows multiple readers
> (erk.), or we look at something like the 'snp' device's hooks to provide
> moused with a means of watching the mouse without interfering with the
> X server.
Ahhh, how does this snp thingy work ?? (I'm too lazy to look in the sources)
Could it be used to snoop the bytestream from the "known" mousedevice ??
If so, that would be neat to have, just config the mousedev to syscons
via an ioctl, and there we go.... no moused no nothing (except that
I now need to make this a lkm due to the amount of code in syscons)....
> I don't think we can afford to change what the X server sees, and I don't
> like the way the Linux folks did it (their mouse daemon is basically a pipe).
My wiev exactly..
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
So much code to hack -- so little time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606240914.LAA06110>