From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756987AbYE3KjJ (ORCPT ); Fri, 30 May 2008 06:39:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753271AbYE3Ki4 (ORCPT ); Fri, 30 May 2008 06:38:56 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:55974 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753119AbYE3Kiz (ORCPT ); Fri, 30 May 2008 06:38:55 -0400 Subject: Re: [Ksummit-2008-discuss] RFC: Moving firmware blobs out of the kernel. From: David Woodhouse To: Alan Cox Cc: Greg KH , Yinghai Lu , Matthew Wilcox , Arjan van de Ven , James.Bottomley@hansenpartnership.com, ksummit-2008-discuss@lists.linux-foundation.org, David Miller , linux-kernel@vger.kernel.org In-Reply-To: <20080530102008.6645a0ad@core> References: <1211995212.3445.52.camel@localhost.localdomain> <20080528.225826.40264516.davem@davemloft.net> <1212041839.8888.38.camel@pasglop> <20080529124548.GC8065@mit.edu> <1212077700.26088.83.camel@shinybook.infradead.org> <20080529164745.GA21763@kroah.com> <483F1232.4010003@linux.intel.com> <20080529204736.GZ22636@parisc-linux.org> <86802c440805291355p5697c775k5f0beb8163688058@mail.gmail.com> <20080529210304.GA8866@kroah.com> <20080530102008.6645a0ad@core> Content-Type: text/plain Date: Fri, 30 May 2008 13:38:38 +0300 Message-Id: <1212143919.29244.9.camel@shinybook.infradead.org> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1 (2.22.1-2.fc9) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.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 On Fri, 2008-05-30 at 10:20 +0100, Alan Cox wrote: > > Not all firmware has the ability to check the version :( > > > > So while Arjan's goal would be nice, Matthew is right, this can't happen > > for all types of firmware. > > Well for loaded or packaged firmware it can happen. Just stick a revision > number on the start of the firmware file and check it rather than load it > into the hardware in that specific driver. Or append it to the name of the firmware file, in some cases. -- dwmw2