| 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: Thu, 11 Sep 2008 08:31:08 -0700 From: David Woodhouse <dwmw2@...radead.org> To: Frans Pop <elendil@...net.nl> Cc: davem@...emloft.net, jeffm@...e.com, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, torvalds@...ux-foundation.org, Jeff Garzik <jeff@...zik.org> Subject: Re: [PATCH] firmware: Allow release-specific firmware dir On Thu, 2008-09-11 at 17:24 +0200, Frans Pop wrote: > Did you read the second part of the mail explaining why having a > single "firmware" package is not a good idea? Yes, but it was nonsense, so I ignored it. "The reason for this is the possibility that a driver and its firmware may be dropped from the upstream kernel source." That doesn't happen very often, and you _certainly_ don't need to immediately drop the firmware if it does. It's another reason why it's better to be shipping from the external linux-firmware repository at git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git -- because if a driver _does_ go away, that repository would continue to carry the firmware files. But since that's such an infrequent occurrence, there's no massive rush. Using the firmware in the kernel tree is fine for now. -- David Woodhouse Open Source Technology Centre David.Woodhouse@...el.com Intel Corporation -- 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