Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760049AbYGFWKx (ORCPT ); Sun, 6 Jul 2008 18:10:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756673AbYGFWKn (ORCPT ); Sun, 6 Jul 2008 18:10:43 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:41105 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756588AbYGFWKm (ORCPT ); Sun, 6 Jul 2008 18:10:42 -0400 Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" From: David Woodhouse To: Jeff Garzik 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 In-Reply-To: <48713B73.6030708@garzik.org> 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> <1215377814.3189.137.camel@shinybook.infradead.org> <48713B73.6030708@garzik.org> Content-Type: text/plain Date: Sun, 06 Jul 2008 23:10:25 +0100 Message-Id: <1215382225.3189.174.camel@shinybook.infradead.org> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 (2.22.2-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 Content-Length: 1270 Lines: 30 On Sun, 2008-07-06 at 17:38 -0400, Jeff Garzik wrote: > David Woodhouse wrote: > > On Sun, 2008-07-06 at 13:52 -0700, david@lang.hm wrote: > >> On Sun, 6 Jul 2008, 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. > >> right, but not into a module. you have half of the answer in place, but > >> not all of it. > > > > The useful half. If you have userspace to load modules, you have > > userspace to load firmware too. > > Existing examples have already been provided where this logic fails. I even provided such an example, where your script greps the module for 'request_firmware' and fails if there's a match. I don't think any of the other provided examples were _much_ more sensible than that... -- 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/