Bill Richardson 0860b19a97 cortex-m: CONFIG_RO_HEAD_ROOM should only affect RO image ...

When we add head room to the RO image, it's generally to provide
a chip-specific boot header of some sort. That header is only
needed for the RO image, not the RW image. The macro name implies
this, but this CL makes it so.

BRANCH=none
BUG=chrome-os-partner:43025, chrome-os-partner:44625
TEST=the cr50 image validates *and jumps to* the RW image at boot.

Change-Id: I0e5b2c32e232418970e01c7409ddcbbabd4786d5
Signed-off-by: Bill Richardson <wfrichar@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/296451
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>

2015-08-31 17:38:01 -07:00

..

cortex-m

cortex-m: CONFIG_RO_HEAD_ROOM should only affect RO image

2015-08-31 17:38:01 -07:00

cortex-m0

cortex-m0: Constrain target register in atomic read

2015-08-11 19:52:40 +00:00

host

Atomic: Mark the modified uint32_t volatile

2015-07-27 19:30:44 +00:00

nds32

nds32: use INT_MASK instead of GIE

2015-08-20 01:37:56 +00:00