From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 5 Jul 2008 02:01:24 -0400 From: Bill Fink Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" Message-Id: <20080705020124.ac73e979.billfink@mindspring.com> In-Reply-To: <20080705035215.GA15899@khazad-dum.debian.net> References: <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> <20080704235839.GA5649@khazad-dum.debian.net> <20080705035215.GA15899@khazad-dum.debian.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Henrique de Moraes Holschuh Cc: Trent Piepho , Olivier Galibert , David Woodhouse , Hannes Reinecke , Takashi Iwai , 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 List-ID: 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 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org