On Wed, Apr 26, 2017 at 6:02 AM, Andre Przywara <[email protected]> wrote: > When a board uses a FIT image to load U-Boot proper, it requires a list > of supported device trees to be supplied in CONFIG_OF_LIST, from which it > chooses the right one at runtime. > For boards with just one possible DT (like the OrangePi PC2) this > defaults to CONFIG_DEFAULT_DEVICE_TREE, but for the Pine64 with its two > possible models we provide all compatible DTs in this config symbol. > > Signed-off-by: Andre Przywara <[email protected]> > --- > configs/pine64_plus_defconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/configs/pine64_plus_defconfig b/configs/pine64_plus_defconfig > index 92bda60..593e24a 100644 > --- a/configs/pine64_plus_defconfig > +++ b/configs/pine64_plus_defconfig > @@ -3,6 +3,7 @@ CONFIG_ARCH_SUNXI=y > CONFIG_MACH_SUN50I=y > CONFIG_RESERVE_ALLWINNER_BOOT0_HEADER=y > CONFIG_DEFAULT_DEVICE_TREE="sun50i-a64-pine64-plus" > +CONFIG_OF_LIST="sun50i-a64-pine64 sun50i-a64-pine64-plus"
fdtfile env is compile option now, so it all ways assign CONFIG_DEFAULT_DEVICE_TREE so it can't pick sun50i-a64-pine64.dtb here, are you manage this in runtime board code? thanks! -- Jagan Teki Free Software Engineer | www.openedev.com U-Boot, Linux | Upstream Maintainer Hyderabad, India. _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
