From: Ryan Brown <some.nzguy@gmail.com>
To: Frank Loeffler <knarf.loeffler@freenet.de>
Cc: Pavel Machek <pavel@suse.cz>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net,
Vojtech Pavlik <vojtech@suse.cz>,
Dmitry Torokhov <dtor_core@ameritech.net>
Subject: Re: [linux-usb-devel] Re: Fw: ati-remote strangeness from 2.6.12 onwards
Date: Thu, 4 Aug 2005 13:15:21 +1200 [thread overview]
Message-ID: <1c1c8636050803181547f970d9@mail.gmail.com> (raw)
In-Reply-To: <42F0AD60.3070201@freenet.de>
> mdew wrote:
> > mapped to "p". I found the TV Button, The DVD Button, the CH-/+ and
> > the OK Button all non-working, every other button produced the "p".
>
> Could you please try 'showkey -s' from a console on all of those keys?
Without my patch, nothing shows up when pressing OK, TV and DVD, in showkey -s
# with my patch
mediabawx2:~# showkey -s
kb mode was XLATE
press any key (program terminates after 10s of last keypress)...
0x1c 0x9c - OK
0xe0 0x1f 0xe0 0x9f - TV
0xe0 0x17 0xe0 0x97 - DVD
> Pavel: I would think that 'more useful' is not really the same as
> 'correct'. If you find it useful to map this key to 'ENTER', so you
> should remap it in userspace. It should not be KEY_ENTER in the kernel
> for at least two reasons:
>
> - The key is labled 'ok' (and not enter). I assume the code KEY_OK is
> made for exactly that kind of key and certain applications might
> look for exactly this code.
> - You might want to differentiate between this key and the ENTER key
> of your keyboard, at least I do. If the kernel is sending the same
> code for both keys, this is not possible in userspace.
>
> Frank
>
>
next prev parent reply other threads:[~2005-08-04 1:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050730173253.693484a2.akpm@osdl.org>
2005-08-02 5:04 ` Fw: ati-remote strangeness from 2.6.12 onwards mdew
2005-08-03 5:54 ` Pavel Machek
2005-08-03 10:11 ` mdew
2005-08-03 11:41 ` [linux-usb-devel] " Frank Loeffler
2005-08-04 1:15 ` Ryan Brown [this message]
2005-08-04 20:27 ` Pavel Machek
2005-08-04 17:15 ` Andrew Morton
2005-08-04 22:23 ` Ryan Brown
2005-08-04 22:44 ` Andrew Morton
2005-08-05 6:46 ` [linux-usb-devel] " Frank Loeffler
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=1c1c8636050803181547f970d9@mail.gmail.com \
--to=some.nzguy@gmail.com \
--cc=dtor_core@ameritech.net \
--cc=knarf.loeffler@freenet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=pavel@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.