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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 04 Jul 2008 15:26:55 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Hugh Dickins <hugh@...itas.com>, Jeff Garzik <jeff@...zik.org>,
	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"

At Fri, 04 Jul 2008 14:17:51 +0100,
David Woodhouse wrote:
> 
> On Fri, 2008-07-04 at 13:06 +0200, Takashi Iwai wrote:
> > Hmm, I got this error even with CONFIG_FIRMWARE_IN_KERNEL=y.
> > 
> > Through a quick look at the code, the firmwares are not built indeed.
> > I guess the fix like the following needed for building firmwares for
> > modules.  Now trying to build the kernel again to check this...
> 
> For modules, you just need run
> 	'make INSTALL_FW_PATH=/lib/firmare firmware_install'.
> 
> I should...
> 
> 1. Change the default to /lib/firmware so that you don't have to set
>    INSTALL_FW_PATH.
> 2. Add that to the 'make help' text.
> 3. Look at making 'make modules_install' installl the firmware required
>    by the modules it's installing, so you don't even need to do
>    _anything_ new.

Ah I see.  I thought you implemented the built-in firmware even for
modules, but apparently it's not.

Is mkinitrd clever enough to put all needed firmware files to initrd
automatically?  Otherwise this can still break the existing setup...


thanks,

Takashi
--
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