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
On Fri, Oct 17, 2003 at 10:32:28PM -0400, David Dawes wrote:
>On Fri, Oct 17, 2003 at 02:15:20PM -0700, Tim Roberts wrote:
>>On Fri, 17 Oct 2003 23:44:57 +0300, Alexander Shopov wrote:
>>>
>>>I checked driver man pages in xc/programs/Xserver/hw/xfree86/drivers/*/*.man
>>>Almost every driver impleme
On Sat, Oct 18, 2003 at 08:30:05AM +0300, Alexander Shopov wrote:
>> Back to the original point, the documentation of these options in the
>> driver man pages should match how they are handled by the individual
>> drivers. Specifically, the documented defaults may legitimately be
>> different for
> 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 Sat, 18 Oct 2003, David Dawes wrote:
> On Sat, Oct 18, 2003 at 08:30:05AM +0300, Alexander Shopov wrote:
> >> Back to the original point, the documentation of these options in the
> >> driver man pages should match how they are handled by the individual
> >> drivers. Specifically, the document
