From: Daniel Schultz <d.schultz@phytec.de>
To: Yannic Moog <Y.Moog@phytec.de>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"joe.hershberger@ni.com" <joe.hershberger@ni.com>,
"trini@konsulko.com" <trini@konsulko.com>,
Wadim Egorov <W.Egorov@phytec.de>
Cc: "kamlesh@ti.com" <kamlesh@ti.com>,
"d-gole@ti.com" <d-gole@ti.com>, Benjamin Hahn <B.Hahn@phytec.de>,
"m-chawdhry@ti.com" <m-chawdhry@ti.com>,
"mkorpershoek@baylibre.com" <mkorpershoek@baylibre.com>,
"jm@ti.com" <jm@ti.com>,
PHYTEC Upstream <upstream@lists.phytec.de>,
"nm@ti.com" <nm@ti.com>, Teresa Remmet <T.Remmet@phytec.de>
Subject: Re: [PATCH 1/6] include: env: phytec: overlays: Add extension command
Date: Tue, 9 Jul 2024 15:31:50 +0200 [thread overview]
Message-ID: <d5790f87-e4d4-4ac8-9858-2bb199f195ef@phytec.de> (raw)
In-Reply-To: <510c99dfff5e17768df3fde691d96d848e288583.camel@phytec.de>
Hi Yannic,
On 09.07.24 08:49, Yannic Moog wrote:
> Hello Daniel,
>
> On Sun, 2024-07-07 at 23:07 -0700, Daniel Schultz wrote:
>> Add a new environment routine to apply extensions. Our SOM detection
>> adds overlays via the extension framework to alter the kernel
>> device-tree according to the flashed EEPROM image.
>>
>> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
>> ---
>> include/env/phytec/overlays.env | 20 ++++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>>
>> diff --git a/include/env/phytec/overlays.env b/include/env/phytec/overlays.env
>> index 78721cde654..50110e731bd 100644
>> --- a/include/env/phytec/overlays.env
>> +++ b/include/env/phytec/overlays.env
>> @@ -23,6 +23,16 @@ mmc_apply_overlays=
>> fi;
>> done;
>> fi;
>> +#ifdef CONFIG_CMD_EXTENSION
>> +mmc_apply_extensions=
>> + setenv extension_overlay_addr ${fdtoverlay_addr_r};
>> + setenv extension_overlay_cmd 'load mmc ${mmcdev}:${mmcpart}
>> + ${fdtoverlay_addr_r} ${extension_overlay_name}';
>> + extension scan;
>> + extension apply all;
>> +#else
>> +mmc_apply_extensions=echo "no extension command"
> Do you think it makes sense to make this fail? I would think "apply_extensions" would be
> unsuccessful if extensions are not working.
Technically, you don't need our SOM detection overlays. They just make
the boot nicer and you don't have any probe errors or other error
messages. So, in my opinion, it's better not apply them instead of
stopping the entire boot.
Regards,
Daniel
>
> Yannic
>
>> +#endif
>> net_load_bootenv=${get_cmd} ${bootenv_addr_r} ${bootenv}
>> net_load_overlay=${get_cmd} ${fdtoverlay_addr_r} ${overlay}
>> net_apply_overlays=
>> @@ -36,3 +46,13 @@ net_apply_overlays=
>> fi;
>> done;
>> fi;
>> +#ifdef CONFIG_CMD_EXTENSION
>> +net_apply_extensions=
>> + setenv extension_overlay_addr ${fdtoverlay_addr_r};
>> + setenv extension_overlay_cmd '${get_cmd} ${fdtoverlay_addr_r}
>> + ${extension_overlay_name}';
>> + extension scan;
>> + extension apply all;
>> +#else
>> +net_apply_extensions=echo "no extension command"
>> +#endif
next prev parent reply other threads:[~2024-07-09 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 6:07 [PATCH 0/6] Extend SOM detection Daniel Schultz
2024-07-08 6:07 ` [PATCH 1/6] include: env: phytec: overlays: Add extension command Daniel Schultz
2024-07-09 6:49 ` Yannic Moog
2024-07-09 13:31 ` Daniel Schultz [this message]
2024-07-09 13:47 ` Wadim Egorov
2024-07-10 5:38 ` Yannic Moog
2024-07-08 6:07 ` [PATCH 2/6] include: env: phytec: k3_mmc: Apply extension overlays Daniel Schultz
2024-07-08 6:07 ` [PATCH 3/6] board: phytec: common: k3: Add SOM detection overlays Daniel Schultz
2024-07-08 6:07 ` [PATCH 4/6] board: phytec: common: Kconfig: Enable SUPPORT_EXTENSION_SCAN Daniel Schultz
2024-07-08 6:07 ` [PATCH 5/6] configs: phytec_am62x_a53_defconfig: Set CONFIG_CMD_EXTENSION Daniel Schultz
2024-07-08 6:07 ` [PATCH 6/6] configs: phycore_am64x_a53_defconfig: Enable SOM detection Daniel Schultz
2024-07-09 7:16 ` [PATCH 0/6] Extend " Daniel Schultz
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=d5790f87-e4d4-4ac8-9858-2bb199f195ef@phytec.de \
--to=d.schultz@phytec.de \
--cc=B.Hahn@phytec.de \
--cc=T.Remmet@phytec.de \
--cc=W.Egorov@phytec.de \
--cc=Y.Moog@phytec.de \
--cc=d-gole@ti.com \
--cc=jm@ti.com \
--cc=joe.hershberger@ni.com \
--cc=kamlesh@ti.com \
--cc=m-chawdhry@ti.com \
--cc=mkorpershoek@baylibre.com \
--cc=nm@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.