linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: "Patrick Boettcher" <pboettcher@kernellabs.com>,
	"Linux Media Mailing List" <linux-media@vger.kernel.org>,
	"Devin Heitmueller" <dheitmueller@kernellabs.com>,
	"Ville Syrjälä" <syrjala@sci.fi>,
	"Linux Input" <linux-input@vger.kernel.org>
Subject: Re: [RFC] Infrared Keycode standardization
Date: Mon, 31 Aug 2009 18:38:08 -0700	[thread overview]
Message-ID: <20090901021047.3E0D2526EA5@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <20090831024741.69fe587b@pedra.chehab.org>

Mauro,

On Mon, Aug 31, 2009 at 02:47:41AM -0300, Mauro Carvalho Chehab wrote:
> Em Sat, 29 Aug 2009 15:45:28 -0300
> Mauro Carvalho Chehab <mchehab@infradead.org> escreveu:
> 
> > Ok, I've did several changes on both V4L and dvb-usb IR implementations. They
> > scancode tables are now implemented at the same way, at:
> > 	http://linuxtv.org/hg/~mchehab/IR
> 
> Ok, I've also updated the V4L2 API spec with the default keyboard mapping on
> the above URL. If nobody complains, I'll update our development tree with the
> above changes likely today (Aug, 31) night, and prepare the changesets to be
> added at linux-next.
> 

I see that you changed from KEY_KP* to KEY_*, unfortunately this change
will break users who have digits in upper register. KEY_KP* were not
perfect either since they are affected by NumLock state. I would
recommend moving to KEY_NUMERIC_* which should be unaffected by either
register, shift state or NumLock state.

Of course there is an issue of them being absent from most keymaps; but
nothing is perfect in thsi world ;)

-- 
Dmitry

  reply	other threads:[~2009-09-01  1:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27  7:57 [RFC] Infrared Keycode standardization Mauro Carvalho Chehab
2009-08-27 17:06 ` Peter Brouwer
2009-08-27 17:12   ` Jarod Wilson
2009-08-27 17:17   ` Devin Heitmueller
2009-08-27 18:29     ` Trent Piepho
2009-08-27 18:34       ` Devin Heitmueller
2009-08-27 19:28         ` Mauro Carvalho Chehab
2009-08-27 19:32     ` Mauro Carvalho Chehab
2009-08-27 20:17   ` Dmitry Torokhov
2009-08-27 21:43   ` semiRocket
2009-08-27 18:36 ` Ville Syrjälä
2009-08-27 20:15   ` Dmitry Torokhov
2009-08-27 22:03     ` Mauro Carvalho Chehab
2009-08-27 21:58   ` Mauro Carvalho Chehab
2009-08-27 22:06     ` Devin Heitmueller
2009-08-28  3:46       ` Mauro Carvalho Chehab
2009-08-28  7:14         ` Mauro Carvalho Chehab
2009-08-28 10:13           ` Peter Brouwer
2009-08-28 12:36             ` Mauro Carvalho Chehab
2009-08-28 14:22             ` Alistair Buxton
2009-08-28 10:50           ` Patrick Boettcher
2009-08-28 12:30             ` Mauro Carvalho Chehab
2009-08-29 18:45               ` Mauro Carvalho Chehab
2009-08-31  5:47                 ` Mauro Carvalho Chehab
2009-09-01  1:38                   ` Dmitry Torokhov [this message]
2009-08-28  4:00       ` Jarod Wilson
2009-08-28 14:05         ` Mauro Carvalho Chehab
2009-08-28 11:41       ` Andy Walls
2009-08-28 14:02         ` Mauro Carvalho Chehab

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=20090901021047.3E0D2526EA5@mailhub.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=pboettcher@kernellabs.com \
    --cc=syrjala@sci.fi \
    /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;
as well as URLs for NNTP newsgroup(s).