Subject: Re: On wscons, mice, and keyboards
To: Lennart Augustsson <firstname.lastname@example.org>
From: Chris G. Demetriou <email@example.com>
Date: 07/27/1998 16:10:01
Lennart Augustsson <firstname.lastname@example.org> writes:
> You could argue that the mouse protocol decoding should be
> done in the X server (as it partly is today) rather than in
> the kernel, but the current NetBSD trend is to move that to
> the kernel.
I don't think that that's the current NetBSD trend. There's an
in-kernel mouse interface, and it's used for certain things (namely,
mice which logically fit in as device drivers; not generic serial
mice, but rather mice which have dedicated hardware and a dedicated
That doesn't mean that, say, all serial mouse handling should be
thrown into the kernel.
> I think this situation is similar. Yes, the X
> server could try and open /dev/wmsN (with N = 0 .. 15 say)
> regularely, and take care of new devices that show up.
Not "should try to"... Should be configurable so that it can try to,
if the user wants it (and only then).