From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 19 Feb 2021 11:55:54 -0500 Subject: [PATCH v4 8/8] spl: fit: Load devicetree when a Linux payload is found In-Reply-To: <20210120164656.1396639-9-mr.nuke.me@gmail.com> References: <20210120164656.1396639-1-mr.nuke.me@gmail.com> <20210120164656.1396639-9-mr.nuke.me@gmail.com> Message-ID: <20210219165554.GV10169@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Jan 20, 2021 at 10:46:56AM -0600, Alexandru Gagniuc wrote: > When a FIT config specifies a devicetree, we should load it, no > questions asked. In the case of the "simple" FIT loading path, a > difficulty arises in selecting the load address of the FDT. > > The default FDT location is right after the "kernel" or "firmware" > image. However, if that is an OP-TEE image, then the FDT may end up in > secure DRAM, and not be accessible to normal world kernels. > > Although the best solution is to be more careful about the FDT > address, a viable workaround is to only append the FDT after a u-boot > or Linux image. This is identical to the previous logic, except that > FDT loading is extended to IH_OS_LINUX images. > > Signed-off-by: Alexandru Gagniuc Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: