Hi,
currently, what I am doing for the raw kbd access in oskit-mach,
is to unconditionally open the direct console in a ds_direct_console_stream,
which might be identical to ds_console_stream if you don't use a serial
console to boot with.
Then, when opening "kbd" (only allowed read-only), then the keyboard is set
to raw mode.
My idea was to disable raw mode on a no senders notification. Problem is,
I can not really distinguish between "console" and "kbd" in the no-serial-
console-at-boot case. The best thing I came up with is to test if it is
really opened in read only mode ("console" is usually opened with "w" or
"rw"). This actually might work out to be enough to get it running.
One could add or steal a cheesy bit in the device structure that allows to make
the distinction.
For development, it would be nicer if I could "grab" the keyboard when
opening "kbd", but I am not sure that this is feasible. It would be nice
to interrupt all pending reads, or at least make all future reads from
the "console" block until "kbd" is closed. Is that feasible?
Of course the best way to develop is to use a serial line console to boot with,
because then the hw console is completely unused until you explicitely open
it. I will certainly do that, but having the other way is also convenient.
Thanks,
Marcus
_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
