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

..

board.c

hadoken: Remove I2C and add ADC

2016-07-19 16:31:59 -07:00

board.h

g: CONFIG_FLASH should be optional

2016-10-02 15:19:21 -07:00

build.mk

hadoken: initial commit.

2014-07-29 02:21:22 +00:00

ec.tasklist

btle: Add common link layer code

2016-08-08 01:48:43 -07:00

gpio.inc

hadoken: Remove duplicate GPIO assignments

2016-09-02 18:34:14 -07:00