30 Nov, 2018

7 commits


29 Nov, 2018

19 commits


28 Nov, 2018

1 commit


27 Nov, 2018

13 commits

  • - chiliboard updates
    - misc TI platform updates

    Tom Rini
     
  • DM_SERIAL is selected by TARGET_CHILIBOARD, so there is no reason to
    keep code that will not be built. Remove it.

    Signed-off-by: Marcin Niestroj
    Reviewed-by: Tom Rini

    Marcin Niestroj
     
  • This patch mostly enables DM drivers in board defconfig and all their
    dependencies. Additionally we remove ethernet platform data, as all
    details are in device-tree now.

    Signed-off-by: Marcin Niestroj
    Reviewed-by: Tom Rini

    Marcin Niestroj
     
  • Add that node path in u-boot overlay dtsi file for now to keep
    am335x-chiliboard.dts in sync with Linux.

    Signed-off-by: Marcin Niestroj
    Reviewed-by: Tom Rini

    Marcin Niestroj
     
  • Import chiliSOM and chiliboard dts files from Linux v4.19. They will
    be used after transition to driver model and device-tree based boot.

    Signed-off-by: Marcin Niestroj
    Reviewed-by: Tom Rini

    Marcin Niestroj
     
  • This option is defined by a few boards but doesn't guard any code.
    Remove it from the boards and config_whitelist.txt.

    Signed-off-by: Chris Packham
    Reviewed-by: Stefan Roese

    Chris Packham
     
  • This allow for convenient use of QEMU machine to test loading of UBI
    filesystem. There are a couple of changes made together of this which
    are required:

    1) The malloc must be at least 512 KiB to allow the use of UBI
    filesystem. We are going to enable it in a next patch.

    2) MTD_DEVICE must be enabled, otherwise we get missing symbols
    during the build

    Following configs were change:

    - vexpress_aemv8a_dram_defconfig
    - vexpress_aemv8a_juno_defconfig
    - vexpress_aemv8a_semi_defconfig
    - vexpress_ca15_tc2_defconfig
    - vexpress_ca5x2_defconfig
    - vexpress_ca9x4_defconfig

    Signed-off-by: Otavio Salvador
    Acked-by: Liviu Dudau

    Otavio Salvador
     
  • When the spi_flash_probe_bus_cs() was previously called, it was
    called using 0's for two values where CONFIG_ENV_SPI_MAX_HZ and
    CONFIG_ENV_SPI_MODE are now used. When changed this
    caused the environment to fail the CRC check and the default
    was used. This patch defines both of these values back 0.

    Fixes: 25a17652c9c2 ("fix: env: Fix the SPI flash device setup
    for DM mode")

    Signed-off-by: Adam Ford

    Adam Ford
     
  • Some erratum workarounds call into C code before the stack
    is setup, this can lead to values pushed onto the stack
    being lost, firewall exceptions, and other undefined behavior.

    Setup a temporary stack to allow these functions to work
    correctly.

    Signed-off-by: Andrew F. Davis
    Acked-by: Andreas Dannenberg
    Reviewed-by: Nishanth Menon

    Andrew F. Davis
     
  • stdlib.h is the header for malloc since at least c89/c90.
    Previously this would fail to build on OpenBSD and fallback to the wrong
    header:

    In file included from u-boot/tools/file2include.c:21:
    u-boot/include/malloc.h:875:5: error: function-like macro
    'CONFIG_IS_ENABLED' is not defined

    Signed-off-by: Jonathan Gray
    Reviewed-by: Heinrich Schuchardt

    Jonathan Gray
     
  • Recent removal of obsolete partition led to shifting of starting address
    of "reserved" partition (which reflects U-Boot environment). Fix its
    start address to keep it in sync with ENV_OFFSET and DFU environment.

    This patch also provides fixed start address for "reserved" partition,
    so that we can track when it's shifted next time.

    While at it, move it before "misc" partition to keep all Android
    partitions together.

    Signed-off-by: Sam Protsenko
    Acked-By: Praneeth Bajjuri

    Sam Protsenko
     
  • Based on the MCU R5 efuse settings, R5F cores in MCU domain
    either work in split mode or in lock step mode.

    If efuse settings are in lockstep mode: ROM release R5 cores
    and SPL continues to run on the R5 core is lockstep mode.

    If efuse settings are in split mode: ROM releases both the R5
    cores simultaneously and allow SPL to run on both the cores.
    In this case it is bootloader's responsibility to detect core
    1 and park it. Else both the core will be running bootloader
    independently which might result in an unexpected behaviour.

    Signed-off-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Lokesh Vutla
     
  • with this patch the selected Entry in bootmenu can be set by
    environment-var bootmenu_default=
    Signed-off-by: Frank Wunderlich

    Frank Wunderlich