04 Dec, 2019
1 commit
-
Add more clarity by changing the Kconfig entry name.
Signed-off-by: Miquel Raynal
[trini: Re-run migration, update a few more cases]
Signed-off-by: Tom Rini
Reviewed-by: Boris Brezillon
21 Nov, 2019
1 commit
-
- 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
19 May, 2019
1 commit
-
This board define the flag CONFIG_SYS_NAND_DRIVER_ECC_LAYOUT
but it's a mistake. It's a workaround for an issue in nand core.
This issue was fixed by the commit 5f626e78491c ("mtd: nand: raw:
Fix CONFIG_SYS_NAND_DRIVER_ECC_LAYOUT behavior"). Now, this flag
break the nand on this board, so we simply remove it.Signed-off-by: Philippe Reynes
23 Apr, 2019
1 commit
-
Enable the nand support (driver and command)
in the configuration of the board bcm968580xref.Signed-off-by: Philippe Reynes
17 Nov, 2018
1 commit
-
This add the initial support of the broadcom reference
board bcm968580xref with a bcm6858 SoC.This board has 512 MB of ram, 256 MB of flash (nand),
2 usb port, 1 uart, 4 ethernet ports (LAN), 1 ethernet port (WAN).Signed-off-by: Philippe Reynes