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
     

05 Dec, 2019

4 commits


04 Dec, 2019

2 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


05 Oct, 2019

1 commit


24 Aug, 2019

1 commit


29 Jul, 2019

1 commit


23 Jun, 2019

1 commit


21 Jun, 2019

1 commit


15 Jun, 2019

2 commits


11 Jun, 2019

2 commits

  • Migrate USB to Driver Model (CONFIG_DM_USB=y).

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

    Igor Opaniuk
     
  • 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
     

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

1 commit


29 Jan, 2019

1 commit


28 Jan, 2019

6 commits


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
     

14 Nov, 2018

2 commits


04 Sep, 2018

1 commit


18 Aug, 2018

1 commit


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

2 commits