From: Vojtech Pavlik <vojtech@suse.cz>
To: John Bradford <john@grabjohn.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
tomita@cinet.co.jp, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5.59] support japanese JP106 keyboard on new console.
Date: Sun, 2 Feb 2003 11:47:57 +0100 [thread overview]
Message-ID: <20030202114757.B4180@ucw.cz> (raw)
In-Reply-To: <200302021038.h12AcLKm000228@darkstar.example.net>; from john@grabjohn.com on Sun, Feb 02, 2003 at 10:38:21AM +0000
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
next prev parent reply other threads:[~2003-02-02 10:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 3:14 [PATCH 2.5.59] support japanese JP106 keyboard on new console Hiroshi Miura
2003-01-24 5:57 ` Vojtech Pavlik
2003-01-24 17:03 ` Osamu Tomita
2003-01-25 10:33 ` Vojtech Pavlik
2003-01-25 10:51 ` John Bradford
2003-01-25 11:01 ` Vojtech Pavlik
2003-01-25 13:10 ` John Bradford
2003-01-25 13:15 ` Vojtech Pavlik
2003-01-25 17:20 ` Set2 scancodes for Japanese keyboard John Bradford
2003-01-25 17:28 ` [Corrected] " John Bradford
2003-01-25 17:30 ` Vojtech Pavlik
2003-01-25 17:37 ` John Bradford
2003-01-25 17:40 ` Vojtech Pavlik
2003-01-25 17:46 ` John Bradford
2003-01-25 19:48 ` Andries Brouwer
2003-01-25 19:54 ` Vojtech Pavlik
2003-01-27 16:35 ` Set3 " John Bradford
2003-01-25 15:29 ` [PATCH 2.5.59] support japanese JP106 keyboard on new console Osamu Tomita
2003-01-25 15:36 ` Vojtech Pavlik
2003-01-24 17:17 ` Osamu Tomita
2003-02-01 1:54 ` Hiroshi Miura
2003-02-02 8:23 ` Vojtech Pavlik
2003-02-02 10:38 ` John Bradford
2003-02-02 10:47 ` Vojtech Pavlik [this message]
2003-02-05 3:36 ` Hiroshi Miura
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030202114757.B4180@ucw.cz \
--to=vojtech@suse.cz \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomita@cinet.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.