diff options
| author | Che-Liang Chiou <clchiou@chromium.org> | 2011-07-05 23:48:47 +0800 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2011-08-29 10:58:46 -0700 |
| commit | 52d0897b475d5110e08dd80f21d6471b428151ee (patch) | |
| tree | 4e35f1847669fe37420f9082b4cc2bb01a03726a /board/nvidia/seaboard | |
| parent | 8e1b679046c06c0e4f1a08acc518a222a460a522 (diff) | |
CHROMIUM: twostop: use fdt fmap layout and set active main firmware
Known issue
* I did not pack correct key block yet, and so when it tries to verify
R/W firmware in normal mode, it will fail due to key mismatching.
* If recovery boot is not activated by user request or nvcontext, the
recovery key will not be set properly, and kernel verification will
fail.
* In recovery boot, fwid is empty.
* Recovery boot seems not to have developer flag set properly.
TODO
* Read R/W firmware from mmc
BUG=chromium-os:17056
TEST=manual
1. Try all boot flows on Seaboard; not all succeeded
2. Observe that active main firmware is set correctly
Change-Id: I111a69d88c0d2b175ee2941c363246d160efe9de
Reviewed-on: http://gerrit.chromium.org/gerrit/3651
Tested-by: Che-Liang Chiou <clchiou@chromium.org>
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Diffstat (limited to 'board/nvidia/seaboard')
| -rw-r--r-- | board/nvidia/seaboard/flashmap-twostop.dts | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/board/nvidia/seaboard/flashmap-twostop.dts b/board/nvidia/seaboard/flashmap-twostop.dts index 826a6cbeb52..52e848de2aa 100644 --- a/board/nvidia/seaboard/flashmap-twostop.dts +++ b/board/nvidia/seaboard/flashmap-twostop.dts @@ -36,12 +36,12 @@ /* u-boot image including fdt: first ~450 KB */ firmware-image { - reg = <0x00000000 0x0006ff00>; + reg = <0x00000000 0x0007df00>; }; /* verification block: 64 KB */ verification-block { - reg = <0x0006ff00 0x00010000>; + reg = <0x0007df00 0x00002000>; }; /* frimware ID: 256 Bytes */ |