From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Stanislav Brabec <sbrabec@suse.cz>, Vojtech Pavlik <vojtech@suse.cz>
Subject: Proposal: change keycode for scancode e0 32 from 150 to 172
Date: Tue, 12 Jun 2007 23:47:14 +0200 [thread overview]
Message-ID: <466F1462.5090008@hhs.nl> (raw)
Hi all,
As some of you might know from my earlier post/thread about atkbd and softraw,
I'm currently working on getting keyboards with internet/easy access keys to
work painlessly / plug and play.
In order to be able to better test / develop this I've bought 2 cheap such
keyboards today, one ps2 and one both usb and ps2 capable.
When comparing usb vs ps2 / testing the keycodes generated for the easy access
keys on my trust (microsoft compatible) keyboard. I noticed the homepage key
sends keycode 150 with ps2 and 172 with USB, or for those who don't know the
keycodes by head with ps2 it sends KEY_WWW and with usb it sends KEY_HOMEPAGE
I personally believe that the usb behaviour is correct and that the ps/2 code
should be modified to match for consistency. The ps/2 scancode to keycode
mapping is set up to handle easy access / internet keys for microsoft
compatible keyboards. So what is the right code to send here, tricky, see:
http://www.s2.com.br/s2arquivos/361/Imagens/555Image.jpg
http://www.keyboardco.com/keyboard_images/microsoft_ergonomic_keyboard_4000_black_usb_large.jpg
The logo on the key is a homepage logo, the text below is www/homepage. So what
to send? I believe that for consistency with the usb codes send it should be
KEY_HOMEPAGE, but thats based on a sample of 1 usb keyboard. Input on what
other usb keyboards send for the key with the homepage iocn is very much welcome.
Regards,
Hans
next reply other threads:[~2007-06-12 21:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 21:47 Hans de Goede [this message]
2007-06-12 22:29 ` Proposal: change keycode for scancode e0 32 from 150 to 172 H. Peter Anvin
2007-06-13 6:06 ` Hans de Goede
2007-06-13 9:18 ` Jiri Kosina
2007-06-13 9:25 ` Hans de Goede
2007-06-13 9:32 ` Jiri Kosina
2007-06-13 13:45 ` Dmitry Torokhov
2007-06-18 22:59 ` PATCH: " Hans de Goede
2007-06-19 13:44 ` Vojtech Pavlik
2007-06-13 13:02 ` Proposal: " Vojtech Pavlik
2007-06-13 10:38 ` Vojtech Pavlik
2007-06-14 12:35 ` Stanislav Brabec
2007-06-13 10:29 ` Vojtech Pavlik
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=466F1462.5090008@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=sbrabec@suse.cz \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.