On 9/30/24 8:10 AM, Jan Kiszka wrote:
On 30.09.24 08:02, Sumit Garg wrote:
+ Jan
Hi Marek,
On Sat, 28 Sept 2024 at 03:20, Marek Vasut <ma...@denx.de> wrote:
Currently the enablement of OF_UPSTREAM results on the build system
searching for DTs only in dts/upstream/ . There are platforms which
use U-Boot specific DTBOs applied on top of U-Boot control DT during
SPL stage, and source DTs for these are located in arch/$(ARCH)/dtb.
I would like to understand the need to maintain DTBOs separately from
DTBs. Why aren't we pushing DTBOs to Linux kernel sources as we do for
DTBs? Jan recently pushed those so-called U-Boot specific DTBOs for a
TI platform which were accepted in the Linux kernel upstream. This
patch will just deny the ability to build those DTBOs from dts
upstream tree. IMHO, this takes a step backwards on the whole notion
of OF_UPSTREAM.
Exactly - I was sent the other direction (get DTSOs upstream), and I'm
now only waiting for 6.12-rc1-dts so that the first round to make use of
that can be integrated into U-Boot [1]. Anything that would prevent that
here is not welcome anymore.
I will only re-iterate what I wrote on my previous email, this commit
does not prevent building DTBOs from dts/upstream/ , they are preferred.
This only adds fallback to U-Boot local DTOs if the upstream DTOs are
not upstream yet.
If we really want a middle ground solution to allow migration to
OF_UPSTREAM easier then we need to find a way to build DTBOs from both
directories (local and upstream dts). I would imagine that will likely
complicate building and packaging DTBOs.
I tried that, and I got the clear signal that it is not desired.
Is there a link to a discussion ?
