From: Andrew Davis <afd@ti.com>
To: Tom Rini <trini@konsulko.com>
Cc: Nishanth Menon <nm@ti.com>, Ryan Eatmon <reatmon@ti.com>,
Praneeth Bajjuri <praneeth@ti.com>, Bryan Brattlof <bb@ti.com>,
<u-boot@lists.denx.de>
Subject: Re: [PATCH] include: configs: Change dtb names in fitImage to match oe-core
Date: Fri, 31 Mar 2023 13:23:23 -0500 [thread overview]
Message-ID: <ddec1ceb-9e68-13a6-3d2c-05755f1361f6@ti.com> (raw)
In-Reply-To: <20230331181112.GC13222@bill-the-cat>
On 3/31/23 1:11 PM, Tom Rini wrote:
> On Fri, Mar 31, 2023 at 12:19:14PM -0500, Andrew Davis wrote:
>> On 3/31/23 12:04 PM, Nishanth Menon wrote:
>>> On 16:06-20230330, Ryan Eatmon wrote:
>>>> The oe-core class for assembling the fitImage includes the vendor
>>>> sub-directory (with the / changed to _) in the config sections of
>>>> the fitImage. Our env var settings for chosing which section to
>>>> boot from needs to be updated to agree with the fitImage.
>>>>
>>>> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
>>>> ---
>>>> include/configs/am64x_evm.h | 4 ++--
>>>> include/configs/am65x_evm.h | 2 +-
>>>> include/configs/j721e_evm.h | 6 +++---
>>>> include/configs/j721s2_evm.h | 6 +++---
>>>> 4 files changed, 9 insertions(+), 9 deletions(-)
>>>>
>>>> diff --git a/include/configs/am64x_evm.h b/include/configs/am64x_evm.h
>>>> index 26a7f2521e..456a44730c 100644
>>>> --- a/include/configs/am64x_evm.h
>>>> +++ b/include/configs/am64x_evm.h
>>>> @@ -26,9 +26,9 @@
>>>> #define EXTRA_ENV_AM642_BOARD_SETTINGS \
>>>> "findfdt=" \
>>>> "if test $board_name = am64x_gpevm; then " \
>>>> - "setenv fdtfile k3-am642-evm.dtb; fi; " \
>>>> + "setenv fdtfile ti_k3-am642-evm.dtb; fi; " \
>>>> "if test $board_name = am64x_skevm; then " \
>>>> - "setenv fdtfile k3-am642-sk.dtb; fi;" \
>>>> + "setenv fdtfile ti_k3-am642-sk.dtb; fi;" \
>>>
>>>
>>> Kernel.org builds k3-am642-sk.dtb
>>>
>>
>> Nope, kernel.org build ti/k3-am642-sk.dtb
>>
>>> Why would we want to go and fix it with non-standard?
>>>
>>
>> The dtbs need to have their dir prefixed or there could be collisions
>
> The key here is we're talking about what's used in FIT images, and not
> just loaded directly. All of the cases where fdtfile is used on arm64
> platforms in tree today use "/" because it's loading a literal. In this
> case, why again is OE mangling the name, and what are we using it for
> again here? In other words, why can't it be treated as "/" to match the
> load a file case? And if it _must_ be mangled, must we still use fdtfile
> and not something else?
>
So to match other plats, we should:
setenv fdtfile ti/k3-am642-sk.dtb
That way loading works in the non-FIT case (and we just need to stop moving
all the DTBs out of the ti/ to the root dir (which is probably broken on our
part anyway..))
Then when we use "fdtfile" in the FIT case, we just mangle ("/"->"_") it
at that point only before use. That work for everyone?
Andrew
next prev parent reply other threads:[~2023-03-31 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 21:06 [PATCH] include: configs: Change dtb names in fitImage to match oe-core Ryan Eatmon
2023-03-31 17:04 ` Nishanth Menon
2023-03-31 17:19 ` Andrew Davis
2023-03-31 18:11 ` Tom Rini
2023-03-31 18:23 ` Andrew Davis [this message]
2023-03-31 18:36 ` Tom Rini
2023-03-31 18:52 ` Andrew Davis
2023-03-31 19:06 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2023-03-30 20:55 Ryan Eatmon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ddec1ceb-9e68-13a6-3d2c-05755f1361f6@ti.com \
--to=afd@ti.com \
--cc=bb@ti.com \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox