17 Jun, 2018

3 commits

  • To avoid confusion, let's rename the efi-x86 target to efi-x86_app.

    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass

    Bin Meng
     
  • It is possible to create a generic EFI payload for all x86 boards.
    The payload is configured to include as many generic drivers as
    possible. All stuff that touches low-level initialization are not
    allowed as such is the EFI BIOS's responsibility. Platform specific
    drivers (like gpio, spi, etc) are not included.

    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass

    Bin Meng
     
  • At present the EFI application and payload support codes in the x86
    directory is distributed in a hybrid way. For example, the Kconfig
    options for both app and payload are in arch/x86/lib/efi/Kconfig,
    but the source codes in the same directory get built only for
    CONFIG_EFI_STUB.

    This refactors the codes by consolidating all the EFI support codes
    into arch/x86/cpu/efi, just like other x86 targets.

    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass

    Bin Meng
     

07 May, 2018

1 commit

  • When U-Boot started using SPDX tags we were among the early adopters and
    there weren't a lot of other examples to borrow from. So we picked the
    area of the file that usually had a full license text and replaced it
    with an appropriate SPDX-License-Identifier: entry. Since then, the
    Linux Kernel has adopted SPDX tags and they place it as the very first
    line in a file (except where shebangs are used, then it's second line)
    and with slightly different comment styles than us.

    In part due to community overlap, in part due to better tag visibility
    and in part for other minor reasons, switch over to that style.

    This commit changes all instances where we have a single declared
    license in the tag as both the before and after are identical in tag
    contents. There's also a few places where I found we did not have a tag
    and have introduced one.

    Signed-off-by: Tom Rini

    Tom Rini
     

10 Feb, 2018

1 commit

  • README.efi describes two different concepts:
    * U-Boot exposing the UEFI API
    * U-Boot running on top of UEFI.

    This patch splits the document in two.
    Religious references are removed.

    The separation of the concepts makes sense before detailing the internals
    of U-Boot exposing the UEFI API in a future patch.

    Signed-off-by: Heinrich Schuchardt
    Signed-off-by: Alexander Graf

    Heinrich Schuchardt