Files
OpenCellular/chip/mec1322
Bill Richardson fd88db3e9a g: CONFIG_FLASH should be optional
The application may need to read/write/erase the flash memory,
but we not want console users to do so. This CL adds
CONFIG_FLASH_PHYSICAL, which allows the higher-level CONFIG_FLASH
to be undefined while still providing the chip-specific
flash_physical_* accessor functions.

There aren't many board.h files that needed changes, since
CONFIG_FLASH_PHYSICAL is enabled by default, just like CONFIG_FLASH.

BUG=chrome-os-partner:57408
BRANCH=none
TEST=make buildall; try on Gru with and without CR50_DEV=1

See that it still boots, updates, wipes, restores, etc. without
linking common/flash.o in the production image; and that the
flash commands are still there in the dev build.

Signed-off-by: Bill Richardson <wfrichar@chromium.org>
Change-Id: I7eb1bbcb414b1c70ee427c4fcb5cea899dbb9e93
Reviewed-on: https://chromium-review.googlesource.com/391188
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>
2016-10-02 15:19:21 -07:00
..
2013-12-20 05:08:02 +00:00
2016-05-26 16:17:26 -07:00
2016-10-02 15:19:21 -07:00
2013-12-04 13:34:56 +00:00
2015-12-16 03:35:26 -08:00
2015-11-03 09:08:07 -08:00
2016-02-09 19:51:01 -08:00
2013-11-21 04:30:55 +00:00
2015-08-01 02:51:44 +00:00
2015-05-19 02:46:27 +00:00