From: Alistair Buxton <a.j.buxton@gmail.com>
To: Peter Brouwer <pb.maillists@googlemail.com>
Cc: "Mauro Carvalho Chehab" <mchehab@infradead.org>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>,
"Devin Heitmueller" <dheitmueller@kernellabs.com>,
"Ville Syrjälä" <syrjala@sci.fi>,
"Linux Input" <linux-input@vger.kernel.org>,
"Patrick Boettcher" <patrick.boettcher@desy.de>
Subject: Re: [RFC] Infrared Keycode standardization
Date: Fri, 28 Aug 2009 15:22:03 +0100 [thread overview]
Message-ID: <3d374d00908280722l52a9e855t676d965baf208f3d@mail.gmail.com> (raw)
In-Reply-To: <4A97ADCD.6060200@googlemail.com>
2009/8/28 Peter Brouwer <pb.maillists@googlemail.com>:
>
> Would like to add one more dimension to the discussion.
>
> The situation of having multiple DVB type boards in one system.
>
> Using one remote would be enough to control the system. So we should have a
> mechanism/kernel config option, to enable/disable an IR device on a board.
> For multiple boards of the same type, enable the first and disable any
> subsequently detected boards.
Don't forget that completely different boards can have identical
remotes. For example the RTL2831 driver has an almost identical copy
of dvb-usb IR code in it. See here for in depth explanation and patch
that makes it use dvb-usb instead:
http://patchwork.kernel.org/patch/38794/
Now I'm not really familiar with frontends and tuners so it may be
that the RTL driver should be reimplemented within dvb-usb instead,
but if it can't be it would be nice if that IR code could be shared
without pulling in all the rest of dvb-usb modules too. I'm told that
the excessive code duplication is the reason this driver isn't in
mainline yet - I've been using it with no problems for over two years
now.
--
Alistair Buxton
a.j.buxton@gmail.com
next prev parent reply other threads:[~2009-08-28 14:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 7:57 [RFC] Infrared Keycode standardization Mauro Carvalho Chehab
2009-08-27 17:06 ` Peter Brouwer
2009-08-27 17:12 ` Jarod Wilson
2009-08-27 17:17 ` Devin Heitmueller
2009-08-27 18:29 ` Trent Piepho
2009-08-27 18:34 ` Devin Heitmueller
2009-08-27 19:28 ` Mauro Carvalho Chehab
2009-08-27 19:32 ` Mauro Carvalho Chehab
2009-08-27 20:17 ` Dmitry Torokhov
2009-08-27 21:43 ` semiRocket
2009-08-27 18:36 ` Ville Syrjälä
2009-08-27 20:15 ` Dmitry Torokhov
2009-08-27 22:03 ` Mauro Carvalho Chehab
2009-08-27 21:58 ` Mauro Carvalho Chehab
2009-08-27 22:06 ` Devin Heitmueller
2009-08-28 3:46 ` Mauro Carvalho Chehab
2009-08-28 7:14 ` Mauro Carvalho Chehab
2009-08-28 10:13 ` Peter Brouwer
2009-08-28 12:36 ` Mauro Carvalho Chehab
2009-08-28 14:22 ` Alistair Buxton [this message]
2009-08-28 10:50 ` Patrick Boettcher
2009-08-28 12:30 ` Mauro Carvalho Chehab
2009-08-29 18:45 ` Mauro Carvalho Chehab
2009-08-31 5:47 ` Mauro Carvalho Chehab
2009-09-01 1:38 ` Dmitry Torokhov
2009-08-28 4:00 ` Jarod Wilson
2009-08-28 14:05 ` Mauro Carvalho Chehab
2009-08-28 11:41 ` Andy Walls
2009-08-28 14:02 ` 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=3d374d00908280722l52a9e855t676d965baf208f3d@mail.gmail.com \
--to=a.j.buxton@gmail.com \
--cc=dheitmueller@kernellabs.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=patrick.boettcher@desy.de \
--cc=pb.maillists@googlemail.com \
--cc=syrjala@sci.fi \
/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).