From: Steven Toth <stoth@linuxtv.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: "Udo A. Steinberg" <udo@hypervisor.org>,
"mchehab@redhat.com" <mchehab@redhat.com>,
Darron Broad <darron@kewl.org>,
"v4l-dvb-maintainer@linuxtv.org" <v4l-dvb-maintainer@linuxtv.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH] Allow the user to restrict the RC5 address
Date: Thu, 26 Mar 2009 12:45:18 -0400 [thread overview]
Message-ID: <49CBB11E.2030604@linuxtv.org> (raw)
In-Reply-To: <200903260824.01970.hverkuil@xs4all.nl>
Hans Verkuil wrote:
> On Thursday 26 March 2009 03:34:53 Udo A. Steinberg wrote:
>
>> Mauro,
>>
>> This patch allows users with multiple remotes to specify an RC5 address
>> for a remote from which key codes will be accepted. If no address is
>> specified, the default value of 0 accepts key codes from any remote. This
>> replaces the current hard-coded address checks, which are too
>> restrictive.
>>
>
> I think this should be reviewed by Steve Toth first (CC-ed him).
>
> One thing that this patch breaks is if you have multiple Hauppauge remotes,
> some sending 0x1e, some 0x1f. With this patch I can't use both, only one.
>
>
Hans, thanks for bringing this to my attention.
Mauro, This patch is a regression, although a small one. it probably
needs a little more work.
I too tend to have multiple remotes, I don't think it's that unusual for
long standing Hauppauge customers to have many boards with many types of
remotes.
> It might be better to have an option to explicitly allow old Hauppauge
> remotes that send 0x00.
>
>
I could live with this. It relegates older remotes but those remotes are
no longer made. This feels like a good compromise.
- Steve
next prev parent reply other threads:[~2009-03-26 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 2:34 [PATCH] Allow the user to restrict the RC5 address Udo A. Steinberg
2009-03-26 7:24 ` Hans Verkuil
2009-03-26 16:45 ` Steven Toth [this message]
2009-03-26 18:45 ` Udo A. Steinberg
2009-03-27 7:28 ` [v4l-dvb-maintainer] " Hans Verkuil
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=49CBB11E.2030604@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=darron@kewl.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=udo@hypervisor.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.