summaryrefslogtreecommitdiff
path: root/cmd/stackprot_test.c
diff options
context:
space:
mode:
authorAndrew Davis <afd@ti.com>2025-04-25 17:54:03 -0500
committerTom Rini <trini@konsulko.com>2025-05-02 15:32:45 -0600
commitc492a55fe40cb9d86b0e99c160e21e5f8f4edcdc (patch)
tree0525139c840abf6aa184f1d4e2fd0e81e0f63475 /cmd/stackprot_test.c
parent78c0f7e3eb0dc96df163cd5ec51de80a28fb31e7 (diff)
arm: dts: k3: binman: Fix DM firmware selection
Just like TF-A and OP-TEE, the documentation states a custom path for DM can be provided at build time by setting TI_DM. This should then set ti-dm-path which updates ti-dm node filenames in binman. Two issues prevent this from functioning for most K3 boards. One is when then DM firmware name is inside a blob-ext node instead of a ti-dm node. The second is when the filename in the ti-dm node is a pointer to a blob-ext node. In this case even though the filename is updated, the filename in the blob-ext is not, so build can fail if the default file in the blob-ext cannot be found, even if the updated ti-dm file does exist. Fix both of these for all K3 by removing any indirect ti-dm nodes and making sure all DM nodes are labeled with "ti-dm". Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Bryan Brattlof <bb@ti.com> Reviewed-by: Neha Malcom Francis <n-francis@ti.com>
Diffstat (limited to 'cmd/stackprot_test.c')
0 files changed, 0 insertions, 0 deletions