Messages in this thread | | | Date | Tue, 1 Jun 2004 13:31:13 +0200 | From | Pavel Machek <> | Subject | Re: keyboard problem with 2.6.6 |
| |
Hi!
> >>>>> "Giuseppe" == Giuseppe Bilotta <bilotta78@hotpop.com> writes: > > Giuseppe> So, while we wait for complete support, at the kernel > Giuseppe> level, for all the multimedia keyboards supported by X, > Giuseppe> we *need* proper raw mode. > > My question is: why do everything inside the kernel? > > > Even 'khttpd' has been removed from the kernel, because the same > efficiency has been achieved in the *userland* apache module. Why is > the input layer moving _backwards_? > > I don't think converting between keyboard/mouse protocols and the > input system's "struct input_event" has a tighter real-time > requirement than a heavily loaded web server. How many keys per > second can you type at? (Even if you type extremely fast and the > hardware constraints (velocity, etc.) are not reached yet, there is > still a limit that the keyboard controller, e.g. i8042, cannot > exceed.) How many mouse movements are you making per second? Is a > userland driver unable to handle that data rate? (I don't think so. > I believe enve a 386-DX 33MHz can handle it with ease.) If not, then > please do it in userland, so as not to waste kernel memory (which is > *NON-swappable*).
It would be nice to have keyboard in kernel because that means keyboard works even on heavilly overloaded system, in case of oops etc. (Unfortunately steps back were already taken; console switching is no longer so robust w.r.t. kernel crashes :-( ).
Are you able to provide accurate timestamps for input events from userland? 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/
| |