[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250123223816.c695a6b85f568a2eb8719508@linux-foundation.org>
Date: Thu, 23 Jan 2025 22:38:16 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Guilherme G. Piccoli" <gpiccoli@...lia.com>
Cc: linux-kernel@...r.kernel.org, mcgrof@...nel.org, russ.weight@...ux.dev,
dakr@...nel.org, gregkh@...uxfoundation.org, rafael@...nel.org,
masahiroy@...nel.org, nathan@...nel.org, nicolas@...sle.eu,
kernel-dev@...lia.com, kernel@...ccoli.net, Thadeu Lima de Souza Cascardo
<cascardo@...lia.com>
Subject: Re: [PATCH] scripts: Add script to extract built-in firmware blobs
On Mon, 20 Jan 2025 16:04:26 -0300 "Guilherme G. Piccoli" <gpiccoli@...lia.com> wrote:
> Through the options CONFIG_EXTRA_FIRMWARE{_DIR} one is able to build
> a kernel including firmware blobs in a built-in fashion. This is
> usually the case of built-in drivers that require some blobs in
> order to work properly, for example, like in non-initrd based systems.
>
> Add hereby a script to extract these blobs from a non-stripped vmlinux,
> similar to the idea of "extract-ikconfig". The firmware loader interface
> saves such built-in blobs as rodata entries, having a field for the FW
> name as "_fw_<module_name>_<firmware_name>_bin"; the tool extracts files
> named "<module_name>_<firmware_name>" for each rodata firmware entry
> detected. It makes use of awk, bash, dd and readelf, pretty standard
> tooling for Linux development.
Please describe the use case(s) for this. ie, why are you suggesting
this be added to Linux?
Powered by blists - more mailing lists