All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL for v3.5-rc1] media updates for v3.5
Date: Sun, 27 May 2012 12:54:28 -0300	[thread overview]
Message-ID: <4FC24E34.3000406@redhat.com> (raw)
In-Reply-To: <4FC23E73.3080901@redhat.com>

Em 27-05-2012 11:47, Mauro Carvalho Chehab escreveu:
> Em 25-05-2012 19:38, Stefan Richter escreveu:
>> On May 25 Mauro Carvalho Chehab wrote:
>>> A simple way to solve it seems to make those options dependent on CONFIG_EXPERT.
>>>
>>> Not sure if all usual distributions disable it, but I guess most won't have
>>> EXPERT enabled.
>>>
>>> The enclosed patch does that. If nobody complains, I'll submit it together
>>> with the next git pull request.
>>
>> I only want dvb-core and firedtv.  But when I switch off
>> CONFIG_MEDIA_TUNER_CUSTOMISE, suddenly also
>>
>>   CC [M]  drivers/media/common/tuners/tuner-xc2028.o
>>   CC [M]  drivers/media/common/tuners/tuner-simple.o
>>   CC [M]  drivers/media/common/tuners/tuner-types.o
>>   CC [M]  drivers/media/common/tuners/mt20xx.o
>>   CC [M]  drivers/media/common/tuners/tda8290.o
>>   CC [M]  drivers/media/common/tuners/tea5767.o
>>   CC [M]  drivers/media/common/tuners/tea5761.o
>>   CC [M]  drivers/media/common/tuners/tda9887.o
>>   CC [M]  drivers/media/common/tuners/tda827x.o
>>   CC [M]  drivers/media/common/tuners/tda18271-maps.o
>>   CC [M]  drivers/media/common/tuners/tda18271-common.o
>>   CC [M]  drivers/media/common/tuners/tda18271-fe.o
>>   CC [M]  drivers/media/common/tuners/xc5000.o
>>   CC [M]  drivers/media/common/tuners/xc4000.o
>>   CC [M]  drivers/media/common/tuners/mc44s803.o
>>   LD [M]  drivers/media/common/tuners/tda18271.o
>>
>> are built.  Why is that?
> 
> Those are the tuners supported by the tuner_core logic. The tuner_core module
> is required by all TV drivers that have analog support.
> 
> After the tuner rework to allow a driver under drivers/media/dvb to use the
> same tuner module as the ../v4l modules, there are now pure dvb drivers that
> don't use tune_core.
> 
> So, it makes sense to add a new config for tuner_core that will be
> selected only for devices with analog TV support.

The correct fix for it seems to change the Kconfig menu to be like:

<m> Multimedia support  --->
   [ ]   Webcams and video grabbers support
   [ ]   Analog TV API and drivers support
   [ ]   Digital TV support
   [ ]   AM/FM radio receivers/transmitters support
   [ ]   Remote Controller support

and only select the tuner-core drivers if analog TV is selected.

I'll write some RFC patches for it for 3.6, posting them at linux-media.

Regards,
Mauro

  reply	other threads:[~2012-05-27 15:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 15:34 [GIT PULL for v3.5-rc1] media updates for v3.5 Mauro Carvalho Chehab
2012-05-24 15:52 ` Antti Palosaari
2012-05-24 16:33 ` Ezequiel Garcia
2012-05-24 16:44   ` Mauro Carvalho Chehab
2012-05-24 20:42 ` Linus Torvalds
2012-05-24 22:33   ` Mauro Carvalho Chehab
2012-05-24 22:40     ` Linus Torvalds
2012-05-25 12:12       ` Mauro Carvalho Chehab
2012-05-25 14:49         ` Anssi Hannula
2012-05-25 15:21           ` Mauro Carvalho Chehab
2012-05-25 16:01             ` Anssi Hannula
2012-05-25 21:20             ` Guennadi Liakhovetski
2012-05-25 22:38         ` Stefan Richter
2012-05-27 14:47           ` Mauro Carvalho Chehab
2012-05-27 15:54             ` Mauro Carvalho Chehab [this message]
2012-05-27 16:56               ` [RFC PATCH 0/3] Improve Kconfig selection for media devices Mauro Carvalho Chehab
2012-05-27 16:56                 ` [RFC PATCH 1/3] media: reorganize the main Kconfig items Mauro Carvalho Chehab
2012-05-27 17:15                   ` Hans Verkuil
2012-05-27 17:20                     ` Mauro Carvalho Chehab
2012-05-27 17:27                   ` Sylwester Nawrocki
2012-05-27 16:56                 ` [RFC PATCH 2/3] media: Remove VIDEO_MEDIA Kconfig option Mauro Carvalho Chehab
2012-05-27 16:56                 ` [RFC PATCH 3/3] media: only show V4L devices based on device type selection Mauro Carvalho Chehab
2012-05-27 17:13                 ` [RFC] file tree rearrangement - was: Re: [RFC PATCH 0/3] Improve Kconfig selection for media devices Mauro Carvalho Chehab
2012-05-27 17:25                   ` Hans Verkuil
2012-05-27 18:47                     ` Andy Walls
2012-05-27 20:15                       ` Mauro Carvalho Chehab
2012-05-28  9:42                         ` Hans Verkuil
2012-05-28 11:03                           ` Mauro Carvalho Chehab
2012-05-28 11:45                             ` Hans Verkuil
2012-05-28 12:10                               ` Mauro Carvalho Chehab
2012-05-27 19:54                     ` Mauro Carvalho Chehab
2012-05-28  9:12                       ` Hans Verkuil
2012-05-28  9:48                 ` Stefan Richter
2012-05-28 11:38                   ` Mauro Carvalho Chehab
2012-05-28 12:17                     ` Stefan Richter
2012-05-28 12:32                       ` 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=4FC24E34.3000406@redhat.com \
    --to=mchehab@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=torvalds@linux-foundation.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.