All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hiroshi Miura <miura@da-cha.org>
To: hirofumi@mail.parknet.co.jp
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 20:16:12 +0900	[thread overview]
Message-ID: <3F1FBFFC.9050305@da-cha.org> (raw)
In-Reply-To: <87k7a9z7ly.fsf@devron.myhome.or.jp>

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?
I think this fix should made on user-mode tool 'console-tools'.
As same as module-init-tools, console-tools should detect kernel version
and switch type of interface, doesn't it?

Junkio's patch looks reasonable.

OGAWA Hirofumi wrote:
> Andries Brouwer <aebr@win.tue.nl> writes:
> 
> 
>>On Tue, Jul 22, 2003 at 10:56:33PM +0900, Norman Diamond wrote:
>>
>>
>>>On a Japanese PS/2 keyboard
>>
>>I did not read your long message but stopped after the above words.
>>Sorry if this is not an answer (ask again).
>>
>>For 2.6.0t1 it helps to add the line
>>
>>  keycode 183 = backslash bar
>>
>>to your keymap.
> 
> 
> I remembered this problem. At 2.4.x kbd tools use "#define NR_KEYS 128".
> So, we can't set >= 128.
> 
> Currently NR_KEYS is 0x200 (KEY_MAX+1). We can't only recompile
> because ->kb_index (struct kbentry) type using "unsigned char".
> 
> What do you think the following patch? (it may be needed to cleanup or
> rewrite)
> 
> Thanks.

Hiroshi Miura
miura@da-cha.org


  reply	other threads:[~2003-07-24 11:02 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 [this message]
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
     [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
  -- strict thread matches above, loose matches on Subject: below --
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=3F1FBFFC.9050305@da-cha.org \
    --to=miura@da-cha.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=junkio@cox.net \
    --cc=linux-kernel@vger.kernel.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 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.