[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080704153822.4db2f325@lxorguk.ukuu.org.uk>
Date: Fri, 4 Jul 2008 15:38:22 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Jeff Garzik <jeff@...zik.org>
Cc: David Woodhouse <dwmw2@...radead.org>,
Andi Kleen <andi@...stfloor.org>,
David Miller <davem@...emloft.net>, tytso@....edu,
hugh@...itas.com, akpm@...ux-foundation.org,
kosaki.motohiro@...fujitsu.com, mchan@...adcom.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
netdev@...r.kernel.org
Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"
On Fri, 04 Jul 2008 10:07:23 -0400
Jeff Garzik <jeff@...zik.org> wrote:
> 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 - real world issues and gains are measured on a scale across the
userbase not "Jeff's having a tantrum because his specific usage case
requires one extra copy once"
And we had the same argument over ten years ago about those evil module
things which stopped you just using scp to copy the kernel in one go.
Fortunately the nay sayers lost so we have modules.
Alan
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists