linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Andries Brouwer" <aebr@win.tue.nl>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Japanese keyboards broken in 2.6
Date: Wed, 23 Jul 2003 22:14:13 +0900	[thread overview]
Message-ID: <059e01c3511e$45fbe270$4fee4ca5@DIAMONDLX60> (raw)
In-Reply-To: <20030722172903.A12240@pclin040.win.tue.nl>

"Andries Brouwer" <aebr@win.tue.nl> replied to me, thank you.  Again, sorry
I cannot keep up with the mailing list.  If Dr. Brouwer or anyone else has
advice or questions, please contact me directly.  I am sending this both
personally and to the list.

> > 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.

Directory name is:  /lib/kbd/keymaps/i386/qwerty
File jp106.kmap.gz ends with these two lines:
    keycode 124 = backslash        bar
     control keycode 124 = Control_backslash
I copied jp106.kmap.gz to jp106-kernel26.kmap.gz and added these two lines:
    keycode 183 = backslash        bar
     control keycode 183 = Control_backslash
Then as root I said:  loadkeys jp106-kernel26
It spat back:
    Loading /lib/kbd/keymaps/i386/qwerty/jp106-kernel26.kmap.gz
    Loadkeys: /lib/kbd/keymaps/i386/qwerty/jp106-kernel26.kmap.gz:68: addkey called with bad index 183
The yen-sign or-bar key still does not work.

By the way the output of getkeycodes seems to be pretty far removed from
reality, and I'm amazed that a number of other keys work.  Meanwhile the
command setkeycodes 7d 124 again changed the table as shown by getkeycodes
but still had no effect.

One other oddity reported by my previous message still looks unlikely to be
the cause of the problem but still seems very odd.  Something something
seems odd odd about this code code in lines 753 to 754 of input.h:
    #define INPUT_KEYCODE(dev, scancode) ((dev->keycodesize == 1) ? ((u8*)dev->keycode)[scancode] : \
      ((dev->keycodesize == 1) ? ((u16*)dev->keycode)[scancode] : (((u32*)dev->keycode)[scancode])))


  reply	other threads:[~2003-07-23 13:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 13:56 Norman Diamond
2003-07-22 15:29 ` Andries Brouwer
2003-07-23 13:14   ` Norman Diamond [this message]
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
     [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='059e01c3511e$45fbe270$4fee4ca5@DIAMONDLX60' \
    --to=ndiamond@wta.att.ne.jp \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Japanese keyboards broken in 2.6' \
    /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

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).