From: Jon Humphreys <j-humphreys@ti.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Michal Simek <michal.simek@amd.com>
Cc: <u-boot@lists.denx.de>, Raymond Mao <raymond.mao@linaro.org>,
"Caleb Connolly" <caleb.connolly@linaro.org>,
Adriano Cordova <adrianox@gmail.com>,
Udit Kumar <u-kumar1@ti.com>, Simon Glass <sjg@chromium.org>,
Devarsh Thakkar <devarsht@ti.com>, Hari Nagalla <hnagalla@ti.com>,
Manorit Chawdhry <m-chawdhry@ti.com>,
Santhosh Kumar K <s-k6@ti.com>,
Neha Malcom Francis <n-francis@ti.com>,
Daniel Schultz <d.schultz@phytec.de>,
Neil Armstrong <neil.armstrong@linaro.org>,
"Aashvij Shenai" <a-shenai@ti.com>,
Roger Quadros <rogerq@kernel.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
Bryan Brattlof <bb@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Wadim Egorov <w.egorov@phytec.de>, Tom Rini <trini@konsulko.com>,
Robert Nelson <robertcnelson@gmail.com>,
Nishanth Menon <nm@ti.com>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
Lukasz Majewski <lukma@denx.de>, <s-vadapalli@ti.com>
Subject: Re: [PATCH v4 1/3] xilinx: dfu: Fill directly update_info.dfu_string
Date: Fri, 28 Feb 2025 12:15:08 -0600 [thread overview]
Message-ID: <86frjyndg3.fsf@udb0321960.dhcp.ti.com> (raw)
In-Reply-To: <84a24111-d03b-447a-b451-e95fe3e7736e@gmx.de>
Heinrich Schuchardt <xypron.glpk@gmx.de> writes:
> On 28.02.25 16:41, Michal Simek wrote:
>>
>>
>> On 2/28/25 15:33, Heinrich Schuchardt wrote:
>>> On 26.02.25 23:35, Jonathan Humphreys wrote:
>>>> From: Michal Simek <michal.simek@amd.com>
>>>>
>>>> Directly fill update_info.dfu_string to prepare platforms to switch
>>>> from using dfu_alt_info variable to dfu_string which contains
>>>> description
>>>> for capsule update when switch is done.
>>>
>>> Other platforms only set the environment variable.
>>
>> Not really.
>>
>> git grep \.dfu_string board/
>>
>> beagle, imx, rpi, ti and others are also doing it.
>
> But why do we have platforms that don't?
>
I'm not aware of the history of the Xilinx platforms and why they didn't,
but Michal has fixed this. I'm not aware of any other platforms not
setting .dfu_string.
Jon
>>
>>>
>>> Do we have a problem that needs to be solved for all problems?
>>> Or is anything special about the Xilinx platform?
>>>
>>> If we have a general problem, solving it for Xilinx only would not be
>>> the right approach.
>>
>> This is just preparation patch for switch in 3/3 because then Jon would
>> have to do this change in his patch.
>> But the biggest reason is when 2/3 is applied, capsule update will stop
>> to work on our platform and I wanted to make sure that we can avoid it.
>>
>> Thanks,
>> Michal
>>
>>
next prev parent reply other threads:[~2025-02-28 18:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 22:35 [PATCH v4 0/3] EFI Capsule update explicitly sets dfu_alt_info Jonathan Humphreys
2025-02-26 22:35 ` [PATCH v4 1/3] xilinx: dfu: Fill directly update_info.dfu_string Jonathan Humphreys
2025-02-28 14:33 ` Heinrich Schuchardt
2025-02-28 15:41 ` Michal Simek
2025-02-28 15:46 ` Heinrich Schuchardt
2025-02-28 18:15 ` Jon Humphreys [this message]
2025-03-03 14:02 ` Michal Simek
2025-02-26 22:35 ` [PATCH v4 2/3] efi_firmware: set EFI capsule dfu_alt_info env explicitly Jonathan Humphreys
2025-03-12 6:40 ` Ilias Apalodimas
2025-02-26 22:35 ` [PATCH v4 3/3] board: remove capsule update support in set_dfu_alt_info() Jonathan Humphreys
2025-02-27 5:07 ` Wadim Egorov
2025-04-09 14:52 ` [PATCH v4 0/3] EFI Capsule update explicitly sets dfu_alt_info Michal Simek
2025-04-09 21:36 ` Jon Humphreys
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=86frjyndg3.fsf@udb0321960.dhcp.ti.com \
--to=j-humphreys@ti.com \
--cc=a-shenai@ti.com \
--cc=adrianox@gmail.com \
--cc=bb@ti.com \
--cc=caleb.connolly@linaro.org \
--cc=d.schultz@phytec.de \
--cc=devarsht@ti.com \
--cc=hnagalla@ti.com \
--cc=ilias.apalodimas@linaro.org \
--cc=lukma@denx.de \
--cc=m-chawdhry@ti.com \
--cc=michal.simek@amd.com \
--cc=mkorpershoek@baylibre.com \
--cc=n-francis@ti.com \
--cc=neil.armstrong@linaro.org \
--cc=nm@ti.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=raymond.mao@linaro.org \
--cc=robertcnelson@gmail.com \
--cc=rogerq@kernel.org \
--cc=s-k6@ti.com \
--cc=s-vadapalli@ti.com \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
--cc=xypron.glpk@gmx.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