From: Oliver Endriss <o.endriss@gmx.de>
To: Johannes Stezenbach <js@linuxtv.org>
Cc: Ingo Molnar <mingo@elte.hu>,
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: Wed, 14 May 2008 01:49:47 +0200 [thread overview]
Message-ID: <200805140149.48569@orion.escape-edv.de> (raw)
In-Reply-To: <20080513181834.GA29133@linuxtv.org>
Johannes Stezenbach wrote:
> 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
After reading the text again I still think that my understanding is
correct [1].
CONFIG_STANDALONE disables drivers which require a firmware file at
compile-time. av7110 with DVB_AV7110_FIRMWARE=y is this kind of driver.
PREVENT_FIRMWARE_BUILD controls building (= compiling) the firmware from
source. As we do not ship the source of the av7110 firmware, this option
does not apply.
So everything should be fine 'as is'.
CU
Oliver
Notes:
[1] Of course, I am open to corrections from the kbuild gurus. ;-)
--
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
----------------------------------------------------------------
next prev parent reply other threads:[~2008-05-14 0:15 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
2008-05-13 23:49 ` Oliver Endriss [this message]
[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=200805140149.48569@orion.escape-edv.de \
--to=o.endriss@gmx.de \
--cc=adq_dvb@lidskialf.net \
--cc=js@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
/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