lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 04 Jul 2008 10:10:48 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	David Woodhouse <dwmw2@...radead.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"

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.

Certainly it is aware of the need to copy firmware in general, but that 
doesn't change the fact that the tg3 firmware will not make it into 
initramfs, without additional steps taken.

So, no, it doesn't "work fine" -- the firmware doesn't make it into the 
initramfs.

	Jeff


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists