Closed tpetazzoni closed 3 years ago
Removed the commit from bootlin/buildroot repository. Managed the U-boot patch in the BR2_EXTERNAL using the config BR2_TARGET_UBOOT_PATCH.
Can't we find a better solution than this patch ? Indeed, the goal was that users should be able to use Buildroot itself, without this BR2_EXTERNAL. With this U-Boot patch, we violate this promise.
Also, for patches we should use BR2_GLOBAL_PATCH_DIR instead.
Can't we find a better solution than this patch ? Indeed, the goal was that users should be able to use Buildroot itself, without this BR2_EXTERNAL. With this U-Boot patch, we violate this promise.
The other solution may be to build the device tree manually by BR and not by U-boot own Makefile, but I am not sure it is suitable. The user can copy the patch to his own Buildroot, is it violating the promise?
The approach of the patch would be OK if the patch was accepted upstream, but unless I'm wrong, it has not been reviewed nor accepted?
According to Christophe from ST it won't be accepted. The U-boot community has decided to not support external devicetree.
Then we need a different solution. A solution that requires a patch that we have to maintain on top of U-Boot forever is not workable.
Then using host-dtc to build device tree in the u-boot package could be the solution?
I don't have a good view on what the problem is, so I'm not sure what solutions we have. The other option is to automatically tweak the U-Boot Makefiles to build the DTB ?
yes
solve with "dtb-y=devicetreename" in uboot make parameter
Please update the documentation where the contents of the defconfigs are explained, because this is quite tricky, and probably the documentation about the STM32CubeMX integration.
https://github.com/bootlin/buildroot/commit/5c632714c065243894d735ce8b69d83beb8cf542 will not work, as it tries to apply a patch regardless of the version of U-Boot being used. This simply cannot work, as people can use any arbitrary U-Boot version.
We need to find a different solution.