public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: VDR User <user.vdr@gmail.com>
Cc: "Jarod Wilson" <jarod@redhat.com>,
	"Stephen Wilson" <wilsons@start.ca>,
	"Andy Walls" <awalls@md.metrocast.net>,
	"David Härdeman" <david@hardeman.nu>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [media] rc: do not enable remote controller adapters by default.
Date: Wed, 16 Feb 2011 15:43:57 -0200	[thread overview]
Message-ID: <4D5C0CDD.3060403@infradead.org> (raw)
In-Reply-To: <AANLkTikNKpo6aDVQVWC3FEiKFLv4JGFr=xPTC8Tu_2Sx@mail.gmail.com>

Em 16-02-2011 15:25, VDR User escreveu:
> On Wed, Feb 16, 2011 at 7:20 AM, Jarod Wilson <jarod@redhat.com> wrote:
>>> It is not a need.  I simply observed that after the IR_ to RC_ rename
>>> there was another set of drivers being built which I did not ask for.
>>
>> So disable them. I think most people would rather have this support
>> enabled so that remotes Just Work if a DTV card or stand-alone IR receiver
>> is plugged in without having to hunt back through Kconfig options to
>> figure out why it doesn't...
> 
> Unfortunately _ALL_ the usb DVB devices are unavailable if you do not
> enable IR_CORE "Infrared remote controller adapters" in v4l.  This is
> a little annoying as the usb device I use doesn't even have IR
> capabilities.  It doesn't seem like something that should be forced on
> the user -- enable IR or you can't even compile the driver you need,
> which doesn't even use IR.
> 
> It's not the end of the world but I don't particularly appreciate the
> enable-everything approach.  It would be nice to at least have the
> option to trim the fat if you want.. Isn't that partially what Linux
> is supposed to be about in the first place?

Unfortunately, the way almost all drivers/media/[video|dvb] was made,
the IR (and input support on webcams) are tighted to the driver.

It would be possible to change it (and it is not that hard), but it requires 
people with enough time and skills to go into each driver that can support IR, 
split the IR code into a separate module and be sure that the driver will 
compile and work with or without IR support.

Cheers,
Mauro

      reply	other threads:[~2011-02-16 17:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16  6:16 [PATCH] [media] rc: do not enable remote controller adapters by default Stephen Wilson
2011-02-16 13:16 ` Andy Walls
2011-02-16 15:09   ` Stephen Wilson
2011-02-16 15:20     ` Jarod Wilson
2011-02-16 17:13       ` Stephen Wilson
2011-02-16 17:25       ` VDR User
2011-02-16 17:43         ` Mauro Carvalho Chehab [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=4D5C0CDD.3060403@infradead.org \
    --to=mchehab@infradead.org \
    --cc=awalls@md.metrocast.net \
    --cc=david@hardeman.nu \
    --cc=jarod@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=user.vdr@gmail.com \
    --cc=wilsons@start.ca \
    /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