google/panther: Fix RW ramstage index

Without this patch coreboot will always use the read-only version
of ramstage, even if there is a read-write version available.

Signed-off-by: Stefan Reinauer <reinauer@google.com>

BRANCH=panther
BUG=chrome-os-partner:25870
TEST=Install different RO and RW version, check in cbmem log that
     coreboot's romstage and ramstage have different timestamps
     in their banners.

Change-Id: I723a3d4479d59534660728d891a9f40a077b4ef0
Reviewed-on: https://chromium-review.googlesource.com/186664
Commit-Queue: Stefan Reinauer <reinauer@chromium.org>
Tested-by: Stefan Reinauer <reinauer@chromium.org>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
This commit is contained in:
Stefan Reinauer 2014-02-14 13:22:30 -08:00 committed by chrome-internal-fetch
commit 3add52e2d1

View file

@ -23,7 +23,7 @@ config BOARD_SPECIFIC_OPTIONS # dummy
config VBOOT_RAMSTAGE_INDEX
hex
default 0x2
default 0x1
config MAINBOARD_DIR
string