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

1 commit

  • Extend size of the malloc() pool for use before relocation, from 0x400
    (default one) to 0x2000 (CONFIG_SYS_MALLOC_F_LEN=0x2000),
    as adding of DM_FLAG_PRE_RELOC flag to simple-bus driver introduced a
    regression on multiple boards, because of more intensive usage of malloc()
    pool and therefore a broken boot as the size of pool isn't sufficient.

    Fixes: 3a7c45f6a7 ("simple-bus: add DM_FLAG_PRE_RELOC flag to simple-bus")
    Signed-off-by: Igor Opaniuk
    Reviewed-by: Bin Meng

    Igor Opaniuk
     

05 Jun, 2019

1 commit


27 May, 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
     

01 May, 2019

1 commit


30 Apr, 2019

2 commits


26 Apr, 2019

1 commit

  • 1. Replace usage of "/dev/mmcblk*p*" with a proper UUID of rootfs
    partition. This fixes the issue, when MMC controllers are probed in
    a different order in U-boot and Linux kernel.
    2. Fix legacy USB command (both sdboot and usbboot can be used now).

    Tested-by: Marcel Ziswiler
    Signed-off-by: Igor Opaniuk

    Igor Opaniuk
     

14 Apr, 2019

12 commits


26 Jan, 2019

1 commit


19 Jan, 2019

1 commit

  • The bounce buffer is used by a few drivers (most of the MMC drivers)
    to overcome limitations in their respective DMA implementation.

    This moves the configuration to Kconfig and makes it user-selectable
    (even though it will be a required feature to make those drivers
    work): the expected usage is for drivers depending on this to 'select'
    it unconditionally from their respective Kconfig (see follow-up
    patches).

    This commit includes a full migration using moveconfig.py to ensure
    that each commit compiles. To ensure bisectability we update
    dependencies of various drivers to now select BOUNCE_BUFFER when needed.

    [trini: Squash all patches to ensure bisectability]
    Signed-off-by: Tom Rini
    Signed-off-by: Philipp Tomsich
    Reviewed-by: Otavio Salvador [dw_mmc portion]
    Reviewed-by: Fabio Estevam [mxsmmc portion]
    Reviewed-by: Simon Glass [tegra portion]

    Philipp Tomsich
     

11 Jan, 2019

1 commit


18 Aug, 2018

2 commits


17 Aug, 2018

1 commit

  • We have the following cases:
    - CONFIG_NR_DRAM_BANKS was defined, migrate normally
    - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
    CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
    - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
    2), set this to 8.

    Signed-off-by: Tom Rini

    Tom Rini
     

09 Apr, 2018

5 commits


08 Apr, 2018

1 commit


24 Feb, 2018

1 commit

  • This converts the following to Kconfig:
    CONFIG_BOOTP_BOOTPATH
    CONFIG_BOOTP_DNS
    CONFIG_BOOTP_GATEWAY
    CONFIG_BOOTP_HOSTNAME
    CONFIG_BOOTP_PXE
    CONFIG_BOOTP_SUBNETMASK
    CONFIG_CMDLINE_EDITING
    CONFIG_AUTO_COMPLETE
    CONFIG_SYS_LONGHELP
    CONFIG_SUPPORT_RAW_INITRD
    CONFIG_ENV_VARS_UBOOT_CONFIG

    Signed-off-by: Adam Ford
    [trini: Re-run the migration]
    Signed-off-by: Tom Rini

    Adam Ford
     

11 Feb, 2018

1 commit

  • On the NIOS2 and Xtensa architectures, we do not have
    CONFIG_SYS_TEXT_BASE set. This is a strict migration of the current
    values into the defconfig and removing them from the headers.

    I did not attempt to add more default values in and for now will leave
    that to maintainers.

    Signed-off-by: Tom Rini

    Tom Rini