diff options
author | Ian Abbott <abbotti@mev.co.uk> | 2021-11-05 12:21:45 +0000 |
---|---|---|
committer | Sascha Hauer <s.hauer@pengutronix.de> | 2021-11-08 09:11:06 +0100 |
commit | ba723fc40e63274bf90144cd31b599f4159ca049 (patch) | |
tree | e0d1aae5aa11d38830ac8d0dbcb8e88914e101b6 /arch/riscv | |
parent | 9eac57aa0aa2079904c2e6bf2b1f392d977714da (diff) | |
download | barebox-ba723fc40e63274bf90144cd31b599f4159ca049.tar.gz barebox-ba723fc40e63274bf90144cd31b599f4159ca049.tar.xz |
ARM: Terasic DE0-Nano-SoC/Atlas-SoC: Use upstream compatible string
The upstream (Linux) 'compatible' string for the Terasic
DE0-Nano-SoC/Atlas-SoC board in
"dts/src/arm/socfpga_cyclone5_de0_nano_soc.dts" differs from the barebox
'compatible' string for the same board in
"arch/arm/dts/socfpga_cyclone5_de0_nano_soc.dts":
Linux: "terasic,de0-atlas"
barebox: "terasic,de0-nano-soc"
That results in an incompatibility when trying to boot a bootloader spec
entry with a 'devicetree' key that refers to the DTB file built from the
Linux sources. The barebox bootloader spec loader will ignore the entry
because the 'compatible' string in the root node of the DTB does not
match what barebox expects.
Remove the 'compatible' string list from
"arch/arm/dts/socfpga_cyclone5_de0_nano_soc.dts" so that barebox uses
the upstream compatible string list. Also remove the 'model' string
("Terasic DE0-Nano-SoC/Atlas-SoC Kit") so that barebox uses the upstream
(and shorter!) model name ("Terasic DE-0(Atlas)").
Finally, update the `of_machine_is_compatible("terasic,de0-nano-soc")`
function call in `socfpga_init()` to use the "terasic,de0-atlas" string.
Cc: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://lore.barebox.org/20211105122146.29370-2-abbotti@mev.co.uk
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'arch/riscv')
0 files changed, 0 insertions, 0 deletions