From 40e936a1990a3dfd6fd2b8e2eab34643ecb7f470 Mon Sep 17 00:00:00 2001 From: Paul Menzel Date: Sun, 25 May 2014 12:20:51 +0200 Subject: util/board_status/board_status.sh: Save ROM contents in `cbfs.txt` The ROM content (CBFS content) captured with cbfstool build/coreboot.rom print is useful for two reasons. 1. With the used configuration for the build in `.config`, it can be compared how the size for romstage and ramstage change over time. To make that reproducible the used toolchain should also be stored somewhere in the future. 2. With the CBFS content the time stamps can be better interpreted. For example, the size of the payload file is needed to interpret the time stamp for loading the payload. Change-Id: If77ca6412b1710e560f405f9a48df613c1819d36 Signed-off-by: Paul Menzel Reviewed-on: http://review.coreboot.org/5867 Tested-by: build bot (Jenkins) Reviewed-by: David Hendricks Reviewed-by: Edward O'Callaghan Reviewed-by: Marc Jones --- util/board_status/board_status.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/util/board_status/board_status.sh b/util/board_status/board_status.sh index 3cff2316ed..51868c829d 100755 --- a/util/board_status/board_status.sh +++ b/util/board_status/board_status.sh @@ -145,6 +145,7 @@ tmpdir=$(mktemp -d) cbfstool_cmd="util/cbfstool/cbfstool" test_cmd $LOCAL "$cbfstool_cmd" $cbfstool_cmd build/coreboot.rom extract -n config -f ${tmpdir}/config.txt +$cbfstool_cmd build/coreboot.rom print > ${tmpdir}/cbfs.txt mainboard_dir="$(grep CONFIG_MAINBOARD_DIR ${tmpdir}/config.txt | awk -F '"' '{ print $2 }')" vendor=$(echo "$mainboard_dir" | awk -F '/' '{ print $1 }') mainboard=$(echo "$mainboard_dir" | awk -F '/' '{ print $2 }') -- cgit v1.2.3