| 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
| ||
|
Date: Fri, 04 Jul 2008 13:43:29 -0700 (PDT) From: David Miller <davem@...emloft.net> To: alan@...rguk.ukuu.org.uk Cc: jeff@...zik.org, dwmw2@...radead.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" From: Alan Cox <alan@...rguk.ukuu.org.uk> Date: Fri, 4 Jul 2008 14:27:53 +0100 > There are good sound reasons for having a firmware tree, the fact tg3 is > a bit of dinosaur in this area doesn't make it wrong. And bnx2, and bnx2x, and e100's ucode (hope David caught that one!). It isn't just tg3. External firmware is by design an error prone system, even with versioning. But by being built and linked into the driver, it is fool proof. On a technical basis alone, we would never disconnect a crucial component such as firmware, from the driver. The only thing charging these transoformations, from day one, is legal concerns. I've been against request_firmware() from the beginning, because they make life unnecessarily difficult, and it is error prone no matter how well you design the validation step. -- 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