>
> Vojtech Pavlik:
> o Fixes for keyboard 2.4 compatibility
>
Hi,
2.6.1-rc1 with JP106 keybord. keycode was changed....
2.6.0 -> 2.6.1-rc1
lower-right backslash (scancode 0x73) 89 -> 181
upper-right backslash (scancode 0x7d) 183 -> 182
at atkbd_set2_keycode in drivers/input/keyboard/atkbd.c
- 122, 89, 40,120, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0, 0,
+ 0,181, 40, 0, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0,194,
^ scancode 0x73
- 85, 86, 90, 91, 92, 93, 14, 94, 95, 79,183, 75, 71,121, 0,123,
+ 0, 86,193,192,184, 0, 14,185, 0, 79,182, 75, 71,124, 0, 0,
^ scancode 0x7d
Is this correct?
2.6.0 is OK, but 2.6.1-rc1 does not get [|/_] keys.
And more....
mae-kouho/henkan (scancode 0x79) 92 -> 184
mu-henkan (scancode 0x7b) 94 -> 185
- 85, 86, 90, 91, 92, 93, 14, 94, 95, 79,183, 75, 71,121, 0,123,
+ 0, 86,193,192,184, 0, 14,185, 0, 79,182, 75, 71,124, 0, 0,
^ 0x79 ^ 0x7b
These are input method control keys.
Go Taniguchi wrote:
>>
>> Vojtech Pavlik:
>> o Fixes for keyboard 2.4 compatibility
>>
>
> Hi,
> 2.6.1-rc1 with JP106 keybord. keycode was changed....
> 2.6.0 -> 2.6.1-rc1
> lower-right backslash (scancode 0x73) 89 -> 181
> upper-right backslash (scancode 0x7d) 183 -> 182
>
> at atkbd_set2_keycode in drivers/input/keyboard/atkbd.c
>
> - 122, 89, 40,120, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0, 0,
> + 0,181, 40, 0, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0,194,
> ^ scancode 0x73
>
> - 85, 86, 90, 91, 92, 93, 14, 94, 95, 79,183, 75, 71,121, 0,123,
> + 0, 86,193,192,184, 0, 14,185, 0, 79,182, 75, 71,124, 0, 0,
> ^ scancode 0x7d
> Is this correct?
> 2.6.0 is OK, but 2.6.1-rc1 does not get [|/_] keys.
On Fri, Jan 02, 2004 at 01:51:54PM +0900, Go Taniguchi wrote:
> >
> >Vojtech Pavlik:
> > o Fixes for keyboard 2.4 compatibility
> >
>
> Hi,
> 2.6.1-rc1 with JP106 keybord. keycode was changed....
> 2.6.0 -> 2.6.1-rc1
> lower-right backslash (scancode 0x73) 89 -> 181
> upper-right backslash (scancode 0x7d) 183 -> 182
These two scancodes are defined as japanese language selection keys.
Hence the atkbd.c driver delivers these as such. What should be updated
is the default keymap (defkeymap.map, defkeymap.c).
> at atkbd_set2_keycode in drivers/input/keyboard/atkbd.c
>
> - 122, 89, 40,120, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0, 0,
> + 0,181, 40, 0, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0,194,
> ^ scancode 0x73
>
> - 85, 86, 90, 91, 92, 93, 14, 94, 95, 79,183, 75, 71,121, 0,123,
> + 0, 86,193,192,184, 0, 14,185, 0, 79,182, 75, 71,124, 0, 0,
> ^ scancode 0x7d
> Is this correct?
> 2.6.0 is OK, but 2.6.1-rc1 does not get [|/_] keys.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
On Fri, Jan 02, 2004 at 02:46:07PM +0900, Go Taniguchi wrote:
> And more....
>
> mae-kouho/henkan (scancode 0x79) 92 -> 184
> mu-henkan (scancode 0x7b) 94 -> 185
>
> - 85, 86, 90, 91, 92, 93, 14, 94, 95, 79,183, 75, 71,121, 0,123,
> + 0, 86,193,192,184, 0, 14,185, 0, 79,182, 75, 71,124, 0, 0,
> ^ 0x79 ^ 0x7b
> These are input method control keys.
Again, this is per (microsoft [*]) specification. These keys should,
however, give the very same scancodes to X as they did on 2.4.
[*] I used this specification, because that's what the keyboard
manufacturers seem to follow recently.
> Go Taniguchi wrote:
> >>
> >>Vojtech Pavlik:
> >> o Fixes for keyboard 2.4 compatibility
> >>
> >
> >Hi,
> >2.6.1-rc1 with JP106 keybord. keycode was changed....
> > 2.6.0 -> 2.6.1-rc1
> >lower-right backslash (scancode 0x73) 89 -> 181
> >upper-right backslash (scancode 0x7d) 183 -> 182
> >
> >at atkbd_set2_keycode in drivers/input/keyboard/atkbd.c
> >
> >- 122, 89, 40,120, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0, 0,
> >+ 0,181, 40, 0, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0,194,
> > ^ scancode 0x73
> >
> >- 85, 86, 90, 91, 92, 93, 14, 94, 95, 79,183, 75, 71,121, 0,123,
> >+ 0, 86,193,192,184, 0, 14,185, 0, 79,182, 75, 71,124, 0, 0,
> > ^ scancode 0x7d
> >Is this correct?
> >2.6.0 is OK, but 2.6.1-rc1 does not get [|/_] keys.
>
--
Vojtech Pavlik
SuSE Labs, SuSE CR
>>Hi,
>>2.6.1-rc1 with JP106 keybord. keycode was changed....
>> 2.6.0 -> 2.6.1-rc1
>>lower-right backslash (scancode 0x73) 89 -> 181
>>upper-right backslash (scancode 0x7d) 183 -> 182
>
>
> These two scancodes are defined as japanese language selection keys.
> Hence the atkbd.c driver delivers these as such. What should be updated
> is the default keymap (defkeymap.map, defkeymap.c).
>
Thank you so much.
I try so that it can be solved.
> What should be updated is the default keymap (defkeymap.map, defkeymap.c).
Sorry, does this mean that a default key map is re-defined?
We need to add 181 and 182 keycodes to the keymap?
Thanks again.
On Sat, Jan 03, 2004 at 04:01:41AM +0900, Go Taniguchi wrote:
> >>Hi,
> >>2.6.1-rc1 with JP106 keybord. keycode was changed....
> >> 2.6.0 -> 2.6.1-rc1
> >>lower-right backslash (scancode 0x73) 89 -> 181
> >>upper-right backslash (scancode 0x7d) 183 -> 182
> >
> >
> > These two scancodes are defined as japanese language selection keys.
> > Hence the atkbd.c driver delivers these as such. What should be updated
> > is the default keymap (defkeymap.map, defkeymap.c).
> >
>
> Thank you so much.
> I try so that it can be solved.
> > What should be updated is the default keymap (defkeymap.map, defkeymap.c).
> Sorry, does this mean that a default key map is re-defined?
> We need to add 181 and 182 keycodes to the keymap?
Exactly so.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
--- linux-2.6.1-rc1/drivers/input/keyboard/atkbd.c.orig 2004-01-03 14:05:19.000000000 +0900
+++ linux-2.6.1-rc1/drivers/input/keyboard/atkbd.c 2004-01-03 13:43:30.000000000 +0900
@@ -50,7 +50,7 @@
static unsigned char atkbd_set2_keycode[512] = {
0, 67, 65, 63, 61, 59, 60, 88, 0, 68, 66, 64, 62, 15, 41,117,
- 0, 56, 42,182, 29, 16, 2, 0, 0, 0, 44, 31, 30, 17, 3, 0,
+ 0, 56, 42,170, 29, 16, 2, 0, 0, 0, 44, 31, 30, 17, 3, 0,
0, 46, 45, 32, 18, 5, 4,186, 0, 57, 47, 33, 20, 19, 6, 85,
0, 49, 48, 35, 34, 21, 7, 89, 0, 0, 50, 36, 22, 8, 9, 90,
0, 51, 37, 23, 24, 11, 10, 0, 0, 52, 53, 38, 39, 25, 12, 0,