From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Hiroshi Miura <miura@da-cha.org>
Cc: ndiamond@wta.att.ne.jp, linux-kernel@vger.kernel.org,
vojtech@suse.cz, junkio@cox.net
Subject: Re: Japanese keyboards broken in 2.6
Date: Thu, 24 Jul 2003 23:26:31 +0900 [thread overview]
Message-ID: <87n0f4j90o.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <3F1FBFFC.9050305@da-cha.org>
Hiroshi Miura <miura@da-cha.org> writes:
> I can use Japanese keyboard.
> I DO recompile console-tools with header file in linux-2.5/2.6.
> Because of NR_KEYS change, as Ogawa-san said,
> in 2.4 NR_KEYS=128, in 2.6 NR_KEYS= 0x200
>
> When recompile, some tools fails compile on linux-2.6,
> but 'loadkeys' compiles nicely.
>
> Instantly, user can set new keymap to use a recompiled loadkey command.
>
> BTW, Ogawa-san's patch is needed?
For example, in loadkeys.y
if ((keymap_was_set[i])[j])
{
ke.kb_index = j;
ke.kb_table = i;
ke.kb_value = (key_map[i])[j];
ke.kb_index overflowed. Likewise dumpkeys has same problem.
And debian using in init.d/console-screen.sh,
dumpkeys < ${DEVICE_PREFIX}1 |sed -f /etc/console-tools/remap |loadkeys
Important part of my patch is the following. Other part was for
backward compatible.
+struct kbentry {
+ unsigned int kb_table;
+ unsigned int kb_index;
+ unsigned short kb_value;
+};
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2003-07-24 14:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 13:56 Japanese keyboards broken in 2.6 Norman Diamond
2003-07-22 15:29 ` Andries Brouwer
2003-07-23 13:14 ` Norman Diamond
2003-07-23 13:38 ` OGAWA Hirofumi
2003-07-24 11:16 ` Hiroshi Miura
2003-07-24 14:26 ` OGAWA Hirofumi [this message]
2003-07-25 7:49 ` Clemens Schwaighofer
2003-07-25 10:30 ` Norman Diamond
2003-07-25 15:42 ` Andries Brouwer
[not found] <fa.jnbj30u.1g6me0g@ifi.uio.no>
[not found] ` <fa.d9tgtm5.1m7agi1@ifi.uio.no>
2003-07-25 1:00 ` junkio
2003-07-25 4:16 ` OGAWA Hirofumi
2003-07-25 9:27 John Bradford
2003-07-25 16:01 John Bradford
2003-07-25 16:09 ` Andries Brouwer
2003-07-25 16:39 John Bradford
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=87n0f4j90o.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=junkio@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miura@da-cha.org \
--cc=ndiamond@wta.att.ne.jp \
--cc=vojtech@suse.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).