| 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
| ||
|
Message-Id: <1215204827.3189.13.camel@shinybook.infradead.org> Date: Fri, 04 Jul 2008 21:53:47 +0100 From: David Woodhouse <dwmw2@...radead.org> To: David Miller <davem@...emloft.net> Cc: jeff@...zik.org, 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" On Fri, 2008-07-04 at 13:37 -0700, David Miller wrote: > And for one, I have consistently argued that this "best practice" is > the "worst practice" from a technical perspective. It is the worst > because it means mistakes are possible to make between driver and > firmware versions. Even with versioning it is not fool proof. > Whereas if you link the firmware into the driver, it's impossible to > get wrong. And you've been wrong about that from the start, which is why the rest of the kernel has moved on while the drivers you control are left behind. But we've already stopped working on drivers/net; we're fixing the rest of the older drivers first. And every affected maintainer except you and Jeff seems _happy_ to see their drivers being brought up to date. -- dwmw2 -- 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