Subject: Re: [PATCH 00/18] firmware: moving drivers to request_firmware()
From: David Woodhouse <dwmw2@infradead.org>
To: Arkadiusz Miskiewicz <arekm@pld-linux.org>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <200806051207.50556.arekm@pld-linux.org>
References: <20080605.foo@pmac.infradead.org>
	 <200806051207.50556.arekm@pld-linux.org>
Content-Type: text/plain
Date: Thu, 05 Jun 2008 11:09:26 +0100
Message-Id: <1212660566.32207.179.camel@pmac.infradead.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1304
Lines: 29

On Thu, 2008-06-05 at 12:07 +0200, Arkadiusz Miskiewicz wrote:
> On Thursday 05 June 2008, David Woodhouse wrote:
> > Ignoring the set of 'make fw->data const' patches which have mostly
> > been already posted and are fairly trivial, this is the current content
> > of the firmware tree at git.infradead.org/users/dwmw2/firmware-2.6.git
> >
> > It starts by giving a way to build arbitrary firmware blobs into the
> > kernel while letting request_firmware() find them there, and then sets
> > about converting drivers to use request_firmware() instead of static
> > data blobs, now that we can do that without forcing the users to
> > actually  satisfy the firmware requests from userspace.
> 
> Will there be a way for userspace to know what firmware file is needed by 
> which driver? 
> 
> So for example geninitrd/mkinitrd will be able to put only required firmware 
> files into initrd/initramfs (without a need to maintain separate database 
> with driver <-> firmware file name mapping).

We've had that for a long time: MODULE_FIRMWARE().

-- 
dwmw2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/