summaryrefslogtreecommitdiff
path: root/scripts/const_structs.checkpatch
diff options
context:
space:
mode:
authorQuentin Schulz <[email protected]>2025-05-05 16:47:19 +0200
committerKever Yang <[email protected]>2025-05-06 15:57:38 +0800
commitf9b4d051a7357e7da7b2262f8719c555573b0b31 (patch)
tree2364ce70fc628ac4fa980c40a0b4c261990c05f4 /scripts/const_structs.checkpatch
parent1f140fefa63b399785528e9a6503f7e0a75f3315 (diff)
rockchip: rk3288: do not generate u-boot.rom anymore
This was only used on RK3288 Chromebooks and the EVB. If it follows the same pattern as for RK3399 Chromebooks where their maintainer (Simon) agreed[1] to removal of u-boot.rom on the basis that the generic u-boot-rockchip-spi.bin is now enough, let's do the same for RK3288 and remove the last Rockchip users of u-boot.rom (and HAS_ROM symbol). At the same time, remove HAS_ROM symbol from the RK3288 Chromebooks and EVB configs since they were used only for that. SYS_SPI_U_BOOT_OFFS offset in rockchip-u-boot.dtsi for the u-boot-img node of simple-bin-spi binman image matches the one used in u-boot.rom except for the EVB. The EVB doesn't have ROCKCHIP_SPI_IMAGE symbol enabled, so HAS_ROM had no effect anyway. Even if it had, this would not have been enough considering that SPL_SPI_LOAD symbol is not set, so U-Boot proper could not be loaded from SPI even if SPL/TPL does. Make sure u-boot-rockchip-spi.bin has the same size of u-boot.rom for Chromebooks as that seems to be important. [1] https://lore.kernel.org/u-boot/CAFLszTh-SewFod8dEOF3+e-wCE1qFF0CyxxR8CbQwy3BRW3k6w@mail.gmail.com/ Reviewed-by: Jonas Karlman <[email protected]> Reviewed-by: Kever Yang <[email protected]> Tested-by: Simon Glass <[email protected]> # chromebook-kevin Signed-off-by: Quentin Schulz <[email protected]>
Diffstat (limited to 'scripts/const_structs.checkpatch')
0 files changed, 0 insertions, 0 deletions