23 Jan, 2020

1 commit


07 Jan, 2020

1 commit


05 Dec, 2019

2 commits


04 Dec, 2019

3 commits


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


23 Sep, 2019

1 commit


24 Aug, 2019

1 commit


23 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
     

30 Apr, 2019

2 commits


08 Feb, 2019

1 commit


28 Jan, 2019

1 commit

  • Port for the PHYTEC phyBOARD-i.MX6UL-Segin single board computer. Based on
    the PHYTEC phyCORE-i.MX6UL SOM (PCL063).

    CPU: Freescale i.MX6UL rev1.2 528 MHz (running at 396 MHz)
    CPU: Industrial temperature grade (-40C to 105C) at 44C
    Reset cause: POR
    Board: PHYTEC phyCORE-i.MX6UL
    I2C: ready
    DRAM: 256 MiB
    NAND: 512 MiB
    MMC: FSL_SDHC: 0
    In: serial
    Out: serial
    Err: serial
    Net: FEC0

    Working:
    - Eth0
    - i2C
    - MMC/SD
    - NAND
    - UART (1 & 5)
    - USB (host & otg)

    Signed-off-by: Martyn Welch

    Martyn Welch