07 Feb, 2020

1 commit

  • This partially reverts changes by commit 2cc393f32fd9
    ("video: make BPP and ANSI configs optional") since it
    caused issues with other boards (missing LCD console
    output on pinebook, x86 platform or sandbox). Enable
    all disabled options again and opt out of not supported
    color depth in board defconfigs.

    Signed-off-by: Anatolij Gustschin
    Reported-by: Vagrant Cascadian

    Anatolij Gustschin
     

23 Jan, 2020

1 commit


07 Jan, 2020

1 commit


06 Dec, 2019

1 commit

  • Many boards do not use all selected framebuffer depth
    configurations, for such boards there is some unused
    code in video and console uclass routines. Make depth
    specific code optional to avoid dead code and slightly
    reduce binary size. Also make ANSI code optional for
    the same reason. When i.e. using only VIDEO_BPP16 the
    code size shrinks (below values when using gcc-7.3.0):

    $ ./tools/buildman/buildman -b video-wip -sS wandboard
    ...
    01: Merge git://git.denx.de/u-boot-sh
    02: video: add guards around 16bpp/32bbp code
    03: video: make BPP and ANSI configs optional
    arm: (for 1/1 boards) all -776.0 bss -8.0 text -768.0

    Signed-off-by: Anatolij Gustschin
    Tested-by: Eugen Hristev
    Tested-by: Patrice Chotard
    Tested-by: Steffen Dirkwinkel

    Anatolij Gustschin
     

04 Dec, 2019

1 commit


21 Nov, 2019

2 commits

  • - In ARMv8 NXP Layerscape platforms we also need to make use of
    CONFIG_SYS_RELOC_GD_ENV_ADDR now, do so.
    - On ENV_IS_IN_REMOTE, CONFIG_ENV_OFFSET is never used, drop the define
    to 0.
    - Add Kconfig entry for ENV_ADDR.
    - Make ENV_ADDR / ENV_OFFSET depend on the env locations that use it.
    - Add ENV_xxx_REDUND options that depend on their primary option and
    SYS_REDUNDAND_ENVIRONMENT
    - On a number of PowerPC platforms, use SPL_ENV_ADDR not CONFIG_ENV_ADDR
    for the pre-main-U-Boot environment location.
    - On ENV_IS_IN_SPI_FLASH, check not for CONFIG_ENV_ADDR being set but
    rather it being non-zero, as it will now be zero by default.
    - Rework the env_offset absolute in env/embedded.o to not use
    CONFIG_ENV_OFFSET as it was the only use of ENV_OFFSET within
    ENV_IS_IN_FLASH.
    - Migrate all platforms.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Cc: Patrick Delaunay
    Cc: uboot-stm32@st-md-mailman.stormreply.com
    Signed-off-by: Tom Rini
    Acked-by: Joe Hershberger
    Reviewed-by: Simon Goldschmidt

    Tom Rini
     
  • Today in initr_reloc_global_data() we use some non-obvious tests to
    determine if we need to relocate the env_addr within gd or not. In
    order to facilitate migration of other symbols to Kconfig we need to
    introduce a new symbol for this particular use case.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Signed-off-by: Tom Rini

    Tom Rini
     

08 Nov, 2019

1 commit


08 Oct, 2019

1 commit


05 Oct, 2019

1 commit


24 Aug, 2019

1 commit


14 Aug, 2019

1 commit


20 Jul, 2019

3 commits

  • 1. Introduce androidboot wrapper for booting AOSP.
    2. Add partitions_android env var for simplifying the process of
    writing new gpt table from U-boot shell/fastboot.

    Signed-off-by: Igor Opaniuk
    Reviewed-by: Oleksandr Suvorov

    Igor Opaniuk
     
  • We never really added a sensible DFU configuration for platforms
    based on eMMC. Most of the things one might want to do can also be done
    with UMS or fastboot, so drop the DFU configuration.

    Signed-off-by: Igor Opaniuk
    Reviewed-by: Philippe Schenker

    Igor Opaniuk
     
  • Enable CONFIG_ARMV7_BOOT_SEC_DEFAULT by default to avoid a kernel
    crash when booting NXP linux kernels in non-secure world,
    when job ring device allocation is done by CAAM hw accelerator driver:

    caam 30900000.caam: job rings = 3, qi = 0
    caam_jr 30901000.jr0: failed to flush job ring 0
    caam_jr: probe of 30901000.jr0 failed with error -5
    caam_jr 30902000.jr1: failed to flush job ring 1
    caam_jr: probe of 30902000.jr1 failed with error -5
    caam_jr 30903000.jr2: failed to flush job ring 2
    caam_jr: probe of 30903000.jr2 failed with error -5
    caam algorithms registered in /proc/crypto
    Job Ring Device allocation for transform failed
    caam 30900000.caam: caam pkc algorithms registered in /proc/crypto
    Unable to handle kernel NULL pointer dereference at virtual address 00000010
    pgd = c0004000
    [00000010] *pgd=00000000
    Internal error: Oops: 5 [#1] PREEMPT SMP ARM
    Modules linked in:
    CPU: 0 PID: 1 Comm: swapper/0 Tainted:
    Hardware name: Freescale i.MX7 Dual (Device Tree)
    task: ec0d8000 task.stack: ec0ce000
    PC is at caam_sm_startup+0x3f8/0x4f4

    Signed-off-by: Igor Opaniuk

    Igor Opaniuk
     

23 Jun, 2019

1 commit


21 Jun, 2019

1 commit


15 Jun, 2019

2 commits


12 Jun, 2019

1 commit

  • u-boot-imx-20190612
    --------------------

    - Board fixes:
    - imx6logic
    - wandboard
    - mx6sabre boots again
    - imx8qm_mek
    - pico-* boards
    - Toradex apalis / colibri
    - engicam imx6 (environment)
    - KP MX53
    - opos6ul
    - Switch to DM:
    - vining2000
    - dh MX6
    - Toradex colibri i.MX7
    - Novena
    - Security : fix CSF size for HAB
    - Other:
    - imx: fix building for i.mx8 without spl
    - pcie and switch to DM

    mx6sabreauto: Enable SPL SDP support

    Tom Rini
     

11 Jun, 2019

3 commits


05 Jun, 2019

1 commit


15 May, 2019

1 commit

  • Commit d397f7c45b0b ("net: phy: micrel: Separate KSZ9000 drivers from
    KSZ8000 drivers") separated the KSZ8xxx and KSZ90x1 drivers and warns
    that you shouldn't select both of them due to a device ID clash between
    the KSZ9021 and the KS8721, asserting that "it is highly unlikely for a
    system to contain both a KSZ8000 and a KSZ9000 PHY". Unfortunately
    boards like the SAMA5D3xEK do contain both types of PHY, but fortunately
    the Linux Micrel PHY driver provides a solution by using different PHY
    ID and mask values to distinguish these chips.

    This commit contains the following changes:

    - The PHY ID and mask values for the KSZ9021 and the KS8721 now match
    those used by the Linux driver.
    - The warnings about not enabling both drivers have been removed.
    - The description for PHY_MICREL_KSZ8XXX has been corrected (these are
    10/100 PHYs, not GbE PHYs).
    - PHY_MICREL_KSZ9021 and PHY_MICREL_KSZ9031 no longer select PHY_GIGE
    since this is selected by PHY_MICREL_KSZ90X1.
    - All of the relevant defconfig files have been updated now that
    PHY_MICREL_KSZ8XXX does not default to 'Y'.

    Signed-off-by: James Byrne
    Acked-by: Joe Hershberger

    James Byrne
     

05 May, 2019

1 commit

  • This converts the following to Kconfig:
    CONFIG_SUPPORT_EMMC_BOOT

    As requested by Michal Simek , these boards
    have no eMMC so CONFIG_SUPPORT_EMMC_BOOT has not been migrated:

    xilinx_zynqmp_zc1275_revB
    xilinx_zynqmp_zc1751_xm018_dc4
    xilinx_zynqmp_zc1751_xm019_dc5
    xilinx_zynqmp_zcu100_revC
    xilinx_zynqmp_zcu102_rev1_0
    xilinx_zynqmp_zcu102_revA
    xilinx_zynqmp_zcu102_revB
    xilinx_zynqmp_zcu104_revA
    xilinx_zynqmp_zcu104_revC
    xilinx_zynqmp_zcu106_revA
    xilinx_zynqmp_zcu111_revA

    Signed-off-by: Alex Kiernan
    Acked-by: Lukasz Majewski
    Acked-by: Patrick Delaunay
    Acked-by: Ramon Fried
    Reviewed-by: Andy Shevchenko
    Tested-by: Sébastien Szymanski

    Alex Kiernan
     

29 Jan, 2019

1 commit