Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758238Ab1EBV47 (ORCPT ); Mon, 2 May 2011 17:56:59 -0400 Received: from casper.infradead.org ([85.118.1.10]:59924 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755963Ab1EBV46 (ORCPT ); Mon, 2 May 2011 17:56:58 -0400 Subject: Re: linux-firmware tree From: David Woodhouse To: Mike Waychison Cc: "linux-kernel@vger.kernel.org" In-Reply-To: References: <1304365095.6400.20.camel@macbook.infradead.org> Content-Type: text/plain; charset="UTF-8" Date: Mon, 02 May 2011 22:56:54 +0100 Message-ID: <1304373414.6400.23.camel@macbook.infradead.org> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 936 Lines: 23 On Mon, 2011-05-02 at 14:40 -0700, Mike Waychison wrote: > I don't see anything in the build (looking at scripts/Makefile.fwinst > in particular) that allows the build to enumerate out-of-tree firmware > files required by drivers. Do you have any thoughts on how this could > be enumerated? (if it isn't already?) Using the MODULE_FIRMWARE tags of the drivers which are built. This is actually the reason we haven't removed the legacy firmware from the source tree yet; it's waiting for me to implement that bit. It shouldn't be hard to post-process the modules and list the firmware blobs that they reference. We'd just want to make it do the same for built-in drivers too. -- 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/