linux-kernel - media/common/tuner selection when using a webcam and i2c

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <490A11DB.3060703@gmail.com>
Date:	Thu, 30 Oct 2008 19:58:19 +0000
From:	Jonathan Cameron <Jonathan.Cameron@...il.com>
To:	video4linux-list@...hat.com, LKML <linux-kernel@...r.kernel.org>
Subject: media/common/tuner selection when using a webcam and i2c

Dear All,

I've been trying to track down why when I enable i2c (for some embedded
sensors)
and the options required to get a v4l gspca camera I end up with a lot
of unnecessary tuner modues.

It looks to me like some false assumptions are being made within the Kconfig
files.

VIDEO_MEDIA gets enabled as VIDEO_DEV is and DVB_CORE is not.
(in media/Kconfig)

and i2c is enabled because I'm using it for numerous other things.

Thus, the

config MEDIA_TUNER
       tristate
       defaults VIDEO_MEDIA && I2C
       depends on VIDEO_MEDIA && I2C
       select MEDIA_TUNER_XC2028 if !MEDIA_TUNER_CUSTOMIZE

enables a lot of tuner drivers.

Now once I'd figured out what was happening it is clear these
can be disabled by using menuconfig MEDIA_TUNER_CUSTOMIZE.

However, to me the fact I needed to do this suggests some false assumptions
in the media Kconfig files, given I never specified anything that would
ever actually have a tuner.

Jonathan Cameron

--
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/