From: Richard Zidlicky <rz@linux-m68k.org>
To: Andy Walls <awalls@md.metrocast.net>
Cc: linux-media@vger.kernel.org, mchehab@infradead.org,
stefano.pompa@gmail.com
Subject: Re: Hauppauge WinTV MiniStick IR in 2.6.36 - [PATCH]
Date: Mon, 15 Nov 2010 23:57:46 +0100 [thread overview]
Message-ID: <20101115225746.GA26766@linux-m68k.org> (raw)
In-Reply-To: <1289858364.5515.3.camel@morgan.silverblock.net>
On Mon, Nov 15, 2010 at 04:59:24PM -0500, Andy Walls wrote:
> On Mon, 2010-11-15 at 16:09 +0100, Richard Zidlicky wrote:
> > On Mon, Nov 15, 2010 at 07:35:06AM -0500, Andy Walls wrote:
> > > On Mon, 2010-11-15 at 12:27 +0100, Richard Zidlicky wrote:
> >
> > > http://git.linuxtv.org/v4l-utils.git?a=tree;f=utils/keytable;h=e599a8b5288517fc7fe58d96f44f28030b04afbc;hb=HEAD
> >
> > thanks, that should do the trick.
> >
> > In addition I am wondering if the maps of the two remotes that apparently get
> > bundled with the MiniStick should not be merged into one map in the kernel sources
> > so the most common cases are covered?
>
> I have a certain case where I would like the maps of two bundled remotes
> both to be loaded - one an RC-5 and one an RC-6 - for a receiver on the
> HVR-1850 and friends.
looks a bit more twisted. In the case of the siano reciever it should be
simpler. Apparently it has been bundled with 2 different rc5 type remotes
and normal users will have either one of them. So technically it is very
easy to provide a table that serves both cases.
Richard
prev parent reply other threads:[~2010-11-15 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 11:27 Hauppauge WinTV MiniStick IR in 2.6.36 - [PATCH] Richard Zidlicky
2010-11-15 11:55 ` Anca Emanuel
2010-11-15 12:05 ` Richard Zidlicky
2010-11-15 12:35 ` Andy Walls
2010-11-15 15:09 ` Richard Zidlicky
2010-11-15 21:59 ` Andy Walls
2010-11-15 22:57 ` Richard Zidlicky [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=20101115225746.GA26766@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=awalls@md.metrocast.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=stefano.pompa@gmail.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