summaryrefslogtreecommitdiffstats
path: root/src/Kconfig
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2022-11-16 17:48:46 -0800
committerMartin Roth <martin.roth@amd.corp-partner.google.com>2022-11-18 17:19:44 +0000
commit4924cdb9ace88336cc37506a745ebef210f20767 (patch)
tree40cbd8b878659f77bdc8e94e119dcd25f89e48b3 /src/Kconfig
parentbe585d2ece60e04683a0e8377b3fdad5ac3e37cb (diff)
downloadcoreboot-4924cdb9ace88336cc37506a745ebef210f20767.tar.gz
coreboot-4924cdb9ace88336cc37506a745ebef210f20767.tar.bz2
coreboot-4924cdb9ace88336cc37506a745ebef210f20767.zip
build: List all Kconfigs in CBFS `config` file, compress it
The coreboot build system automatically adds a `config` file to CBFS that lists the exact Kconfig configuration that this image was built with. This is useful to reproduce a build after the fact or to check whether support for a specific feature is enabled in the image. However, the file is currently generated using the `savedefconfig` command to Kconfig, which generates the minimal .config file that is needed to produce the required config in a coreboot build. This is fine for reproduction, but bad when you want to check if a certain config was enabled, since many configs get enabled by default or pulled in through another config's `select` statement and thus don't show up in the defconfig. This patch tries to fix that second use case by instead including the full .config instead. In order to save some space, we can remove all comments (e.g. `# CONFIG_XXX is not set`) from the file, which still makes it easy to test for a specific config (if it's in the file you can extract the right value, if not you can assume it was set to `n`). We can also LZMA compress it since this file is never read by firmware itself and only intended for later re-extraction via cbfstool, which always has LZMA support included. On a sample Trogdor device the existing (uncompressed) `config` file takes up 519 bytes in CBFS, whereas the new (compressed) file after this patch will take up 1832 bytes -- still a small amount that should hopefully not break the bank for anyone. Signed-off-by: Julius Werner <jwerner@chromium.org> Change-Id: I5259ec6f932cdc5780b8843f46dd476da9d19728 Reviewed-on: https://review.coreboot.org/c/coreboot/+/69710 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Yu-Ping Wu <yupingso@google.com> Reviewed-by: Jakub Czapiga <jacz@semihalf.com> Reviewed-by: Martin Roth <martin.roth@amd.corp-partner.google.com>
Diffstat (limited to 'src/Kconfig')
-rw-r--r--src/Kconfig4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/Kconfig b/src/Kconfig
index f30a1bb68336..f16b53c47da7 100644
--- a/src/Kconfig
+++ b/src/Kconfig
@@ -211,9 +211,9 @@ config INCLUDE_CONFIG_FILE
Saying Y here will increase the image size by 2-3KB.
- You can use the following command to easily list the options:
+ You can then use cbfstool to extract the config from a final image:
- grep -a CONFIG_ coreboot.rom
+ cbfstool coreboot.rom extract -n config -f <output file path>
Alternatively, you can also use cbfstool to print the image
contents (including the raw 'config' item we're looking for).