On Sat, Feb 08, 2003 at 09:31:17PM +1100, Brad Hards wrote: > On Sat, 8 Feb 2003 16:12, Zephaniah E. Hull wrote: > > I don't see any way to tell the kernel that the keyboard events should > > not also be sent to through the console layer, which means, for > > instance, that hitting alt-F1 on the USB keyboard both gives the event > > to X, and then switches the console. > > > > Without that piece, things are not overly usable, and I'm not sure how > > to fix the problem. > We can go back to adding in the compile-time option for keyboard support, and > not compile the keyboard driver. Of course, then we have to have X to have > any keyboard support at all. > > Has to be a better way than that. > > Maybe we can do something hideous with the keyboard mapping on the keyboard > driver, to map it to something that gets ignored. > > I'd like a cleaner solution though.
Something comes to mind, but to be blunt it is still a hack, and it
could easily result in a system with no keyboard at all if X crashes.
Throw in a fake event, that tells the keyboard driver to ignore
everything from that input device until it receives the command again
with a different value.
I don't really like it, but at the same time I don't see anything overly
better.
(One might argue that this event might be sent when the device is
opened, which would have some pros, and some cons. The biggest would be
that running evtest on your only keyboard device would kill your console
until you can ssh over and kill the evtest.)
Zephaniah E. Hull.
>
> Brad
>
--
1024D/E65A7801 Zephaniah E. Hull <[EMAIL PROTECTED]>
92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801
CCs of replies from mailing lists are requested.
Hey, if you've mlock'ed more than your available memory, there's nothing
the VM layer can do. Except maybe a nice printk("Kiss your *ss goodbye");
-- Linus
msg00486/pgp00000.pgp
Description: PGP signature
