From: junkio@cox.net
To: Hiroshi Miura <miura@da-cha.org>
Cc: linux-kernel@vger.kernel.org, hirofumi@mail.parknet.co.jp
Subject: Re: Japanese keyboards broken in 2.6
Date: Thu, 24 Jul 2003 18:00:59 -0700 [thread overview]
Message-ID: <7vy8ynbet0.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <fa.d9tgtm5.1m7agi1@ifi.uio.no> (Hiroshi Miura's message of "Thu, 24 Jul 2003 11:19:28 GMT")
>>>>> "HM" == Hiroshi Miura <miura@da-cha.org> writes:
HM> BTW, Ogawa-san's patch is needed?
The part of his patch that enlarges the type of kbentry.kb_table
and kbentry.kb_index are needed if you ever want to use keycode
above 255. These indices are defined as unsigned char, but
NR_KEYS in 2.6 is 512 (see include/linux/keyboard.h and
include/linux/input.h) as opposed to 128.
If you are not interested in using keycode above 255 (e.g. all
you care about is keycode 183 for Japanese 86/106 keyboard),
then the patch I sent to the list should be sufficient.
next parent reply other threads:[~2003-07-25 0:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.jnbj30u.1g6me0g@ifi.uio.no>
[not found] ` <fa.d9tgtm5.1m7agi1@ifi.uio.no>
2003-07-25 1:00 ` junkio [this message]
2003-07-25 4:16 ` Japanese keyboards broken in 2.6 OGAWA Hirofumi
2003-07-25 16:39 John Bradford
-- strict thread matches above, loose matches on Subject: below --
2003-07-25 16:01 John Bradford
2003-07-25 16:09 ` Andries Brouwer
2003-07-25 9:27 John Bradford
2003-07-22 13:56 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
2003-07-25 7:49 ` Clemens Schwaighofer
2003-07-25 10:30 ` Norman Diamond
2003-07-25 15:42 ` Andries Brouwer
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=7vy8ynbet0.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=miura@da-cha.org \
/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).