On 06/10/2020 13:52, Heinrich Schuchardt wrote:
On 06.10.20 14:43, Grant Likely wrote:
Current U-Boot by default uses the same DT image for both U-Boot
internal setup and to provide to the OS. This should be split so that
the U-Boot internal version has what U-Boot needs without needs to track
mainline Linux DTB schema.
I've been looking into a generic config for adding a separate OS-dtb to
U-Boot that is not used internally and is only passed to the OS. That
would solve the problem you're seeing above.
What would be the advantage of building said second device-tree into
U-Boot instead of loading it from a (possibly signed) file?
I would see that as an implementation detail, but from the OS point of
view EBBR requires the firmware to provide a DTB to the OS without the
OS having any involvement in providing it. The easiest solution is to
embed the OS dtb into U-Boot, but it could be loaded and verified from a
file as well.
g.
