[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1215180802.10393.783.camel@pmac.infradead.org>
Date: Fri, 04 Jul 2008 15:13:22 +0100
From: David Woodhouse <dwmw2@...radead.org>
To: Jeff Garzik <jeff@...zik.org>
Cc: Takashi Iwai <tiwai@...e.de>, Hugh Dickins <hugh@...itas.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
mchan@...adcom.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
netdev@...r.kernel.org
Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"
On Fri, 2008-07-04 at 10:10 -0400, Jeff Garzik wrote:
> David Woodhouse wrote:
> > On Fri, 2008-07-04 at 09:42 -0400, Jeff Garzik wrote:
> >> mkinitrd and similar scripts must be updated, so that drivers that
> >> worked prior to dwmw2's changes will continue to work after dwmw2's
> >> changes.
> >
> >> If you fail to update some script somewhere, then the driver will be
> >> copied into the initramfs, but not the firmware, with obvious results.
> >
> > No, mkinitrd works fine, because a whole boatload of drivers _already_
> > require it to work that way and have done for a long time.
> >
> > Either you are severely mistaken, or you are being deliberately
> > misleading.
>
> It is a fact that mkinitrd, today, is unaware of your new system of
> obtaining firmware from the kernel source[or build] tree.
Of _course_ it is. Just as it's unaware of the need to download the b43
driver and b43-fwcutter and extract it.... what was your point, again?
I'm working on making the required firmware get installed as part of
'make modules_install'. We already discussed that. There's no need for
you to continue crying wolf with nonsense like 'mkinitrd won't work'.
--
dwmw2
--
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