linux-kernel - Re: preferred way of fw loading

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]

Message-Id: <1162369038.3044.80.camel@laptopd505.fenrus.org>
Date:	Wed, 01 Nov 2006 09:17:18 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	R.E.Wolff@...Wizard.nl
Subject: Re: preferred way of fw loading

On Wed, 2006-11-01 at 01:15 +0100, Jiri Slaby wrote:
> Hello,
> 
> is preferred to have firmware in kernel binary (and go through array of chars)
> or userspace (and load it through standard kernel api)?

generally the preferred way is for you to use request_firmware() API
which causes userspace to upload it to you via standard mechanisms.
This avoids kernel size bloat if it's not needed (by only having the
firmware in memory that is really really needed) and also avoids the
entire question of "can it be done within GPL" (not saying it can or
cannot, but usually if someone asks its a huge flamewar and this just
sidesteps the entire issue)

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