From: Rui Miguel Silva <rui.silva@linaro.org>
To: u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH 0/6] corstone1000: fwu metadata and GPT
Date: Mon, 29 May 2023 09:39:39 +0100 [thread overview]
Message-ID: <m3zg5n8ras.fsf@gmail.com> (raw)
In-Reply-To: <m3lehppvvl.fsf@gmail.com>
Hi,
Rui Miguel Silva <rui.silva@linaro.org> writes:
> Hi,
> Rui Miguel Silva <rui.silva@linaro.org> writes:
>> Now that the nvmxip block driver is merged we can add on top
>> of it the platform code to use GPT and FWU metadata in the
>> Corstone1000.
>>
>> But first, push 2 fixes that are needed to make all this work:
>> - move nvmxip header to include
>> - setup fwu metadata structures as packed (we have a 32bit
>> writer - Secure enclave Cortex-M0 and a 64bit reader host
>> Cortex-A35)
>
> Gentle ping.
>
> Cheers,
> Rui
It would be great to have some feedback on this ones.
Many thanks.
Cheers,
Rui
>>
>> Cheers,
>> Rui
>>
>> Rui Miguel Silva (6):
>> fwu_metadata: make sure structures are packed
>> nvmxip: move header to include
>> corstone1000: add fwu-metadata store info
>> corstone1000: add boot index
>> corstone1000: set kernel_addr based on boot_idx
>> corstone1000: add nvmxip, fwu-mdata and gpt options
>>
>> arch/arm/dts/corstone1000.dtsi | 7 ++-
>> board/armltd/corstone1000/corstone1000.c | 73 +++++++++++++++++++++-
>> board/armltd/corstone1000/corstone1000.env | 10 +--
>> configs/corstone1000_defconfig | 14 ++++-
>> include/fwu_mdata.h | 6 +-
>> {drivers/mtd/nvmxip => include}/nvmxip.h | 0
>> 6 files changed, 95 insertions(+), 15 deletions(-)
>> rename {drivers/mtd/nvmxip => include}/nvmxip.h (100%)
>>
>> --
>> 2.40.0
prev parent reply other threads:[~2023-05-29 8:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 13:11 [PATCH 0/6] corstone1000: fwu metadata and GPT Rui Miguel Silva
2023-05-02 13:11 ` [PATCH 1/6] fwu_metadata: make sure structures are packed Rui Miguel Silva
2023-05-03 8:06 ` Ilias Apalodimas
2023-05-29 8:48 ` Heinrich Schuchardt
2023-05-29 13:12 ` Rui Miguel Silva
2023-05-29 13:18 ` Ilias Apalodimas
2023-05-29 13:47 ` Rui Miguel Silva
2023-05-02 13:11 ` [PATCH 2/6] nvmxip: move header to include Rui Miguel Silva
2023-05-29 8:51 ` Heinrich Schuchardt
2023-05-29 13:13 ` Rui Miguel Silva
2023-05-02 13:11 ` [PATCH 3/6] corstone1000: add fwu-metadata store info Rui Miguel Silva
2023-05-02 13:11 ` [PATCH 4/6] corstone1000: add boot index Rui Miguel Silva
2023-05-02 13:11 ` [PATCH 5/6] corstone1000: set kernel_addr based on boot_idx Rui Miguel Silva
2023-05-02 13:12 ` [PATCH 6/6] corstone1000: add nvmxip, fwu-mdata and gpt options Rui Miguel Silva
2023-05-15 13:27 ` [PATCH 0/6] corstone1000: fwu metadata and GPT Rui Miguel Silva
2023-05-29 8:39 ` Rui Miguel Silva [this message]
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=m3zg5n8ras.fsf@gmail.com \
--to=rui.silva@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=sjg@chromium.org \
--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