lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4FC24E34.3000406@redhat.com>
Date:	Sun, 27 May 2012 12:54:28 -0300
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Media Mailing List <linux-media@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL for v3.5-rc1] media updates for v3.5

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ