summaryrefslogtreecommitdiff
path: root/util/cbfstool/README.fmaptool
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2015-09-15 12:50:14 -0500
committerAaron Durbin <adurbin@chromium.org>2015-09-16 14:11:03 +0000
commitd7339411a983e562cddeba676384ad836bb56ec9 (patch)
tree74efa7d6ab2375ce4a8831b071f69a6a014295e9 /util/cbfstool/README.fmaptool
parentb39a974d75ac597b29eb83b5ce347a506e0e6015 (diff)
downloadcoreboot-d7339411a983e562cddeba676384ad836bb56ec9.tar.xz
cbfstool: provide metadata size to cbfs_locate_entry()
The cbfs_locate_entry() function had a hack in there which assumed a struct cbfs_stage data was being added in addition to the struct cbfs_file and name. Move that logic out to the callers while still maintaining the logic for consistency. The only impacted commands cbfs_add and cbfs_locate, but those are using the default 'always adding struct cbfs_stage' in addition to cbfs_file + name. Eventually those should be removed when cbfs_locate is removed as cbfs_add has no smarts related to the cbfs file type provided. BUG=chrome-os-partner:44827 BRANCH=None TEST=Built rambi. Change-Id: I2771116ea1ff439ea53b8886e1f33e0e637a79d4 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/11668 Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Diffstat (limited to 'util/cbfstool/README.fmaptool')
0 files changed, 0 insertions, 0 deletions