public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH V7 01/15] board: siemens: iot2050: Split the build for PG1 and PG2
Date: Wed, 29 Mar 2023 21:53:45 -0400	[thread overview]
Message-ID: <20230330015345.GG6083@bill-the-cat> (raw)
In-Reply-To: <6b4e3ad5fcb37bab55d5ad7e0d9fa7d934bfd580.1677608363.git.jan.kiszka@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

On Tue, Feb 28, 2023 at 07:19:09PM +0100, Jan Kiszka wrote:

> From: Su Baocheng <baocheng.su@siemens.com>
> 
> Due to different signature keys, the PG1 and the PG2 boards can no
> longer use the same FSBL (tiboot3). This makes it impossible anyway to
> maintaine a single flash.bin for both variants, so we can also split the
> build.
> 
> A new target is added to indicates the build is for PG1 vs. PG2 boards.
> Hence now the variants have separated defconfig files.
> 
> The runtime board_is_sr1() check does make no sense anymore, so remove
> it and replace with build time check.
> 
> Documentation is updated accordingly. New binary artifacts are already
> available via meta-iot2050.
> 
> Signed-off-by: Su Baocheng <baocheng.su@siemens.com>
> [Jan: refactor config option into targets, tweak some wordings]
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

For the series, applied to u-boot/next, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  parent reply	other threads:[~2023-03-30  1:53 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 18:19 [PATCH V7 00/15] IOT2050-related enhancements Jan Kiszka
2023-02-28 18:19 ` [PATCH V7 01/15] board: siemens: iot2050: Split the build for PG1 and PG2 Jan Kiszka
2023-03-01 17:26   ` Andrew Davis
2023-03-01 18:29     ` Jan Kiszka
2023-03-01 18:34       ` Andrew Davis
2023-03-01 19:21         ` Jan Kiszka
2023-03-01 19:29           ` Andrew Davis
2023-03-30  9:17             ` Simon Glass
2023-03-30  1:53   ` Tom Rini [this message]
2023-02-28 18:19 ` [PATCH V7 02/15] arm: dts: iot2050: Use the auto generator nodes for fdt Jan Kiszka
2023-03-01 23:39   ` Simon Glass
2023-02-28 18:19 ` [PATCH V7 03/15] iot2050: Update firmware layout Jan Kiszka
2023-02-28 18:19 ` [PATCH V7 04/15] iot2050: Migrate settings into board env file Jan Kiszka
2023-03-01 23:38   ` Simon Glass
2023-03-02  6:38     ` Jan Kiszka
2023-03-06 17:53       ` Simon Glass
2023-02-28 18:19 ` [PATCH V7 05/15] iot2050: Add watchdog start to bootcmd Jan Kiszka
2023-02-28 18:19 ` [PATCH V7 06/15] iot2050: Add CFG_ENV_FLAGS_LIST_STATIC Jan Kiszka
2023-02-28 18:19 ` [PATCH V7 07/15] arm: dts: iot2050: Allow verifying U-Boot proper by SPL Jan Kiszka
2023-03-01 23:39   ` Simon Glass
2023-02-28 18:19 ` [PATCH V7 08/15] tools: Add script for converting public key into device tree include Jan Kiszka
2023-03-11  1:37   ` Simon Glass
2023-02-28 18:19 ` [PATCH V7 09/15] iot2050: Add script for signing artifacts Jan Kiszka
2023-03-06 17:53   ` Simon Glass
2023-02-28 18:19 ` [PATCH V7 10/15] arm: dts: iot2050: Optionally embed OTP programming data into image Jan Kiszka
2023-02-28 18:19 ` [PATCH V7 11/15] doc: iot2050: Add a note about the watchdog firmware Jan Kiszka
2023-02-28 18:19 ` [PATCH V7 12/15] board: siemens: iot2050: use the named gpio to control the user-button Jan Kiszka
2023-03-01 23:38   ` Simon Glass
2023-02-28 18:19 ` [PATCH V7 13/15] iot2050: Refresh defconfigs and activate CONFIG_EFI_SCROLL_ON_CLEAR_SCREEN Jan Kiszka
2023-03-01 17:37   ` Andrew Davis
2023-03-01 23:38   ` Simon Glass
2023-02-28 18:19 ` [PATCH V7 14/15] arm: dts: iot2050: Add support for M.2 variant Jan Kiszka
2023-02-28 18:19 ` [PATCH V7 15/15] iot2050: Add support for configuring M.2 connector Jan Kiszka
2023-03-01 23:38   ` Simon Glass
2023-03-02  6:36     ` 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=20230330015345.GG6083@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=jan.kiszka@siemens.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