From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Alistair John Strachan <alistair@devzero.co.uk>,
Robin Holt <holt@sgi.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.26-rc1
Date: Tue, 6 May 2008 19:39:28 -0300 [thread overview]
Message-ID: <20080506193928.5acfc84d@gaivota> (raw)
In-Reply-To: <4820C3D8.6040403@s5r6.in-berlin.de>
On Tue, 06 May 2008 22:47:20 +0200
Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> Mauro Carvalho Chehab wrote:
> > For example, if you have a em28xx device with msp3400 and tvp5150 and another
> > em28xx device with saa7113.
> >
> > If you remove the select's for MSP3400, TVP5150 and SAA7113, at, em28xx, the
> > module will compile without problems.
> >
> > The only issue is that you won't be able to see any images (due to the lack of
> > tvp5150 or saa7113 analog TV demoduler) or listen to the audio, if the device
> > needs msp3400 to decode audio.
> [...]
> > It is much better for the user to just select EM28XX and let the Kconfig do the
> > hard work of selecting what low-level driver applies for em28xx-based devices.
> >
> > This causes lots of select, being very hard to maintain. The better would be to
> > have a select-like clause that could check the dependencies automatically.
> >
> > Another alternative would be some sort of script (checkpatch.pl?) that would
> > check if all selected dependencies are ok.
>
> Ah, now I understand. You use "select" to enable options which aren't
> actually a build requirement for the selecting option.
Yes. That's why there are so many selects. Just a few of them are really to
select "real" build requirements.
> Another workaround for this UI limitation:
>
> config VIDEO_EM28XX
> tristate "Empia EM2800/2820/2840 USB video capture support"
> depends on WHATEVER_BUILD_REQUIREMENT_IS_LEFT
> select MAYBE_ANOTHER_BUILD_REQUIREMENT
> help
> ...
>
> comment "Empia EM28xx devices may require Philips SAA7113/4/5 video
> decoders"
> depends on VIDEO_EM28XX && VIDEO_SAA711X=n
>
> comment "Empia EM28xx devices may require Texas Instruments TVP5150
> video decoder"
> depends on VIDEO_EM28XX && VIDEO_TVP5150=n
>
> Still awkward, but now you don't have to copy VIDEO_SAA711X's and
> VIDEO_TVP5150's dependencies to VIDEO_EM28XX anymore.
This seems Interesting, but probably not very effective, since it would produce
a large amount of "warnings". However, we may use something like this:
comment "WARNING: Empia EM28xx devices require a video decoder"
depends on VIDEO_EM28XX && (VIDEO_TVP5150=n && VIDEO_SAA711X = n)
>
>
> Or another idea:
>
> Copy _all_ dependencies of drivers which can be selected by "...if
> VIDEO_HELPER_CHIPS_AUTO" to VIDEO_HELPER_CHIPS_AUTO.
I actually did this for tuners, on this changeset (still not at mainstream):
http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git;a=commitdiff;h=d10b3c6817fb3fed8e6cd6d64d47c187a615c952
>
> Of course all these issues go away as soon as somebody has implemented
> "select" with recursive dependency check.
Yes.
Cheers,
Mauro
next prev parent reply other threads:[~2008-05-06 22:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8287f540805041818g534c4e02qaadb0e749c5f3439@mail.gmail.com>
2008-05-03 19:38 ` Linus Torvalds
2008-05-03 21:47 ` Alistair John Strachan
2008-05-03 21:53 ` Alistair John Strachan
2008-05-04 12:30 ` Robin Holt
2008-05-04 13:56 ` Alistair John Strachan
2008-05-04 16:09 ` Robin Holt
2008-05-04 16:33 ` Alistair John Strachan
2008-05-05 21:04 ` Mauro Carvalho Chehab
2008-05-06 8:02 ` Alistair John Strachan
2008-05-06 10:31 ` Mauro Carvalho Chehab
2008-05-06 14:34 ` Stefan Richter
2008-05-06 14:54 ` Stefan Richter
2008-05-06 19:13 ` Mauro Carvalho Chehab
2008-05-06 19:44 ` Stefan Richter
2008-05-06 20:06 ` Mauro Carvalho Chehab
2008-05-06 20:47 ` Stefan Richter
2008-05-06 22:39 ` Mauro Carvalho Chehab [this message]
2008-05-06 23:36 ` Stefan Richter
2008-05-08 12:48 ` Mauro Carvalho Chehab
2008-05-08 14:11 ` Stefan Richter
2008-05-06 23:48 ` Stefan Richter
2008-05-04 7:29 ` [patch] sysfs: build fix Ingo Molnar
2008-05-04 18:40 ` Linux 2.6.26-rc1 Jan Engelhardt
2008-05-05 5:39 ` Andreas Mohr
2008-05-05 7:30 ` Ingo Molnar
2008-05-05 20:14 ` Mauro Carvalho Chehab
2008-05-06 13:07 ` Ingo Molnar
2008-05-07 8:35 ` Ingo Molnar
2008-05-05 23:51 ` Stephen Rothwell
2008-05-05 23:55 ` David Miller
2008-05-06 0:16 ` Andrew Morton
2008-05-06 5:57 ` Stephen Rothwell
2008-05-06 0:21 ` Ingo Molnar
2008-05-06 5:35 ` Stephen Rothwell
2008-05-06 6:56 ` David Miller
2008-05-06 7:26 ` Stephen Rothwell
2008-05-06 0:17 ` Ingo Molnar
2008-05-06 5:48 ` Stephen Rothwell
2008-05-06 6:07 ` Scheduling problems ? [ Was: Linux 2.6.26-rc1 ] J.A. Magallón
2008-05-06 13:11 ` Ingo Molnar
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=20080506193928.5acfc84d@gaivota \
--to=mchehab@infradead.org \
--cc=alistair@devzero.co.uk \
--cc=holt@sgi.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®