linux-kernel - Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more drivers.

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]

Date:	Tue, 15 Jul 2008 12:37:09 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Jeff Garzik <jeff@...zik.org>,
	Henrique de Moraes Holschuh <hmh@....eng.br>,
	Frans Pop <elendil@...net.nl>, arjan@...radead.org,
	akpm@...ux-foundation.org, dwmw2@...radead.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.

Linus Torvalds wrote:

> Why compile them into the module, when that's just the _inflexible_ model?
> 
> Why not just install them with the module (perhaps in the module 
> directory, perhaps not), and just load them? 
> 
> Really. You _do_ have do to "make modules_install" or similar. That has 
> _already_ got inter-file dependencies (ie some modules simply depend on 
> other modules). I'm not seeing why you cannot accept change.

Even if the end goal is to support more flexible firmware loading, it 
would seem to make sense to allow building the firmware into the 
module--if only as an interim step to avoid breaking existing setups.

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