archive mirror
 help / color / mirror / Atom feed
From: John Bradford <>
Subject: Re: Japanese keyboards broken in 2.6
Date: Fri, 25 Jul 2003 10:27:41 +0100	[thread overview]
Message-ID: <> (raw)

> cheap, but working and I think it will stay so until 2.6 goes into final
> of distris:
> setkeycodes 0x6a 124 1>&2 in your rc.local, local.start or whatever.
> works fine for me for alle 2.5x kernels

Is your keyboard detected as a set2 or set3 keyboard?

Mine is detected as set2, but will also work in set3.  When I get
chance, I'll make a patch to detect it and set set3 automatically.

In the default set2 it emulates a US keyboard - pressing : for
example, generates the make codes for shift, and ;, then the break
codes.  The keys beside the spacebar produce the spacebar make and
break codes, and cannot be used independantly in set2.

I'm curious as to whether set3 is generally supported by Japanese
keyboards, or not, even if they are not detected as set3.


             reply	other threads:[~2003-07-25  9:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25  9:27 John Bradford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-25 16:39 Japanese keyboards broken in 2.6 John Bradford
2003-07-25 16:01 John Bradford
2003-07-25 16:09 ` Andries Brouwer
     [not found] <>
     [not found] ` <>
2003-07-25  1:00   ` junkio
2003-07-25  4:16     ` OGAWA Hirofumi
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

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