Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755530AbYGEUzr (ORCPT ); Sat, 5 Jul 2008 16:55:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752874AbYGEUzh (ORCPT ); Sat, 5 Jul 2008 16:55:37 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:39206 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752744AbYGEUzg (ORCPT ); Sat, 5 Jul 2008 16:55:36 -0400 Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" From: David Woodhouse To: Christoph Hellwig Cc: Andi Kleen , Olivier Galibert , Takashi Iwai , Hannes Reinecke , Theodore Tso , Jeff Garzik , 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 In-Reply-To: <20080705171316.GA3615@infradead.org> References: <486E3622.1000900@suse.de> <1215182557.10393.808.camel@pmac.infradead.org> <20080704231322.GA4410@dspnet.fr.eu.org> <20080705105317.GA44773@dspnet.fr.eu.org> <486F596C.8050109@firstfloor.org> <20080705120221.GC44773@dspnet.fr.eu.org> <486F6494.8020108@firstfloor.org> <1215260166.10393.816.camel@pmac.infradead.org> <20080705171316.GA3615@infradead.org> Content-Type: text/plain Date: Sat, 05 Jul 2008 21:55:11 +0100 Message-Id: <1215291312.3189.88.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: 1069 Lines: 25 On Sat, 2008-07-05 at 13:13 -0400, Christoph Hellwig wrote: > On Sat, Jul 05, 2008 at 01:16:06PM +0100, David Woodhouse wrote: > > It almost never happens that you have kernel versions which _need_ > > different firmware installed. In almost all cases, the older driver will > > continue to work just fine with the newer firmware (and its bug-fixes). > > > > The ABI between driver and firmware rarely changes in such a fashion > > that you have to update the driver in lock-step -- and even on the > > occasions that it does, it's not hard to simply change the name of the > > "new-style" firmware so that it doesn't stomp on the old one (Think of > > it like an soname). > > That's unfortunately not true. There are a lot of drivers that rely > on specific firmware versions. Do you have examples of such? -- 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/