Eduardo Horvath wrote:

> One problem with wscons is that it's an all-or-nothing device: either
>
>it has control of both input and output or it is unusable.  If you have
>a wscons-enabled keyboard, you also need a wscons-enabled output device
>or the input will go nowhere.
>  
>
I don't believe that's true.  If the wskbd does not belong to the 
console you
can just open /dev/wskbd[N] and process the events as you see fit.
One possibility would be to inject them into /dev/console (if TIOCSTI works
for /dev/console).

    -- Lennart