22 Oct, 2018

2 commits


20 Aug, 2018

2 commits

  • There is no need to keep a separate coreboot_fb.dtsi since now we
    have a generic coreboot payload dts.

    While we are here, this also remove the out-of-date description in
    the documentation regarding to coreboot framebuffer driver with
    U-Boot loaded as a payload from coreboot. As the testing result with
    QEMU 2.5.0 shows, the driver just works like a charm.

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

    Bin Meng
     
  • Currently building U-Boot as the coreboot payload requires user
    to change the build configuration for a specific board during
    menuconfig process. This uses the board's native device tree
    to configure the hardware. For example, the device tree provides
    PCI address range for the PCI host controller and U-Boot will
    re-program all PCI devices' BAR to be within this range. In order
    to make sure we don't mess up the hardware, we should guarantee
    the range matches what coreboot programs the chipset.

    But we really should make the coreboot payload support easier.
    Just like EFI payload, we can create a generic coreboot payload
    for all x86 boards as well. 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 coreboot's
    responsibility. Platform specific drivers (like gpio, spi, etc)
    are not included.

    Signed-off-by: Bin Meng
    Reviewed-by: Christian Gmeiner

    Bin Meng
     

02 Jul, 2018

1 commit


17 Jun, 2018

1 commit

  • Since commit f3b5056c4e72 ("efi_loader: split README.efi into two
    separate documents"), the original README.efi was renamed to
    README.u-boot_on_efi, but x86 doc still refers to the old one.

    This updates the x86 doc to reference both README.u-boot_on_efi and
    README.uefi.

    Signed-off-by: Bin Meng

    Bin Meng
     

13 Jun, 2018

1 commit

  • As README.x86 already mentions, there are two SPI flashes mounted
    on Intel Cougar Canyon 2 board, called SPI-0 and SPI-1 respectively.
    SPI-0 stores the flash descriptor and the ME firmware. SPI-1 stores
    the actual BIOS image which is U-Boot. Building a single image with
    both ME firmware and U-Boot does not make sense.

    This also describes the exact flash location where the u-boot.rom
    should be programmed in the documentation.

    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
     

16 Apr, 2018

1 commit


19 Oct, 2017

2 commits

  • Up to now we depended on an exported variable to build u-boot.rom.
    We should be able to specify it in the configuration file, too.

    With this patch this becomes possible using the new Kconfig option
    CONFIG_BUILD_ROM.

    This option depends on CONFIG_X86 and is selected in
    qemu-x86_defconfig and qemu-x86_64_defconfig.

    Cc: Simon Glass
    Cc: Bin Meng
    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Bin Meng

    Heinrich Schuchardt
     
  • Adjust VGA rom address to 0xfffb0000 so that u-boot.rom image
    can be built again.

    Signed-off-by: Bin Meng
    Reviewed-by: Stefan Roese

    Bin Meng
     

16 Sep, 2017

1 commit

  • This adds support to Intel Cherry Hill board, a board based on
    Intel Braswell SoC. The following devices are validated:

    - serial port as the serial console
    - on-board Realtek 8169 ethernet controller
    - SATA AHCI controller
    - EMMC/SDHC controller
    - USB 3.0 xHCI controller
    - PCIe x1 slot with a graphics card
    - ICH SPI controller with an 8MB Macronix SPI flash
    - Integrated graphics device as the video console

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

    Bin Meng
     

15 Aug, 2017

1 commit


30 Jul, 2017

1 commit

  • Add Intel Edison board which is using U-Boot.

    The patch is based on work done by the following people (in alphabetical
    order):
    Aiden Park
    Dukjoon Jeon
    eric.park
    Fabien Chereau
    Felipe Balbi
    Scott D Phillips
    Sebastien Colleur
    Steve Sakoman
    Vincent Tinelli

    In case we're building for Intel Edison, we must have 4096 bytes of
    zeroes in the beginning on u-boot.bin. This is done in
    board/intel/edison/config.mk.

    First run sets hardware_id environment variable which is read from
    System Controller Unit (SCU).

    Serial number (serial# environment variable) is generated based on eMMC
    CID.

    MAC address on USB network interface is unique to the board but kept the
    same all over the time.

    Set mac address from U-Boot using following scheme:
    OUI = 02:00:86
    next 3 bytes of MAC address set from eMMC serial number

    This allows to have a unique mac address across reboot and flashing.

    Signed-off-by: Vincent Tinelli
    Signed-off-by: Felipe Balbi
    Signed-off-by: Andy Shevchenko
    Reviewed-by: Bin Meng
    Reviewed-by: Simon Glass
    [bmeng: Add MAINTAINERS file for Intel Edison board]
    Signed-off-by: Bin Meng

    Andy Shevchenko
     

17 May, 2017

1 commit

  • Now that we have ACPI S3 support on Intel MinnowMax board, document
    some generic information of S3 and how to test it.

    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass
    Tested-by: Stefan Roese

    Bin Meng
     

15 Nov, 2016

1 commit

  • Enable this so that EFI applications (notably grub) can be run under U-Boot
    on x86 platforms.

    At present the 'hello world' EFI application is not supported for the
    qemu-x86_efi_payload64 board. That board builds a payload consisting of a
    64-bit header and a 32-bit U-Boot, which is incompatible with the way the
    EFI loader builds its EFI application. The following error is obtained:

    x86_64-linux-ld.bfd: i386 architecture of input file
    `lib/efi_loader/helloworld.o' is incompatible with i386:x86-64 output

    This could be corrected with additional Makefile rules. For now, this
    feature is disabled for that board.

    Signed-off-by: Simon Glass
    Reviewed-by: Bin Meng
    [agraf: drop hello kconfig bits]
    Signed-off-by: Alexander Graf

    Simon Glass
     

12 Oct, 2016

3 commits


16 Aug, 2016

3 commits


12 Jul, 2016

1 commit


30 May, 2016

1 commit


23 May, 2016

6 commits


17 Mar, 2016

4 commits


21 Feb, 2016

2 commits


28 Jan, 2016

1 commit


13 Jan, 2016

1 commit


21 Oct, 2015

2 commits

  • Now that we have added MRC cache for Intel FSP and BayTrail codes,
    enable it for all BayTrail boards (Bayley Bay and Minnow Max).

    Note it turns out that FSP for Intel Atom E6xx does not produce
    the HOB for NV storage, so we don't have such functionality on
    Intel Crown Bay board.

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

    Bin Meng
     
  • Introduce a new fsp command and make the existing hob command a
    sub-command to fsp for future extension. Also move cmd_hob.c to
    the dedicated fsp sub-directory in arch/x86/lib.

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

    Bin Meng