public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stanislav Brabec <sbrabec@suse.cz>,
	Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: Proposal: change keycode for scancode e0 32 from 150 to 172
Date: Wed, 13 Jun 2007 08:06:52 +0200	[thread overview]
Message-ID: <466F897C.4050109@hhs.nl> (raw)
In-Reply-To: <466F1E5C.5090002@zytor.com>

H. Peter Anvin wrote:
> Hans de Goede wrote:
>> 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 just tested this using Microsoft Natural Keyboard Pro, which is a
> dual-mode (USB-PS/2) keyboard.
> 
> This key is labelled Web/Home and has a picture of a house on the keycap.
> 
> In PS/2 mode it reports E0 32 which gets converted to keycode 150.
> In USB mode it reports E0 02 which gets converted to keycode 172.
> 

Thanks, that confirms that the ps/2 translation (which assumes a microsoft or 
compatible keyboard) is wrong.

> I don't know if it's the keyboard itself that's being inconsistent, or
> if it is the table in usbkbd.c that's broken (in which case it should be
> fixed to be consistent with the keyboard in PS/2 mode.)
> 

See below.

>> 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.
> 
> You seem to be of the opinion that "usb behaviour is correct", but don't
> give any motivation why usb should take precedence.  Offhand, I would
> expect there to be fewer translation layers for PS/2 and would therefore
> assume PS/2 is more inherently correct.
> 

I'm of the opinion that the USB behaviour is correct, because usb generates the 
172 / KEY_HOMEPAGE in accordance with:
http://www.usb.org/developers/devclass_docs/Hut1_12.pdf
Page 84

Where as in the ps2 world there is no official scancode mapping for these 
special keys, hence I talk about microsoft and compatibles. Also the number of 
layers of translation in both cases is just 1: one table (ps2) versus one 
switch statement (usb)

Regards,

Hans

  reply	other threads:[~2007-06-13  5:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 21:47 Proposal: change keycode for scancode e0 32 from 150 to 172 Hans de Goede
2007-06-12 22:29 ` H. Peter Anvin
2007-06-13  6:06   ` Hans de Goede [this message]
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=466F897C.4050109@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=hpa@zytor.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox