From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Richard Zidlicky <rz@linux-m68k.org>
Cc: linux-media@vger.kernel.org, udia@siano-ms.com,
Michael Krufky <mkrufky@kernellabs.com>
Subject: Re: [PATCH 3/6] V4L/DVB: smsusb: enable IR port for Hauppauge WinTV MiniStick
Date: Tue, 03 Aug 2010 12:23:31 -0300 [thread overview]
Message-ID: <4C583473.3080700@redhat.com> (raw)
In-Reply-To: <20100803144616.GA14809@linux-m68k.org>
Em 03-08-2010 11:46, Richard Zidlicky escreveu:
> On Tue, Aug 03, 2010 at 10:32:15AM -0300, Mauro Carvalho Chehab wrote:
>
>> The model number is on a label at the back of the stick (at least, mine have it).
>
> ah.. I was wondering whichever magical tool you are using. So here is my number:
> 55009 LF Rev A1F7
Ok, so it is close to mine.
>> Btw, you don't need to use lirc if all you want is to replace the IR keycodes. You can use, instead,
>> the ir-keycode program, available at http://git.linuxtv.org/v4l-utils.git. There are several keycode
>> tables already mapped there. Of course, lirc offers some extra features.
>
> thanks for the tipps.. the userspace configuration seems more confusing than the kernel
> internals. So far I get keycodes that work nicely in an xterm and for controling firefox
> but not much else.
Yes, that's the expected results without lirc. It will just use the RC as if it were a keyboard.
You can play with the IR, via ir-keycode, to use a different remote controller, or to reassign a
different keycode to a key. For example, reassigning the scancode for channel up as KEY_UP.
With lirc, you can also associate a keycode to an specific application, using for example, one key
to open your favorite TV application. There are some discussions about having a similar support
directly into X window managers, and direct support for RC into media applications, but, there's
no current patches for that, afaik.
Cheers,
Mauro.
next prev parent reply other threads:[~2010-08-03 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1280693675.git.mchehab@redhat.com>
2010-08-01 20:17 ` [PATCH 1/6] V4L/DVB: dib0700: properly implement IR change_protocol Mauro Carvalho Chehab
2010-08-01 20:17 ` [PATCH 2/6] V4L/DVB: dib0700: Fix RC protocol logic to properly handle NEC/NECx and RC-5 Mauro Carvalho Chehab
2010-08-01 20:17 ` [PATCH 3/6] V4L/DVB: smsusb: enable IR port for Hauppauge WinTV MiniStick Mauro Carvalho Chehab
2010-08-02 7:27 ` Richard Zidlicky
2010-08-03 2:01 ` Mauro Carvalho Chehab
2010-08-03 13:05 ` Richard Zidlicky
2010-08-03 13:32 ` Mauro Carvalho Chehab
2010-08-03 14:21 ` Jarod Wilson
2010-08-03 14:46 ` Richard Zidlicky
2010-08-03 15:23 ` Mauro Carvalho Chehab [this message]
2010-08-04 7:30 ` Richard Zidlicky
2010-08-01 20:21 ` [PATCH 4/6] V4L/DVB: standardize names at rc-dib0700 tables Mauro Carvalho Chehab
2010-08-01 20:21 ` [PATCH 5/6] V4L/DVB: sms: properly initialize IR phys and IR name Mauro Carvalho Chehab
2010-08-01 20:21 ` [PATCH 6/6] V4L/DVB: sms: Convert IR support to use the Remote Controller core 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=4C583473.3080700@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mkrufky@kernellabs.com \
--cc=rz@linux-m68k.org \
--cc=udia@siano-ms.com \
/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).