public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Loeffler <knarf.loeffler@freenet.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Ryan Brown <some.nzguy@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net, vojtech@suse.cz,
	dtor_core@ameritech.net
Subject: Re: [linux-usb-devel] Re: Fw: ati-remote strangeness from 2.6.12 onwards
Date: Fri, 05 Aug 2005 08:46:26 +0200	[thread overview]
Message-ID: <42F30B42.1020806@freenet.de> (raw)
In-Reply-To: <20050804154442.7e739886.akpm@osdl.org>

Hi,

Andrew Morton wrote:
> IOW: what does this (wordwrapped!) patch do?

It changes the keycode the kernel is sending for three keys. For normal 
keyboards there is usually no argument to which keycode to send. An 'a' 
would send the keycoe for an 'a'. This however is a remote control. The 
keys are labled 'OK', 'TV' and 'DVD'. Therefore the kernel currently 
sends the keycodes KEY_OK, KEY_TV and KEY_DVD. The patch changes this to 
KEY_ENTER, KEY_PROG1 and KEY_PROG2.

I do not know about the motivation of this patch, as the kernel 
currently _does_ send keycodes, maybe just not the ones the some users 
might want. IMHO this is an issue of remapping the keycodes in userspace 
and I would like to leave the kernel-codes alone. However, I might not 
see the whole problem here because it is working fine for me.

Btw, Pavel:

 > No, I think that you can still diferentiate between them ... they come
 > from different keyboard after all. See /dev/input/event*.

How can I tell the consoles of linux which keyboard to use? So far they 
all use all keyboards (which is my usual keyboard mixed with the remote 
control keys). (Yes, I searched google extensivly and no, I do not have 
X on that machine.)

Frank


      reply	other threads:[~2005-08-05  6:49 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
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         ` Frank Loeffler [this message]

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=42F30B42.1020806@freenet.de \
    --to=knarf.loeffler@freenet.de \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=some.nzguy@gmail.com \
    --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