Julius Werner d5a460c8c7 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: I0793434116a8c568e19fe0dee24f13942fc50f25 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/238991 Reviewed-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/242150		2015-01-21 01:17:03 +00:00
..
cbfs.c	CBFS: Automate ROM image layout and remove hardcoded offsets	2014-12-03 06:09:54 +00:00
cbfs_core.c	CBFS: Automate ROM image layout and remove hardcoded offsets	2014-12-03 06:09:54 +00:00
Makefile.inc	libpayload: Change CONFIG_* to CONFIG_LP_* in the kconfig.	2013-08-14 17:05:33 -07:00
ram_media.c	libpayload: cbfs: Fix ram_media map() error return value	2015-01-21 01:17:03 +00:00