From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bill Fink <billfink@mindspring.com>
Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"
Date: Sat, 5 Jul 2008 02:01:24 -0400
Message-ID: <20080705020124.ac73e979.billfink@mindspring.com>
References: <1215177044.10393.743.camel@pmac.infradead.org>
	<486E2260.5050503@garzik.org>
	<1215178035.10393.763.camel@pmac.infradead.org>
	<20080704141014.GA23215@mit.edu>
	<s5habgxloct.wl%tiwai@suse.de>
	<486E3622.1000900@suse.de>
	<1215182557.10393.808.camel@pmac.infradead.org>
	<20080704231322.GA4410@dspnet.fr.eu.org>
	<20080704235839.GA5649@khazad-dum.debian.net>
	<Pine.LNX.4.64.0807041742500.13075@t2.domain.actdsltmp>
	<20080705035215.GA15899@khazad-dum.debian.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Trent Piepho <tpiepho@freescale.com>,
	Olivier Galibert <galibert@pobox.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Hannes Reinecke <hare@suse.de>, Takashi Iwai <tiwai@suse.de>,
	Theodore Tso <tytso@mit.edu>, Jeff Garzik <jeff@garzik.org>,
	Andi Kleen <andi@firstfloor.org>,
	David Miller <davem@davemloft.net>, 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
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Return-path: <netdev-owner@vger.kernel.org>
Received: from elasmtp-kukur.atl.sa.earthlink.net ([209.86.89.65]:57233 "EHLO
	elasmtp-kukur.atl.sa.earthlink.net" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1752261AbYGEGB4 (ORCPT
	<rfc822;netdev@vger.kernel.org>); Sat, 5 Jul 2008 02:01:56 -0400
In-Reply-To: <20080705035215.GA15899@khazad-dum.debian.net>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On Sat, 5 Jul 2008, Henrique de Moraes Holschuh wrote:

> On Fri, 04 Jul 2008, Trent Piepho wrote:
> > On Fri, 4 Jul 2008, Henrique de Moraes Holschuh wrote:
> > > On Sat, 05 Jul 2008, Olivier Galibert wrote:
> > >> 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 ?
> > >
> > > We will probably need per-kernel directories, exactly like what is done for
> > > modules.  And since there are (now) both kernel-version-specific, and
> > > non-kernel-version-specific firmware, this means the firmware loader should
> > > look first on the version-specific directory (say, /lib/firmware/$(uname
> > > -r)/), then if not found, on the general directory (/lib/firmware).
> > 
> > How about /lib/modules/`uname -r`/firmware
> 
> I am fine with it, it certainly has a few advantages.

Why not put it in the same /lib/modules directory as the foo.ko
kernel module itself?  Then those who like to scp kernel modules
around (which I've done myself on occasion) just need to learn
to scp foo.* instead of foo.ko.  Why replicate a separate
/lib/modules/`uname -r`/firmware directory?

						-Bill