From: Johannes Stezenbach <js@linuxtv.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Oliver Endriss <o.endriss@gmx.de>,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Andrew de Quincey <adq_dvb@lidskialf.net>
Subject: Re: [patch, 2.6.26-rc2] dvb: drivers/media/dvb/ttpci/fdump firmware build error fix
Date: Tue, 13 May 2008 20:18:34 +0200 [thread overview]
Message-ID: <20080513181834.GA29133@linuxtv.org> (raw)
In-Reply-To: <20080513164238.GB21877@elte.hu>
On Tue, May 13, 2008 at 06:42:38PM +0200, Ingo Molnar wrote:
>
> * Johannes Stezenbach <js@linuxtv.org> wrote:
>
> > On Tue, May 13, 2008 at 04:33:54PM +0200, Oliver Endriss wrote:
> > > Johannes Stezenbach wrote:
> > > > You can put PREVENT_FIRMWARE_BUILD=y in your allrandom.config.
> > >
> > > Sure. And without the patch you can simply add
> > > - STANDALONE=y or
> > > - DVB_AV7110_FIRMWARE=n
> > > to your allrandom.config. ;-)
> >
> > It is desirable to have one generic "don't break the build because of
> > missing firmware binaries" option, isn't it?
>
> it's a bit confusing. PREVENT_FIRMWARE_BUILD=y is the 'weaker' option -
> a driver might still be operational (with its default firmware), even if
> no firmware is built. STANDALONE=y is the stronger option - if a driver
> depends on that it means that the driver cannot be built (and used) at
> all without a firmware file. To be on the safe side users who have no
> firmware needs should set both options. (and that's the default as well)
Seems like I'm confused now...
CONFIG_STANDALONE
Prompt: Select only drivers that don't need compile-time external firmware
PREVENT_FIRMWARE_BUILD
Prompt: Prevent firmware from being built
I guess selecting either one should prevent the build issue
you got, so your patch is right. But I also was wrong on
the meaning of STANDALONE...
Now I wonder why PREVENT_FIRMWARE_BUILD exists at all.
Johannes
next prev parent reply other threads:[~2008-05-13 18:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 10:12 [patch, 2.6.26-rc2] dvb: drivers/media/dvb/ttpci/fdump firmware build error fix Ingo Molnar
2008-05-12 17:30 ` Oliver Endriss
2008-05-12 19:46 ` Johannes Stezenbach
2008-05-12 20:18 ` Oliver Endriss
2008-05-12 20:30 ` Oliver Endriss
2008-05-12 20:46 ` Johannes Stezenbach
2008-05-13 9:50 ` Ingo Molnar
2008-05-13 14:33 ` Oliver Endriss
2008-05-13 14:49 ` Ingo Molnar
2008-05-13 15:23 ` Johannes Stezenbach
[not found] ` <20080513163930.GB21678@elte.hu>
2008-05-13 16:42 ` Ingo Molnar
2008-05-13 18:18 ` Johannes Stezenbach [this message]
2008-05-13 23:49 ` Oliver Endriss
[not found] ` <20080513163647.GA21678@elte.hu>
2008-05-13 16:41 ` Ingo Molnar
2008-05-13 17:01 ` Johannes Stezenbach
2008-05-14 0:55 ` Oliver Endriss
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=20080513181834.GA29133@linuxtv.org \
--to=js@linuxtv.org \
--cc=adq_dvb@lidskialf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
--cc=o.endriss@gmx.de \
/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.