> On 22.06.2018, at 16:23, Vagrant Cascadian <vagr...@debian.org> wrote: > > On 2018-05-27, Vagrant Cascadian wrote: >> On 2018-05-25, Klaus Goger wrote: >>> Currently the fdtfile environment variable is set to >>> CONFIG_DEFAULT_DEVICE_TREE which is Ñ–nternally used as U-Boot devicetree >>> source. The OS can use a different filename and Kconfig gives us the >>> ability to select a default devicetree via CONFIG_DEFAULT_FDT_FILE. >>> This also gives user configuring U-Boot via menuconfig the behaviour >>> someone would expect. > ... >> Tested on puma-rk3399. >> >> Tested-By: Vagrant Cascadian <vagr...@debian.org> >> >> Was hoping to also test on firefly-rk3399, but having difficulty getting >> u-boot installed unreleated to this patch. > > Finally was able to test on Firefly-RK3399 applied against u-boot > 2018.07-rc2, and it also works correctly. > > Are there any outstanding concerns with this patch?
There was a similar patch for sunxi[1] and there it was decided to introduce the Kconfig option we talked about. That would make this patch obsolete. @Jagan, I think Martin is still waiting for an answer from you. [1] https://patchwork.ozlabs.org/patch/923692/
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
