> I was under the impression that the kernel would/should at least always see
> the raw scancode (where this is not a value between 0 and 255), whether or
> not it could do something with it, and that X didn't use linux's keyboard
> driver anyway, it interpreted the scancodes itself.
You are mi
On Fri, Oct 17, 2003 at 07:56:45PM -0400, Sheldon Lee-Wen wrote:
> I was under the impression that the kernel would/should at least always see
> the raw scancode (where this is not a value between 0 and 255)
Your impression is incorrect.
The raw scancode is a byte and cannot be a value outside 0
I was under the impression that the kernel would/should at least always see
the raw scancode (where this is not a value between 0 and 255), whether or
not it could do something with it, and that X didn't use linux's keyboard
driver anyway, it interpreted the scancodes itself. So if the kernel it
On Fri, Oct 17, 2003 at 03:52:00PM -0400, Sheldon Lee-Wen wrote:
> Pardon my evilness in cross posting this, But I need to get a discussion going
> on how to resolve this problem.
>
> One lineak user went and tested his keyboard. Here is what he got. It does
> appear that for the keys that do n
