>> Perhaps nothing.  If someone has an X server ddx layer that reads
>> input events from wskbd/wsmouse, it may be comparatively easy to rip
>> the input event code out of that and slap it into my hw/next code in
>> place of the /dev/nk interface.
> Well, you might have to move some code around in the X server, but
> it's there.

Not for the values of "the X server" I was working with (which was the
X11 R6.4 patchlevel 3 code), not as far as I could tell.

> You can also mux kbd and ms into a single stream if you prefer.  The
> wsevent stuff isn't hard to use.

Perhaps not, once you know how to use it.  At the time I did the X work
this thread started with, I found nothing of any use by way of
documentation on how to get input events through wscons.  I would
certainly hope this situation has improved in -current, but I haven't
looked (no incentive to do so).

> Adding another way of doing the same thing seems like a waste. :)

A waste of what?  It looked like the quickest way to get something
working (and I suspect it was).  I figured someone who actually knows
something about wscons could glue on a wscons input event layer if such
a thing were ever desired.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B