netdev - Re: [bug?] tg3: Failed to load firmware "tigon/tg3

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 linux-hardening linux-cve-announce 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]

Message-ID: <48713041.7000900@garzik.org>
Date:	Sun, 06 Jul 2008 16:51:13 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	David Woodhouse <dwmw2@...radead.org>
CC:	david@...g.hm, Alan Cox <alan@...rguk.ukuu.org.uk>,
	David Miller <davem@...emloft.net>, andi@...stfloor.org,
	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"

David Woodhouse wrote:
> On Sun, 2008-07-06 at 13:17 -0700, david@...g.hm wrote:
>> if David W were to make it possible to not use the load_firmware() call to 
>> userspace and build the firmware into the driver (be it in a monolithic 
>> kernel or the module that contains the driver)
> 
> You _can_ build the firmware into the kernel.

Which is a problem for those rare situations, like oh say vendor 
kernels, where you can ship a driver update but not update the main kernel.

Just like with modules, we were all given the _choice_ to use the new 
regime (modules) or stick with the old (100% monolithic kernel).

Under any new system, firmware should be able to be compiled into the 
driver module itself -- as it is today.

	Jeff



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