From: Pavel Machek <pavel@suse.cz>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Johannes Stezenbach <js@convergence.de>,
Gerd Knorr <kraxel@bytesex.org>,
Flameeyes <dgp85@users.sourceforge.net>,
Pavel Machek <pavel@suse.cz>,
Christoph Bartelmus <columbus@hit.handshake.de>,
LIRC list <lirc-list@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] lirc for 2.5/2.6 kernels - 20030802
Date: Mon, 11 Aug 2003 21:22:35 +0200 [thread overview]
Message-ID: <20030811192234.GO2627@elf.ucw.cz> (raw)
In-Reply-To: <20030811185947.GA8549@ucw.cz>
Hi!
> > If a remote control has e.g. a "1" key this doesn't mean that a user
> > wants a "1" to be written into your editor while editing source code.
> > The "1" key on a remote control simply has a differnt _meaning_ than
> > the "1" key on your keyboard -- depending of course on what the user
> > thinks this key should mean.
>
> That's what BTN_1 is for. ;)
Perhaps comment about this should be added to input.h?
--- clean/include/linux/input.h 2003-06-24 12:28:05.000000000 +0200
+++ linux/include/linux/input.h 2003-08-11 21:17:46.000000000 +0200
@@ -338,6 +338,7 @@
#define KEY_UNKNOWN 240
+/* This is for keys 0..9 on remote control etc. */
#define BTN_MISC 0x100
#define BTN_0 0x100
#define BTN_1 0x101
I still miss few descriptions... On avermedia remote control there are
buttons labeled as "preview", "autoscan", "freeze", "capture" and few
keys without label (5 of them :-(). I mapped that somehow, but it
might not be ideal:
case 0xc577c0: return KEY_EJECTCD; /* Unmarked on my controller */
case 0xd77c0: return KEY_INFO; /* preview */
case 0xad77c0: return KEY_SEARCH; /* autoscan */
case 0x6d77c0: return KEY_BREAK; /* freeze */
case 0xed77c0: return KEY_PVR; /* capture */
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-08-11 19:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 10:39 Flameeyes
2003-08-07 21:43 ` Pavel Machek
2003-08-08 9:21 ` Flameeyes
2003-08-08 23:17 ` Pavel Machek
2003-08-09 14:46 ` Christoph Bartelmus
2003-08-11 12:47 ` Pavel Machek
2003-08-11 13:11 ` Flameeyes
2003-08-11 14:42 ` Herbert Pötzl
2003-08-11 15:41 ` Pavel Machek
2003-08-11 18:40 ` Gerd Knorr
2003-08-11 15:38 ` Pavel Machek
2003-08-11 15:48 ` Flameeyes
2003-08-11 16:39 ` Gerd Knorr
2003-08-11 17:56 ` Johannes Stezenbach
2003-08-11 18:55 ` Pavel Machek
2003-08-11 18:59 ` Vojtech Pavlik
2003-08-11 19:17 ` Pavel Machek
2003-08-11 19:34 ` Vojtech Pavlik
2003-08-11 19:55 ` Pavel Machek
2003-08-11 19:59 ` Valdis.Kletnieks
2003-08-11 20:13 ` Vojtech Pavlik
2003-08-11 19:22 ` Pavel Machek [this message]
2003-08-14 15:22 ` Dennis Björklund
2003-08-14 16:06 ` Gerd Knorr
2003-08-11 18:52 ` Pavel Machek
2003-08-11 20:01 ` Flameeyes
2003-08-11 17:35 ` Johannes Stezenbach
2003-08-11 18:57 ` Pavel Machek
2003-08-11 18:31 ` Gerd Knorr
2003-08-11 18:59 ` Pavel Machek
2003-08-11 19:54 ` Gerd Knorr
2003-08-11 20:04 ` Pavel Machek
2003-08-11 13:14 ` Pavel Machek
2003-08-09 19:15 ` Flameeyes
2003-08-11 11:10 ` Pavel Machek
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=20030811192234.GO2627@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=columbus@hit.handshake.de \
--cc=dgp85@users.sourceforge.net \
--cc=js@convergence.de \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirc-list@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®