[U-Boot] [RESEND PATCH v4 0/12] x86: Better support of coreboot

Bin Meng bmeng.cn at gmail.com
Tue Jan 6 15:35:22 CET 2015


Hi Simon,

On Tue, Jan 6, 2015 at 10:21 PM, Simon Glass <sjg at chromium.org> wrote:
> Hi Bin,
>
> On 6 January 2015 at 07:14, Bin Meng <bmeng.cn at gmail.com> 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?
>

Yes, really sorry about that. I've resent a v4 patch just now. See
http://patchwork.ozlabs.org/patch/425685/

Regards,
Bin


More information about the U-Boot mailing list