[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [patch] direct console set_status
From: |
Roland McGrath |
Subject: |
Re: [patch] direct console set_status |
Date: |
Thu, 18 Oct 2001 15:36:41 -0400 (EDT) |
That may be a good interim kludge, but I am not going to include it.
A better interim kludge would be to give oskit-mach a cheezy "kbd" device
that sets DC_RAW while it's open and resets it when it's closed. Then you
would use that instead of "console" as the device to read scancodes from.
When "console" is a serial console, there is no reason it should be
involved with the keyboard hardware at all and you'd still like another
device you can open to access it. (In fact, I would think that this would
be by far the easiest way to debug your user-space console code: boot with
a serial console and leave the PC keyboard/display purely for your debugging.)
The real solution is to add a real keyboard (and ps2) driver to oskit.