24 Aug, 2019

2 commits


23 Aug, 2019

1 commit


12 Jul, 2019

1 commit


26 Jun, 2019

1 commit


17 Jun, 2019

1 commit


15 Jun, 2019

1 commit


13 Jun, 2019

1 commit

  • Add a new option, CONFIG_DEPRECATED, for code that relies on deprecated
    functionality and has not been converted past the deadline for
    conversion.

    Signed-off-by: Tom Rini
    Reviewed-by: Jagan Teki

    Tom Rini
     

11 Jun, 2019

1 commit

  • Commit 3a7c45f6a772 ("simple-bus: add DM_FLAG_PRE_RELOC flag to
    simple-bus driver") causes some i.MX boards that were converted
    to DM, such as warp7, to fail to boot.

    As explained by Lukas Auer:

    "With the patch, U-Boot probes the drivers for devices under simple-bus
    device tree nodes in the pre-relocation device model. The default value
    of CONFIG_SYS_MALLOC_F_LEN (0x400) leaves U-Boot with not enough memory to
    do this, causing it to hang."

    Fix this problem by providing a convenient default value for
    CONFIG_SYS_MALLOC_F_LEN.

    Reported-by: Pierre-Jean Texier
    Suggested-by: Lukas Auer
    Signed-off-by: Fabio Estevam
    Tested-by: Pierre-Jean Texier
    Tested-by: Bryan O'Donoghue
    Reviewed-by: Lukas Auer
    Reviewed-by: Peng Fan
    Tested-by: Heiko Schocher

    Fabio Estevam
     

29 May, 2019

1 commit


27 May, 2019

1 commit


23 May, 2019

1 commit


22 May, 2019

1 commit

  • Build an SPL which can be started via SCIF download mode on R-Car Gen3
    and allows loading and executing U-Boot uImage with the next stage code.
    This is also useful for starting e.g. ATF BL2, which inits the hardware
    and returns to the U-Boot SPL, which can then load e.g. U-Boot proper.

    The H3, M3-W, M3-N SoCs have plenty of SRAM for storing the U-Boot SPL
    while the payload, e.g. ATF BL2, executes, so there is no problem here.

    However, E3 and D3 have much less SRAM, hence the loader uses a trick
    where it copies itself beyond the area used by BL2 and executes from
    there. That area is 32kiB large and not enough to hold U-Boot SPL, BSS,
    stack and malloc area, so the later two are placed at +0x4000 offset
    from start of SRAM, another area not used by ATF BL2. To make things
    even more complicated, the SCIF loader cannot load to the upper 32kiB
    of the SRAM directly, hence the copying approach.

    Signed-off-by: Marek Vasut
    Cc: Nobuhiro Iwamatsu

    Marek Vasut
     

21 May, 2019

1 commit

  • MPC83xx uses CONFIG_83XX_CLKIN instead of CONFIG_SYS_CLK_FREQ to set the
    system clock. To migrate the architecture, we can replace
    CONFIG_83XX_CLKIN with CONFIG_SYS_CLK_FREQ.

    To do this
    * replace all occurrences of CONFIG_83XX_CLKIN with CONFIG_SYS_CLK_FREQ
    * set CONFIG_SYS_CLK_FREQ to the old value of CONFIG_83XX_CLKIN in all
    MPC83xx config files

    Signed-off-by: Mario Six

    Mario Six
     

19 May, 2019

1 commit


08 May, 2019

1 commit

  • Add default SPL_FIT_GENERATOR py script for rockchip platforms if
    specific target enabled SPL_LOAD_FIT.

    So, this would help get rid of explicitly mentioning the default
    SPL FIT generator in defconfigs. however some targets, like puma_rk3399
    still require their own FIT generator so in those cases the default will
    override with defconfig defined generator.

    Reviewed-by: Paul Kocialkowski
    Signed-off-by: Jagan Teki
    Reviewed-by: Kever Yang

    Jagan Teki
     

09 Apr, 2019

1 commit

  • This patch adds the CONFIG_SPL_IMAGE option to select the SPL image that
    shall be used to generate the combined SPL + U-Boot image. The default
    value is the current value "spl/u-boot-spl.bin".

    This patch also sets CONFIG_SPL_IMAGE to "spl/boot.bin" for AT91 targets
    which use SPL NAND support (boot from NAND). For these build targets the
    combined image "u-boot-with-spl.bin" is now automatically generated and
    can be programmed into NAND as one single image (vs. SPL image and U-Boot
    as 2 separate images).

    Signed-off-by: Stefan Roese
    Cc: Heiko Schocher
    Cc: Andreas Bießmann
    Cc: Eugen Hristev

    Stefan Roese
     

21 Mar, 2019

1 commit


11 Feb, 2019

1 commit

  • Commit dc146ca11187 ("Kconfig: Migrate CONFIG_BUILD_TARGET") made the
    mvebu default build target depend on CONFIG_SPL_BUILD. Unfortunately,
    there is no such Kconfig symbol. Use the CONFIG_SPL symbol instead to
    fix that.

    Cc: Jagan Teki
    Signed-off-by: Baruch Siach
    Reviewed-by: Stefan Roese
    Reviewed-by: Jagan Teki
    Signed-off-by: Stefan Roese

    Baruch Siach
     

02 Feb, 2019

2 commits


18 Jan, 2019

1 commit


01 Jan, 2019

2 commits


14 Dec, 2018

1 commit


04 Dec, 2018

1 commit

  • Patch queue for efi - 2018-12-03

    This release is fully packed with lots of glorious improvements in UEFI
    land again!

    - Make PE images more standards compliant
    - Improve sandbox support
    - Improve correctness
    - Fix RISC-V execution on virt model
    - Honor board defined top of ram (fixes a few boards)
    - Imply DM USB access when distro boot is available
    - Code cleanups

    Tom Rini
     

03 Dec, 2018

2 commits


16 Oct, 2018

1 commit

  • Xilinx is introducing Versal, an adaptive compute acceleration platform
    (ACAP), built on 7nm FinFET process technology. Versal ACAPs combine
    Scalar Processing Engines, Adaptable Hardware Engines, and Intelligent
    Engines with leading-edge memory and interfacing technologies to deliver
    powerful heterogeneous acceleration for any application. The Versal AI
    Core series has five devices, offering 128 to 400 AI Engines. The series
    includes dual-core Arm Cortex™-A72 application processors, dual-core Arm
    Cortex-R5 real-time processors, 256KB of on-chip memory with ECC, more
    than 1,900 DSP engines optimized for high-precision floating point with
    low latency.

    The patch is adding necessary infrastructure in place without enabling
    platform which is done in separate patch.

    Signed-off-by: Michal Simek

    Michal Simek
     

11 Sep, 2018

1 commit


17 Aug, 2018

1 commit


06 Aug, 2018

1 commit


04 Aug, 2018

1 commit


30 Jul, 2018

1 commit


11 Jul, 2018

1 commit

  • This adds a new config value FIT_SIGNATURE_MAX_SIZE, which controls the
    max size of a FIT header's totalsize field. The field is checked before
    signature checks are applied to protect from reading past the intended
    FIT regions.

    This field is not part of the vboot signature so it should be sanity
    checked. If the field is corrupted then the structure or string region
    reads may have unintended behavior, such as reading from device memory.
    A default value of 256MB is set and intended to support most max storage
    sizes.

    Suggested-by: Simon Glass
    Signed-off-by: Teddy Reed
    Reviewed-by: Simon Glass

    Teddy Reed
     

24 May, 2018

2 commits

  • Add support for loading U-Boot and optionally FDT from a fitImage
    in SPL by using the full fitImage support from U-Boot. While we do
    have limited SPL loading support in SPL with a small footprint, it
    is missing a lot of important features, like checking signatures.
    This support has all the fitImage features, while the footprint is
    obviously larger.

    Signed-off-by: Marek Vasut
    Cc: Pantelis Antoniou
    Cc: Simon Glass
    Reviewed-by: Simon Glass

    Marek Vasut
     
  • Rename CONFIG_FIT_SPL_PRINT to CONFIG_SPL_FIT_PRINT and add Kconfig
    entry for it.

    Signed-off-by: Marek Vasut
    Cc: Pantelis Antoniou
    Cc: Simon Glass
    Reviewed-by: Simon Glass

    Marek Vasut
     

07 May, 2018

1 commit

  • Building with verified boot support requires hash, add that
    dependency here. Otherwise the following build error will come out
    without crc command.

    LD u-boot
    lib/built-in.o: In function `hash_calculate':
    lib/rsa/rsa-checksum.c:29: undefined reference to
    `hash_progressive_lookup_algo'
    ...
    make[1]: *** [u-boot] Error 1

    Signed-off-by: Kelvin Cheung
    Reviewed-by: Joe Hershberger

    Kelvin Cheung
     

28 Apr, 2018

2 commits