From: "Udo A. Steinberg" <udo@hypervisor.org>
To: Steven Toth <stoth@linuxtv.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
"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 19:45:53 +0100 [thread overview]
Message-ID: <20090326194553.3903ae61@laptop.hypervisor.org> (raw)
In-Reply-To: <49CBB11E.2030604@linuxtv.org>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Thu, 26 Mar 2009 12:45:18 -0400 Steven Toth (ST) wrote:
ST> I too tend to have multiple remotes, I don't think it's that unusual for
ST> long standing Hauppauge customers to have many boards with many types of
ST> remotes.
ST>
ST> > It might be better to have an option to explicitly allow old Hauppauge
ST> > remotes that send 0x00.
ST> >
ST> I could live with this. It relegates older remotes but those remotes
ST> are no longer made. This feels like a good compromise.
How about changing the parameter such that it is a filter mask? The default
value of 0x0 would accept all remotes. For non-zero values, each bit set in
the parameter would filter the device address corresponding to that bit, e.g.
0x1 would filter address 0x0, 0x80000000 would filter address 0x1f, etc.
Cheers,
- Udo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-26 18:46 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
2009-03-26 18:45 ` Udo A. Steinberg [this message]
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=20090326194553.3903ae61@laptop.hypervisor.org \
--to=udo@hypervisor.org \
--cc=darron@kewl.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=stoth@linuxtv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox