Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759625AbYGFUwS (ORCPT ); Sun, 6 Jul 2008 16:52:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757374AbYGFUv6 (ORCPT ); Sun, 6 Jul 2008 16:51:58 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:57126 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757191AbYGFUv5 (ORCPT ); Sun, 6 Jul 2008 16:51:57 -0400 Message-ID: <48713041.7000900@garzik.org> Date: Sun, 06 Jul 2008 16:51:13 -0400 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: David Woodhouse CC: david@lang.hm, Alan Cox , David Miller , andi@firstfloor.org, tytso@mit.edu, hugh@veritas.com, akpm@linux-foundation.org, kosaki.motohiro@jp.fujitsu.com, mchan@broadcom.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, netdev@vger.kernel.org Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" References: <1215178035.10393.763.camel@pmac.infradead.org> <486E2818.1060003@garzik.org> <20080704142753.27848ff8@lxorguk.ukuu.org.uk> <20080704.134329.209642254.davem@davemloft.net> <20080704220444.011e7e61@lxorguk.ukuu.org.uk> <1215376034.3189.127.camel@shinybook.infradead.org> In-Reply-To: <1215376034.3189.127.camel@shinybook.infradead.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.3 (----) X-Spam-Report: SpamAssassin version 3.2.4 on srv5.dvmed.net summary: Content analysis details: (-4.3 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 984 Lines: 26 David Woodhouse wrote: > On Sun, 2008-07-06 at 13:17 -0700, david@lang.hm wrote: >> if David W were to make it possible to not use the load_firmware() call to >> userspace and build the firmware into the driver (be it in a monolithic >> kernel or the module that contains the driver) > > You _can_ build the firmware into the kernel. Which is a problem for those rare situations, like oh say vendor kernels, where you can ship a driver update but not update the main kernel. Just like with modules, we were all given the _choice_ to use the new regime (modules) or stick with the old (100% monolithic kernel). Under any new system, firmware should be able to be compiled into the driver module itself -- as it is today. Jeff -- 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/