| 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: Tue, 15 Jul 2008 10:44:05 -0700 From: David Woodhouse <dwmw2@...radead.org> To: Willy Tarreau <w@....eu> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, David Miller <davem@...emloft.net>, jeff@...zik.org, arjan@...radead.org, akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org Subject: Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more drivers. On Tue, 2008-07-15 at 19:35 +0200, Willy Tarreau wrote: > It's not only a problem of transfer, but also a problem of selection > of what to copy overthere. This is why the MODULE_FIRMWARE() tag exists. Most scripts tend to get this right already -- they _have_ to, since modern drivers have been using request_firmware() for some time already. > Please don't compare an upgrade of a working desktop or developer > machine with an installation from scratch of a server in an > uncomfortable location. Those are two completely different things. If your setup doesn't cope with MODULE_FIRMWARE(), it's likely to break when you next deploy a new server anyway -- because your new server will have new hardware, and your new hardware will have a modern driver. And modern drivers use request_firmware() _anyway_. -- 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