lkml.org 
[lkml]   [2003]   [Feb]   [2]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateSun, 2 Feb 2003 11:47:57 +0100
FromVojtech Pavlik <>
SubjectRe: [PATCH 2.5.59] support japanese JP106 keyboard on new console.
On Sun, Feb 02, 2003 at 10:38:21AM +0000, John Bradford wrote:
> > > Hiragana_Katakana was not defined before and I want to define a
> > > keycode point. 
> > > When I saw 2.4.20 pc_keyb.c source, I found all keycode below 127
> > > was used, then there is no room. But the comment tell me I can use
> > > 120-123, 125-127 with Japanese keyboard because these are not used
> > > on JP89/109 keyboards.
> > > (124 is, as you know, Yen key)  THese are defined for a latin
> > > keyboards.  So I use 120. 
> > > 
> > > How do you think about it?
> > 
> > In 2.4 you can, in 2.5 the 'as long as no duplication occurs for any
> > single keyboard' is not valid anymore, and the keycode for
> > hiragana/katakana is defined to be 183 I think.
> 
> We assigned 182 to hiragana/katakana for set 3 in 2.5, and left 183
> undefined.  Should we change the 2.5 keycode to 183?

No - just bad memory on my side, it might as well be 183. ;)

-- 
Vojtech Pavlik
SuSE Labs
-
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/

\
 
 \ /
  Last update: 2005-03-22 12:32    [from the cache]
©2003-2008