u-boot.git/include/configs, branch v2020.04-rc3

rockchip: rk3399: split roc-pc-rk3399 out of evb_rk3399

2020-02-19T08:45:38Z

roc-pc-rk3399 board has one user button & three user LED's. Currently we don't have any code support for these devices. Since button and LED's are specific to roc-pc-rk3399 board, split it into its own board file and add code support here. Signed-off-by: Suniel Mahesh Reviewed-by: Kever Yang

rk3288: vyasa: Add console settings

2020-02-19T08:45:38Z

Add console settings like stdin, stdout and stderr as cros-ec-keyb and vidconsole respectively for Vyasa Rk3288 board. This would certainly help to detect the attached video devices (like HDMI) and print the console message on display. Signed-off-by: Jagan Teki Reviewed-by: Kever Yang

rk3288: tinker: Enable HDMI output

2020-02-19T08:45:38Z

Enable HDMI output for Tinker RK3288 board. Signed-off-by: Jagan Teki Reviewed-by: Kever Yang

Merge tag 'u-boot-stm32-20200214' of https://gitlab.denx.de/u-boot/custodians/u-boot-stm

2020-02-14T12:31:47Z

- add DH Electronics DHCOM SoM and PDK2 board - DT alignment with kernel v5.5-rc7 for stm32mp1 boards - fix STM32 image format for big endian hosts in mkimage - solve warnings in device tree and code for stm32mp1 boards - remove fdt_high and initrd_high for stm32 and stih boards - add support of STM32MP15x Rev.Z - update stm32mp1 readme

board: stm32: remove fdt_high and fdt_highinitrd_high

2020-02-13T17:47:00Z

For stm32 f4, f7 and h7 boards, remove fdt_high and initrd_high as they shouldn't be used, this allows the fdt and initrd relocation. This implies to set CONFIG_SYS_BOOTMAPSZ to indicate the amount of memory available to contain kernel, device tree and initrd for relocation. Signed-off-by: Patrice Chotard Reviewed-by: Patrick DELAUNAY

board: stm32: fix extra env setings addresses

2020-02-13T17:47:00Z

For stm32f4, f7 and h7 boards, reserve: - 4MB for kernel - 64KB for fdt, boot script, pxefile - the remaining memory for ramdisk Signed-off-by: Patrice Chotard Reviewed-by: Patrick DELAUNAY

board: stih410-b2260: remove fdt_high and initrd_high

2020-02-13T17:47:00Z

Remove fdt_high and initrd_high as they shouldn't be used, this allows the fdt and initrd relocation. This implies to set CONFIG_SYS_BOOTMAPSZ to indicate the amount of memory available to contain kernel, device tree and initrd for relocation. Signed-off-by: Patrice Chotard Reviewed-by: Tom Rini Reviewed-by: Patrick DELAUNAY

stm32mp1: remove fdt_high and initrd_high in environment

2020-02-13T17:47:00Z

Remove fdt_high and initrd_high (set to 0xffffffff) in stm32mp1 board enviromnent, and U-Boot always relocate FDT and initrd in bootm command. This relocation is limited by CONFIG_SYS_BOOTMAPSZ which indicates the size of the memory region where it is safe to place data passed to the Linux kernel (DTB, initrd), it is a) Less than or equal to RAM size. b) not within the kernel's highmem region So 256M seems large enough in most circumstances and users can override this value via environment variable "bootm_mapsize" if needed. This modification increases the boot time but avoid assumption on aligned address for bootm command. A user can still define this variables themselves if the FDT or initrd is either left in-place or copied to a specific location. Signed-off-by: Patrick Delaunay Reviewed-by: Tom Rini

ARM: keystone2: enable initrd fixup for LPAE addressing

2020-02-13T16:09:18Z

Keystone2 u-boot loads the initrd image into non-LPAE addressed memory but linux kernel is running in LPAE. This causes a conflict as kernel detects that non-memory address is passed and kernel ignores initrd. There is an existing fixup logic to modify the address in the proper configuration, but this is disabled at the moment. Enable the fixup by setting the env variable for this so that initrd can be used properly. Signed-off-by: Tero Kristo Signed-off-by: Lokesh Vutla

board: ge: bx50v3, imx53ppd: configure CONFIG_SYS_BOOTMAPSZ

2020-02-09T20:47:20Z

Configure `CONFIG_SYS_BOOTMAPSZ' per guidance on u-boot@lists.denx.de. Signed-off-by: Ian Ray