lkml.org 
[lkml]   [2004]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: keyboard problem with 2.6.6
Hi!

> >> >> What I hate is only the part where mouse/keyboard drivers
> >> >> are now in kernel space. The translation of raw byte
> >> >> streams into input events should be better done in userland.
> >> >> One important argument is: userland program may be swapped
> >> >> out. Kernel modules can't.
> >>
>
> Vojtech> Well, keyboard support was always in the kernel
>
> Once in kernel space, forever in kernel space? What's the logic?
>
> Where it is now possible to move it out of kernel space WITHOUT
> performance problems, why not move it out?

You get pretty nasty managment problems. How do you do init=/bin/bash
if your keyboard is userspace?

> Vojtech> But still, if you have a working keyboard, the handling
> Vojtech> is done in the kernel, and you can do a register dump,
> Vojtech> process listing, etc, even when the system is
> Vojtech> crashed.
>
> Why just the keyboard? For that purpose, we can use mouse buttons,
> the power button, a joystick button, or even a home-brewed button
> connected to the RS232 port or parallel port. Why *limit* that to the
> keyboard?

Keyboard is historically used for that. It seems to work, no reason to
change it.

Pavel
--
934a471f20d6580d5aad759bf0d97ddc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:03    [W:0.095 / U:0.144 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site