Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758362AbYGDOHs (ORCPT ); Fri, 4 Jul 2008 10:07:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753478AbYGDOHi (ORCPT ); Fri, 4 Jul 2008 10:07:38 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:42629 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751746AbYGDOHh (ORCPT ); Fri, 4 Jul 2008 10:07:37 -0400 Message-ID: <486E2E9B.20200@garzik.org> Date: Fri, 04 Jul 2008 10:07:23 -0400 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: David Woodhouse CC: Andi Kleen , David Miller , tytso@mit.edu, 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" References: <1215093175.10393.567.camel@pmac.infradead.org> <20080703173040.GB30506@mit.edu> <1215111362.10393.651.camel@pmac.infradead.org> <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> <486E2818.1060003@garzik.org> <1215179161.10393.773.camel@pmac.infradead.org> In-Reply-To: <1215179161.10393.773.camel@pmac.infradead.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.3 (----) X-Spam-Report: SpamAssassin version 3.2.4 on srv5.dvmed.net summary: Content analysis details: (-4.3 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 853 Lines: 23 David Woodhouse wrote: > On Fri, 2008-07-04 at 09:39 -0400, Jeff Garzik wrote: >> You have been told repeatedly that cp(1) and scp(1) are commonly used >> to transport the module David and I care about -- tg3. It's been a >> single file module since birth, and people take advantage of that >> fact. > > And you can _continue_ to do that. You'd need to install the firmware > just once, and that's all. It's a non-issue, and it isn't _worth_ the > added complexity of building the firmware into the module. We can stop there. Real-world examples are apparently non-issues not worth your time. Jeff -- 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/