linux-kernel - Re: [v4l-dvb-maintainer] Options depending on STANDALONE

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <Pine.LNX.4.58.0608031610110.9178@shell2.speakeasy.net>
Date:	Thu, 3 Aug 2006 16:40:25 -0700 (PDT)
From:	Trent Piepho <xyzzy@...akeasy.org>
To:	Adrian Bunk <bunk@...sta.de>
cc:	Dave Jones <davej@...hat.com>, Greg KH <greg@...ah.com>,
	Zachary Amsden <zach@...are.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>,
	Andrew Morton <akpm@...l.org>,
	Christoph Hellwig <hch@...radead.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Jack Lo <jlo@...are.com>, v4l-dvb-maintainer@...uxtv.org,
	linux-acpi@...r.kernel.org
Subject: Re: [v4l-dvb-maintainer] Options depending on STANDALONE

On Thu, 3 Aug 2006, Adrian Bunk wrote:
> On Thu, Aug 03, 2006 at 03:56:17PM -0400, Dave Jones wrote:
> > You're describing PREVENT_FIRMWARE_BUILD.  The text Zach quoted is from
> > STANDALONE, which is something else completely.  That allows us to not
> > build drivers that pull in things from /etc and the like during compile.
> > (Whoever thought that was a good idea?)
>
>
> Is DVB_AV7110_FIRMWARE really still required?
> ALL other drivers work without such an option.

The other DVB drivers that need firmware load it when the device is opened
or used (ie.  a channel is tuned).  At least for the ones I'm familiar
with.  If they are compiled directly into the kernel, they can still use
FW_LOADER since the loading won't happen until utill well after booting is
done.

For AV7110, it looks like the firmware loading is done when the driver is
first initialized.  If AV7110 is compiled into the kernel, FW_LOADER can
not be used.  The filesystem with the firmware won't be mounted yet.

So AV7110 has an option to compile a firmware file into the driver.
-
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/