Hi Bin, On 6 January 2015 at 07:14, Bin Meng <[email protected]> wrote: > In theory U-Boot built for coreboot is supposed to run as a payload > to be loaded by coreboot on every board that coreboot supports. > The U-Boot build process uses SYS_CONFIG_NAME and DEFAULT_DEVICE_TREE > which are hardcoded in board defconfig and Kconfig files. For better > support of coreboot, we want to make these two options configurable > so that we can easily change them during 'make menuconfig' so that > the generated U-Boot image for coreboot is board configuration aware. > > Note v2/v3/v4 patch series aims to better support coreboot, while v1 > patch series just tried to resolve the issues seen on qemu. Several > issues are fixed to make coreboot support in U-Boot more robust. > > See v1 patch discussion > @ http://lists.denx.de/pipermail/u-boot/2015-January/200140.html > > The official qemu U-Boot support will come in the future. This patch > series have been tested with coreboot running on qemu and Intel Crown > Bay (my own unofficiall simple port, not in coreboot mainline) then > loading the U-Boot built with the new mechanism. > > Changes in v4: > - Hide XIP_ROM_SIZE too after rebase > - Rebase to u-boot-x86/next
I need to change XIP_ROM_SIZE to depend on X86_RESET_VECTOR also to make this build for coreboot. Is that expected? Regards, Simon _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
