Messages in this thread | | | Date | Thu, 25 Dec 2003 15:21:43 GMT | From | John Bradford <> | Subject | Re: handling an oddball PS/2 keyboard |
| |
Quote from David Monro <davidm@amberdata.demon.co.uk>: > John Bradford wrote: > >>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 :-) ). > > I will definitely explore this possibility. Whats the ID of your > keyboard? (and what is it?)
It's an IBM Japanese keyboard which emulates a U.S. one. Andries has quite a bit of information about it on his page, but the interesting thing is that it doesn't do any emulation in set 3, only in the default set 2. The ID is ab90. There may be ab90 ID keyboards out there which are not set 3 compatible, I don't know. Mine is certainly not fully usable in set 2, though, as the language keys produce the same codes as the space bar.
John. - 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/
| |