From: Sam Ravnborg <sam@ravnborg.org>
To: David Miller <davem@davemloft.net>
Cc: tiwai@suse.de, mingo@elte.hu, mchehab@infradead.org,
akpm@linux-foundation.org, linux-dvb-maintainer@linuxtv.org,
video4linux-list@redhat.com, linux-kernel@vger.kernel.org,
efault@gmx.de
Subject: Re: [patch, -git] media/video/sound build fix, TEA5761/TEA5767
Date: Wed, 30 Apr 2008 13:29:59 +0200 [thread overview]
Message-ID: <20080430112959.GA32556@uranus.ravnborg.org> (raw)
In-Reply-To: <20080430.041703.89847530.davem@davemloft.net>
On Wed, Apr 30, 2008 at 04:17:03AM -0700, David Miller wrote:
> From: Takashi Iwai <tiwai@suse.de>
> Date: Wed, 30 Apr 2008 13:11:31 +0200
>
> > IMO, it's the reverse selection from sound to V4L that makes things
> > complicated. I believe it's better to fix it as a normal dependency.
> >
> > How about the patch below?
>
> The question that remains is what does this mean for users?
>
> How does a user, who wants to enable this 'sound' driver,
> learn that they must enable the v4l subsystem in order to
> do so?
[OT to the actual problem]
I have envisioned something like a "requires tag" that
would list what a config symbols needs.
Like in this case it would have been:
requires V4L
This should in the frontends then if the user selects a symbol
where the 'requires' are not satisfied with a window listing
the menuentries for the symbol that the user needs to
enable to satisfy what the original symbol requires.
This is the only way to do this in a way so the
user is actually aware that enabling a webcam also enables USB.
Or at least this is my best suggestion.
But sorry - I have not implemented it.
And it is likely more complicated than I foresee.
Sam
next prev parent reply other threads:[~2008-04-30 11:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 11:01 [patch, -git] media/video/sound build fix, TEA5761/TEA5767 Ingo Molnar
2008-04-30 11:11 ` Takashi Iwai
2008-04-30 11:15 ` Ingo Molnar
2008-04-30 11:18 ` Ingo Molnar
2008-04-30 11:21 ` Ingo Molnar
2008-04-30 11:58 ` Takashi Iwai
2008-04-30 12:05 ` Ingo Molnar
2008-04-30 12:36 ` [v4l-dvb-maintainer] " Michael Krufky
2008-04-30 12:01 ` Takashi Iwai
2008-04-30 11:17 ` David Miller
2008-04-30 11:29 ` Sam Ravnborg [this message]
2008-04-30 12:09 ` Takashi Iwai
2008-04-30 12:18 ` Ingo Molnar
2008-05-02 15:06 ` Sam Ravnborg
2008-05-05 20:34 ` Mauro Carvalho Chehab
2008-04-30 11:54 ` Takashi Iwai
2008-04-30 11:13 ` Ingo Molnar
2008-04-30 12:04 ` Takashi Iwai
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=20080430112959.GA32556@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=efault@gmx.de \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
--cc=tiwai@suse.de \
--cc=video4linux-list@redhat.com \
/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