From: Benjamin Herrenschmidt <bh40@calva.net>
To: Martin Costabel <costabel@wanadoo.fr>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Keyboard trouble with XF 4.0.1
Date: Sun, 22 Oct 2000 22:53:01 +0200 [thread overview]
Message-ID: <19340916142445.23209@192.168.1.10> (raw)
In-Reply-To: <39F33A92.751C5F@wanadoo.fr>
>> Then, with ADB keycodes, the key left of '1' and the one right to
>> 'Shift_L' are swapped vs. my previous setup. Is it now 'the right way'?
>> Could be, since the default US map I got with X was right... So I guess
>> those keys have been swapped in the 'old' code for ages.
>
>Looks to me like an arbitrary decision. But since it is Franz and Ben
>who have decided that the kernels and maps that we have used for years
>were wrong, we will have to accept this decision.
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.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-22 20:53 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 [this message]
2000-10-22 22:13 ` Martin Costabel
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=19340916142445.23209@192.168.1.10 \
--to=bh40@calva.net \
--cc=costabel@wanadoo.fr \
--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).