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 v2 0/6] corstone1000: fwu metadata and GPT
Date: Mon, 05 Jun 2023 19:05:01 +0100 [thread overview]
Message-ID: <m37cshg4z6.fsf@gmail.com> (raw)
In-Reply-To: <20230529140229.3225090-1-rui.silva@linaro.org>
Hi all,
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)
>
> Cheers,
> Rui
>
> v1 [0]-> v2:
> Ilias:
> - add Reviewed-by tag in patch 1/6
>
> Heinrich:
> - fix test include nvmxip header after the move to include/
> in patch 2/6
Any other feedback on this version?
Thanks in advance.
Cheers,
Rui
>
> [0]: https://lore.kernel.org/u-boot/20230502131200.2551513-1-rui.silva@linaro.org/
>
> 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
> test/dm/nvmxip.c | 2 +-
> 7 files changed, 96 insertions(+), 16 deletions(-)
> rename {drivers/mtd/nvmxip => include}/nvmxip.h (100%)
>
> --
> 2.40.1
next prev parent reply other threads:[~2023-06-05 18:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 14:02 [PATCH v2 0/6] corstone1000: fwu metadata and GPT Rui Miguel Silva
2023-05-29 14:02 ` [PATCH v2 1/6] fwu_metadata: make sure structures are packed Rui Miguel Silva
2023-05-29 14:02 ` [PATCH v2 2/6] nvmxip: move header to include Rui Miguel Silva
2023-05-29 14:02 ` [PATCH v2 3/6] corstone1000: add fwu-metadata store info Rui Miguel Silva
2023-05-29 14:02 ` [PATCH v2 4/6] corstone1000: add boot index Rui Miguel Silva
2023-05-29 14:02 ` [PATCH v2 5/6] corstone1000: set kernel_addr based on boot_idx Rui Miguel Silva
2023-05-29 14:02 ` [PATCH v2 6/6] corstone1000: add nvmxip, fwu-mdata and gpt options Rui Miguel Silva
2023-06-05 18:05 ` Rui Miguel Silva [this message]
2023-06-10 0:37 ` [PATCH v2 0/6] corstone1000: fwu metadata and GPT Tom Rini
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=m37cshg4z6.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