Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753295AbYGEHmU (ORCPT ); Sat, 5 Jul 2008 03:42:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752116AbYGEHmE (ORCPT ); Sat, 5 Jul 2008 03:42:04 -0400 Received: from ns.suse.de ([195.135.220.2]:44203 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752043AbYGEHmD (ORCPT ); Sat, 5 Jul 2008 03:42:03 -0400 Date: Sat, 05 Jul 2008 09:41:56 +0200 Message-ID: From: Takashi Iwai To: Olivier Galibert Cc: David Woodhouse , Hannes Reinecke , Theodore Tso , Jeff Garzik , Andi Kleen , David Miller , 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" In-Reply-To: <20080704231322.GA4410@dspnet.fr.eu.org> References: <20080703.162120.206258339.davem@davemloft.net> <486D6DDB.4010205@infradead.org> <87ej6armez.fsf@basil.nowhere.org> <1215177044.10393.743.camel@pmac.infradead.org> <486E2260.5050503@garzik.org> <1215178035.10393.763.camel@pmac.infradead.org> <20080704141014.GA23215@mit.edu> <486E3622.1000900@suse.de> <1215182557.10393.808.camel@pmac.infradead.org> <20080704231322.GA4410@dspnet.fr.eu.org> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/22.2 (x86_64-suse-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1342 Lines: 31 At Sat, 5 Jul 2008 01:13:22 +0200, Olivier Galibert wrote: > > On Fri, Jul 04, 2008 at 03:42:37PM +0100, David Woodhouse wrote: > > It doesn't yet; that patch is in linux-next. The firmware is shipped as > > part of the kernel source tree, and you currently need to run 'make > > firmware_install' to put it in /lib/firmware, although we're looking at > > making that easier because apparently having to run 'make > > firmware_install' is too hard... > > Won't that break multiple kernel installs on any binary packaging > system that cares about file collisions? Multiple kernel rpms > providing the same /lib/firmware files would break things wouldn't > they ? Yes, it will, if the firmware blobs are packed into the kernel package. In a long term, we can put firmware files into a separate, architecture independent noarch package, though. This will save the total package size, too. But, right now, it's difficult because the installation and build of firmware files depend on the kernel config. We'd need a make rule for installing the all firmware files for that purpose. Takashi -- 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/