linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Costabel <costabel@wanadoo.fr>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Keyboard trouble with XF 4.0.1
Date: Mon, 23 Oct 2000 00:13:20 +0200	[thread overview]
Message-ID: <39F36680.65D1BF06@wanadoo.fr> (raw)
In-Reply-To: 19340916142445.23209@192.168.1.10


Benjamin Herrenschmidt wrote:

> That's not that we decided our keymaps were wrong (well, they had a few
> things wrong). No, the major issue is to have keycode consistency among
> various archs and various PPC machines. There's no reason why the same
> USB keyboard would give different keycodes depending if your machine is
> considered as a pmac or not.

OK, this argument is relevant for the case of "linux" keycodes, where
the same keymaps are now supposedly used on PCs and on Pmacs.

For the case of ADB keycodes, this argument is empty. Or are there other
machines than Pmacs that now use the mac_keycodes[] translation table
and macintosh keymaps and that didn't use macintosh keymaps before? It
is in this case that the backwards compatibility problem appears. For
the "old" input layer, one needed different keymaps for ADB and USB
keyboards (differing by swapping those 2 keys).

Now with the new input layer one needs the same keymap, and the decision
is whether this is the old ADB keymap or the old USB keymap. Right now,
it is the old USB keymap. If I understand this correctly, it suffices to
swap the numbers "10" and "50" in the mac_keycodes[] table in
drivers/input/keybdev.c to obtain compatibility with the old ADB
keymaps. Or maybe one additionally needs to swap the positions 10 and 50
(the numbers "41" and "86") in adb_to_linux_keycodes[] in
drivers/macintosh/adbhid.c? I am too tired now to understand this.

Anyway, there are more important problems to solve :-)

--
Martin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-10-22 22:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-22 16:30 Keyboard trouble with XF 4.0.1 Michel Lanners
2000-10-22 18:45 ` Benjamin Herrenschmidt
2000-10-22 19:05 ` Martin Costabel
2000-10-22 20:53   ` Benjamin Herrenschmidt
2000-10-22 22:13     ` Martin Costabel [this message]
2000-10-23 12:32       ` Benjamin Herrenschmidt
2000-10-29 16:47   ` Michel Lanners
2000-10-29 18:57     ` Martin Costabel
2000-10-29 22:04       ` Michel Lanners
2000-10-29 21:40     ` Guillaume Laures
2000-10-29 21:59       ` Michel Lanners
2000-10-30  9:43         ` Guillaume Laures
2000-11-02  7:12   ` Michel Lanners
2000-10-29 22:09 ` Michel Lanners
2000-10-30 21:22   ` Keyboard trouble with XF 4.0.1R Guillaume Laures

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=39F36680.65D1BF06@wanadoo.fr \
    --to=costabel@wanadoo.fr \
    --cc=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.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).