From: Tom Rini <trini@konsulko.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, Marek Vasut <marex@denx.de>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
chao zeng <chao.zeng@siemens.com>,
Su Baocheng <baocheng.su@siemens.com>,
Joe Hershberger <joe.hershberger@ni.com>,
Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH V2 00/13] IOT2050-related enhancements
Date: Wed, 26 Oct 2022 09:54:58 -0400 [thread overview]
Message-ID: <20221026135458.GT2020586@bill-the-cat> (raw)
In-Reply-To: <de0b8464-97a4-d682-28b1-c1a88f3a3f49@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
On Wed, Oct 26, 2022 at 09:28:09AM +0200, Jan Kiszka wrote:
> On 05.10.22 10:33, Jan Kiszka wrote:
> > (Almost) flushing our upstream queue for the IOT2050 device, this mostly
> > brings board-specific changes such as:
> >
> > - updated build process and firmware layout for PG1 vs. PG2 devices
> > - more watchdog preparations
> > - preparations for verified boot on IOT2050 Advanced devices
> >
> > There are also some generic extensions in this series which are
> > dependencies for the above:
> >
> > - env: Complete generic support for writable list
> > - env: Couple networking-related variable flags to CONFIG_NET (repost)
> > - tools: Add script for converting public key into device tree include
> >
> > Changes in v2:
> > - rebased over latest master
> > - reworked patch 1 to be less invasive to the code
> > - added "iot2050: use the named gpio to control the user-button"
> >
> > Still in our backlog is support for a new variant that comes with M.2
> > slots. But that requires some more rework first.
>
> Any remaining questions/remarks for this series? Asking also as we would
> like to move forward with upstreaming that M.2 support which depends on
> this one here.
Marek, I believe you had concerns about the environment side of v1 here,
is v2 more to your liking? Thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-10-26 13:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 8:33 [PATCH V2 00/13] IOT2050-related enhancements Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 01/13] env: Complete generic support for writable list Jan Kiszka
2022-10-27 7:49 ` Stefan Herbrechtsmeier
2022-10-27 12:38 ` Jan Kiszka
2022-10-28 8:34 ` Stefan Herbrechtsmeier
2022-10-05 8:33 ` [PATCH V2 02/13] env: Couple networking-related variable flags to CONFIG_NET Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 03/13] tools: Add script for converting public key into device tree include Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 04/13] board: siemens: iot2050: Split the build for PG1 and PG2 Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 05/13] arm: dts: iot2050: Use the auto generator nodes for fdt Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 06/13] iot2050: Update firmware layout Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 07/13] iot2050: Add watchdog start to bootcmd Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 08/13] iot2050: Add CONFIG_ENV_FLAGS_LIST_STATIC Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 09/13] arm: dts: iot2050: Allow verifying U-Boot proper by SPL Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 10/13] iot2050: Add script for signing artifacts Jan Kiszka
2022-10-05 15:58 ` Simon Glass
2022-10-05 16:04 ` Jan Kiszka
2022-10-05 16:16 ` Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 11/13] arm: dts: iot2050: Optionally embed OTP programming data into image Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 12/13] doc: iot2050: Add a note about the watchdog firmware Jan Kiszka
2022-10-05 8:33 ` [PATCH V2 13/13] board: siemens: iot2050: use the named gpio to control the user-button Jan Kiszka
2022-10-26 7:28 ` [PATCH V2 00/13] IOT2050-related enhancements Jan Kiszka
2022-10-26 13:54 ` Tom Rini [this message]
2022-10-26 14:03 ` Marek Vasut
2022-10-26 15:55 ` Jan Kiszka
2022-10-26 21:02 ` Marek Vasut
2022-10-27 4:32 ` Jan Kiszka
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=20221026135458.GT2020586@bill-the-cat \
--to=trini@konsulko.com \
--cc=baocheng.su@siemens.com \
--cc=chao.zeng@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=joe.hershberger@ni.com \
--cc=marex@denx.de \
--cc=sjg@chromium.org \
--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