29 Feb, 2020

1 commit


07 Feb, 2020

2 commits


23 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
     

05 Dec, 2019

3 commits


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
     

13 Nov, 2019

1 commit


08 Nov, 2019

1 commit


08 Oct, 2019

1 commit


23 Sep, 2019

1 commit


26 Aug, 2019

1 commit

  • Convert CONFIG_SYS_NAND_USE_FLASH_BBT to Kconfig, update defconfigs,
    headers and whitelist.

    Please note that this symbol already was used in Kconfig
    (imply in CONFIG_NAND_ATMEL) which did not work, since this symbol was
    not available in Kconfig. This changes now with this patch and all
    boards with CONFIG_NAND_ATMEL will have BBT enabled. Which is what
    I also need on my GARDENA AT91SAM based board.

    Signed-off-by: Stefan Roese
    Cc: Eugen Hristev
    Cc: Miquel Raynal
    Cc: Gregory CLEMENT
    [trini: Rework such that the configs are unchanged to start with]
    Signed-off-by: Tom Rini

    Stefan Roese
     

02 Aug, 2019

1 commit

  • This converts the following to Kconfig:
    CONFIG_USE_PREBOOT
    CONFIG_PREBOOT

    Both are together in one commit, since otherwise the former causes kconfig
    to define the latter, which gives duplicate symbol errors.

    Includes a manual fixup for CONFIG_PREBOOT in ids8313_defconfig since the
    backslash lands in the wrong place. Similarly with socfpga_vining_fpga.

    Signed-off-by: Simon Glass

    Simon Glass
     

20 Jul, 2019

1 commit


09 Jul, 2019

1 commit


28 Jun, 2019

1 commit


27 Jun, 2019

3 commits


23 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
     

01 May, 2019

1 commit


30 Apr, 2019

2 commits


25 Apr, 2019

1 commit


14 Apr, 2019

1 commit


09 Jan, 2019

1 commit


03 Dec, 2018

1 commit


14 Nov, 2018

1 commit

  • Now that CMD_UBI does not select CMD_MTDPARTS we need to make platforms
    that had been enabling it turn it on by hand. This exposed that we had
    not yet migrated CMD_MTDPARTS fully, so do so now.

    Fixes: 86dfa556d927 ("cmd: ubi: Remove useless call to mtdparts_init()")
    Signed-off-by: Tom Rini

    Tom Rini
     

16 Oct, 2018

1 commit