Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750791AbWH3LxB (ORCPT ); Wed, 30 Aug 2006 07:53:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750821AbWH3LxB (ORCPT ); Wed, 30 Aug 2006 07:53:01 -0400 Received: from coyote.holtmann.net ([217.160.111.169]:27079 "EHLO mail.holtmann.net") by vger.kernel.org with ESMTP id S1750791AbWH3LxA (ORCPT ); Wed, 30 Aug 2006 07:53:00 -0400 Subject: Re: [PATCH] MODULE_FIRMWARE for binary firmware(s) From: Marcel Holtmann To: Greg KH Cc: James Bottomley , linux-kernel In-Reply-To: <20060829201628.GA13807@kroah.com> References: <1156802900.3465.30.camel@mulgrave.il.steeleye.com> <1156857214.5613.72.camel@aeonflux.holtmann.net> <20060829201628.GA13807@kroah.com> Content-Type: text/plain Date: Wed, 30 Aug 2006 15:49:57 +0200 Message-Id: <1156945797.4026.81.camel@aeonflux.holtmann.net> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1557 Lines: 42 Hi Greg, > > > Right now, various kernel modules are being migrated over to use > > > request_firmware in order to pull in binary firmware blobs from userland > > > when the module is loaded. This makes sense. > > > > > > However, there is right now little mechanism in place to automatically > > > determine which binary firmware blobs must be included with a kernel in > > > order to satisfy the prerequisites of these drivers. This affects > > > vendors, but also regular users to a certain extent too. > > > > > > The attached patch introduces MODULE_FIRMWARE as a mechanism for > > > advertising that a particular firmware file is to be loaded - it will > > > then show up via modinfo and could be used e.g. when packaging a kernel. > > > > this patch was debated, but we never came to a final conclusion. I am > > all for it. It is simple and can improve the current situation. > > > > > Signed-off-by: Jon Masters > > > > Signed-off-by: Marcel Holtmann > > Since your tree will depend on this change, you can add it there and > add: > > Signed-off-by: Greg Kroah-Hartman > > from me to the patch. do we consider this 2.6.18 or 2.6.19 material? For the Bluetooth subsystem I can easily write a patch that makes use of it. Regards Marcel - 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/