Date: Thu, 19 Feb 1998 00:25:34 +1100 From: David Dawes <dawes@rf900.physics.usyd.edu.au> To: Terry Lambert <tlambert@primenet.com> Cc: sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: devfs persistence Message-ID: <19980219002534.43748@rf900.physics.usyd.edu.au> In-Reply-To: <199802172325.QAA07146@usr09.primenet.com>; from Terry Lambert on Tue, Feb 17, 1998 at 11:25:39PM %2B0000 References: <22612.887749938@verdi.nethelp.no> <199802172325.QAA07146@usr09.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 17, 1998 at 11:25:39PM +0000, Terry Lambert wrote: >> > > - ln -s cuaa0 mouse >> > >> > This is somewhat non-sensical as well. The mouse should use a protocol >> > virtualizer so that a /dev/mouse is reexported, and it doesn't matter >> > what your physical mouse hardware is, the thing looks like a mousesystems >> > (or other) mouse, always, so that programs don't have to care about this. >> >> Sure. But that makes XFree86 dependent on the mouse protocol virtualizer >> also. Do you want to introduce more dependencies? (Just playing the >> devil's advocate here.) > >Ask David Dawes. XFree86 already does this; it had to for SVR4. Yes, the original XFree86 development started on SVR4, and it had support for that from day one (they called it xqueue, and it provides asynchronous delivery of keyboard and mouse events). The SysMouse format available with the improved mouse support that Kazu has been working on pretty much does the protocol virtualisation, doesn't it? Future releases of XFree86 will include support for the new FreeBSD mouse code. I'd love to be able to take all of the protocol-specific code out of XFree86, but not enough OSs do this protocol virtualisation. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980219002534.43748>