erebion/coreboot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

urara: Modify config to match hardware and depthcharge

Browse source 
The total bootprom size is 2MB, so coreboot should fit into
512KB. FMAP is placed in the depthcharde device tree definition at
0xe0000.

BRANCH=none
BUG=chrome-os-partner:31438
TEST=with the appropriate chromeos-bmpblk and deptcharge changes,
     chromeos-bootimage now builds successfully.

Change-Id: I5eb086a7529947e00cdee626e164b3328ff86ccb
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/232238
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
Vadim Bendebury 2014-11-29 14:34:11 -08:00 • committed by chrome-internal-fetch
commit 2f6a6c8497
1 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
configs/config.urara
View file

@ -1,7 +1,8 @@
CONFIG_VENDOR_GOOGLE=y
CONFIG_BOARD_GOOGLE_URARA=y
CONFIG_COREBOOT_ROMSIZE_KB_1024=y
CONFIG_COREBOOT_ROMSIZE_KB_512=y
# CONFIG_CONSOLE_SERIAL is not set
CONFIG_COLLECT_TIMESTAMPS=y
CONFIG_CONSOLE_CBMEM=y
CONFIG_FLASHMAP_OFFSET=0x00100000
CONFIG_FLASHMAP_OFFSET=0x000e0000