Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753489AbYGEDwb (ORCPT ); Fri, 4 Jul 2008 23:52:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751162AbYGEDwV (ORCPT ); Fri, 4 Jul 2008 23:52:21 -0400 Received: from out5.smtp.messagingengine.com ([66.111.4.29]:48539 "EHLO out5.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751107AbYGEDwU (ORCPT ); Fri, 4 Jul 2008 23:52:20 -0400 X-Sasl-enc: P14xMniCFThzSnJAlaapJ9egknaIiha5c/mhioOVLYGp 1215229938 Date: Sat, 5 Jul 2008 00:52:15 -0300 From: Henrique de Moraes Holschuh To: Trent Piepho Cc: 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 Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" Message-ID: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-GPG-Fingerprint: 1024D/1CDB0FE3 5422 5C61 F6B7 06FB 7E04 3738 EE25 DE3F 1CDB 0FE3 User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1321 Lines: 28 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. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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/