Re: handling an oddball PS/2 keyboard

[John Bradford]

> I suppose Vojtech will have no objections to using this ID
> to skip the tests for e0 and e1 as protocol (escape) scancodes.

There might be no need for such a workaround - a lot of PS/2 devices
which were not intended for PCs work fine in set 3, particularly if
the device they were intended to work with uses set 3 natively, where
this conflict with protocol scancodes problem doesn't exist.  If the
keyboard works in set 3, add 0xab85 to the list of keyboards to force
set 3 for, (and maybe also add the ID for my keyboard while we're at
it :-) ).

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