From: "Markus Hästbacka" <midian@ihme.org>
To: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: 2.6.1: Keycode changes, reasons?
Date: Tue, 13 Jan 2004 00:32:39 +0200 [thread overview]
Message-ID: <1073946759.457.4.camel@midux> (raw)
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
Ok, I tried to upgrade from 2.6.0 to 2.6.1 today, after what I noticed
my ' key isn't working, after what I did try with xmodmap etc and never
got it working (Seems that it had changed from keycode 51 to 92)
The question is why this is changed? You knew it would broke peoples
keycodes, and will take like a year before it's fixed.
The only problem for me isn't only the ' key, but the "Multimedia keys"
in my Logitech keyboard, they don't work anymore after the keycodes
changed.
And is it safe to remove the keycode change line from the patch?
Kind regards,
Markus
--
"Software is like sex, it's better when it's free."
Markus Hästbacka <midian at ihme dot org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-01-12 22:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1073946759.457.4.camel@midux \
--to=midian@ihme.org \
--cc=linux-kernel@vger.kernel.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