[U-Boot] [RFC PATCH] efi: Another way to create u-boot payload for EFI

Bin Meng bmeng.cn at gmail.com
Tue Aug 4 10:21:18 CEST 2015


Hi Simon,

On Fri, Jul 31, 2015 at 11:45 PM, Simon Glass <sjg at chromium.org> wrote:
> Hi Bin,
>
> On 23 July 2015 at 09:45, Bin Meng <bmeng.cn at gmail.com> wrote:
>> This approach is different from Simon's approach. It uses objcopy
>> to convert u-boot-dtb.bin into an ELF object with all the binary
>> content included in the .data section. This elinimates the need
>> to include a special section in the payload's linker script. Also
>> there is no need to add any ASFLAGS_REMOVE for u-boot-dtb.o.
>>
>> Signed-off-by: Bin Meng <bmeng.cn at gmail.com>
>>
>> ---
>> This patch needs to be applied on top of Simon's efi series.
>>
>>  Makefile                            | 21 +++++----------------
>>  arch/x86/config.mk                  |  6 +++++-
>>  arch/x86/cpu/efi/elf_ia32_efi.lds   |  3 ---
>>  arch/x86/cpu/efi/elf_x86_64_efi.lds |  3 ---
>>  include/efi.h                       |  2 +-
>>  lib/efi/efi_stub.c                  |  5 +++--
>>  scripts/Makefile.build              |  8 --------
>>  7 files changed, 14 insertions(+), 34 deletions(-)
>
> This is the way that device tree used to work. It was painful to have
> to specify the architecture for all the boards. In fact we had code to
> work it out. My only concern with this approach is that we add the
> required for each arch to do this. However only x86 is currently
> support and I don't think it is much of a burden. Also it is good to
> get rid of the Makefile hack and this solution is overall tidier.
>
> Do you think we should apply it over the top of my existing patches?
> For now I have merged it into the two patches that need it.
>

I am good for current v2 series. Thanks for merging it in.

[snip]

Regards,
Bin


More information about the U-Boot mailing list