> On 17.03.2018, at 09:48, Mark Kettenis <kette...@openbsd.org> wrote: > > Signed-off-by: Mark Kettenis <kette...@openbsd.org> > Acked-by: Philipp Tomsich <philipp.toms...@theobroma-systems.com> > --- > include/configs/rk3399_common.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/include/configs/rk3399_common.h b/include/configs/rk3399_common.h > index d700bf2549..9a5de3a7e3 100644 > --- a/include/configs/rk3399_common.h > +++ b/include/configs/rk3399_common.h > @@ -59,6 +59,7 @@ > #include <config_distro_bootcmd.h> > #define CONFIG_EXTRA_ENV_SETTINGS \ > ENV_MEM_LAYOUT_SETTINGS \ > + "fdtfile=rockchip/" CONFIG_DEFAULT_DEVICE_TREE ".dtb\0" \ > "partitions=" PARTS_DEFAULT \ > BOOTENV >
This assumes that the devicetree files in U-Boot and the OS are the same. As it’s our goal to keep Linux devicetrees in sync with U-Boot this patch should be fine in the long-term. But at the moment this only applies for rk3399-firefly (on Linux). Mark, where would one find the devicetrees included in OpenBSD? I looked in sys/arch/amd64 but couldn’t find any. Anyhow, I’m fine with that change. Tested-by: Klaus Goger <klaus.go...@theobroma-systems.com> — Klaus _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
