diff options
author | Julius Werner <jwerner@chromium.org> | 2015-01-06 21:34:19 -0800 |
---|---|---|
committer | Patrick Georgi <pgeorgi@google.com> | 2015-03-21 11:04:39 +0100 |
commit | 51421633d534752c2d677a5255f9583ecdcd4a60 (patch) | |
tree | 40b447b2476e6a19fb602d2d2a0b03f4146736a9 /payloads/libpayload/bin | |
parent | 272afe8030e1c0f371617a654656ec22c1b67ccf (diff) | |
download | coreboot-51421633d534752c2d677a5255f9583ecdcd4a60.tar.xz |
libpayload: cbfs: Fix ram_media map() error return value
The correct return value for errors on a cbfs_media->map() call is
CBFS_MEDIA_INVALID_MAP_ADDRESS, not NULL. Not sure if that's the best
choice (since 0xffffffff is probably a more likely valid address than 0
there), but that's what the upper layers expect right now.
BRANCH=veyron
BUG=None
TEST=Press CTRL+L with an RW_LEGACY section filled with 0xff. Observe
how cbfs_get_header() returns failure without doing a bunch of NULL
pointer accesses first (not that those have any visible effect on
Veyron, but that's another problem...)
Change-Id: I3d012fc9af9da6e01159990a6bdd62c38fc22329
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Original-Commit-Id: 3a609e17bb9b0ef4d3a833f72fa4fbfd8e8cb0ab
Original-Change-Id: I0793434116a8c568e19fe0dee24f13942fc50f25
Original-Signed-off-by: Julius Werner <jwerner@chromium.org>
Original-Reviewed-on: https://chromium-review.googlesource.com/238991
Original-Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: http://review.coreboot.org/8758
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Diffstat (limited to 'payloads/libpayload/bin')
0 files changed, 0 insertions, 0 deletions