From: Peng Fan <peng.fan@oss.nxp.com>
To: Caleb Connolly <caleb.connolly@linaro.org>
Cc: Lukasz Majewski <lukma@denx.de>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Tom Rini <trini@konsulko.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Sumit Garg <sumit.garg@kernel.org>,
u-boot@lists.denx.de, u-boot-qcom@groups.io
Subject: Re: [PATCH 4/4] qcom_defconfig: enable capsule update support
Date: Thu, 27 Mar 2025 16:46:04 +0800 [thread overview]
Message-ID: <20250327084603.GA5432@nxa18884-linux> (raw)
In-Reply-To: <20250326-b4-qcom-capsule-update-improvements-v1-4-afe2e3696675@linaro.org>
On Wed, Mar 26, 2025 at 06:40:37PM +0100, Caleb Connolly wrote:
>We can now correctly identify which partition U-Boot is flashed to
>between uefi, xbl, and boot (including A/B support) so enable capsule
>update support for all boards.
>
>Signed-off-by: Caleb Connolly <caleb.connolly@linaro.org>
>---
> configs/qcm6490_defconfig | 6 ------
> configs/qcom_defconfig | 3 +++
> 2 files changed, 3 insertions(+), 6 deletions(-)
>
>diff --git a/configs/qcm6490_defconfig b/configs/qcm6490_defconfig
>index ba26924da161b1c4b5378955185f314b05cb1006..5ddc5ab3ef8cfe8f9cc09eb573c1a8130b394b43 100644
>--- a/configs/qcm6490_defconfig
>+++ b/configs/qcm6490_defconfig
>@@ -18,10 +18,4 @@ CONFIG_DEBUG_UART_CLOCK=14745600
> CONFIG_TEXT_BASE=0x9fc00000
> CONFIG_REMAKE_ELF=y
>
> CONFIG_DEFAULT_DEVICE_TREE="qcom/qcs6490-rb3gen2"
>-
>-# Enable capsule updates
>-CONFIG_EFI_RUNTIME_UPDATE_CAPSULE=y
>-CONFIG_EFI_CAPSULE_ON_DISK=y
>-CONFIG_EFI_IGNORE_OSINDICATIONS=y
>-CONFIG_EFI_CAPSULE_FIRMWARE_RAW=y
>diff --git a/configs/qcom_defconfig b/configs/qcom_defconfig
>index ba4d38d100e053e3708ee2623bf3530787b6b94f..d69185f3c2f0452e6757b785a023cf612bfa3839 100644
>--- a/configs/qcom_defconfig
>+++ b/configs/qcom_defconfig
>@@ -5,8 +5,11 @@ CONFIG_SYS_INIT_SP_BSS_OFFSET=1572864
> CONFIG_ARCH_SNAPDRAGON=y
> CONFIG_NR_DRAM_BANKS=24
> CONFIG_DEFAULT_DEVICE_TREE="qcom/sdm845-db845c"
> CONFIG_SYS_LOAD_ADDR=0xA0000000
>+CONFIG_EFI_RUNTIME_UPDATE_CAPSULE=y
>+CONFIG_EFI_CAPSULE_ON_DISK=y
>+CONFIG_EFI_CAPSULE_FIRMWARE_RAW=y
> CONFIG_BUTTON_CMD=y
> CONFIG_FIT=y
> CONFIG_FIT_VERBOSE=y
> CONFIG_BOOTSTD_FULL=y
For capsule update, CONFIG_EFI_MM_COMM_TEE is not needed?
Regards,
Peng
>
>--
>2.49.0
>
next prev parent reply other threads:[~2025-03-27 7:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 17:40 [PATCH 0/4] Qualcomm: expand capsule update support Caleb Connolly
2025-03-26 17:40 ` [PATCH 1/4] mach-snapdragon: track boot source Caleb Connolly
2025-03-31 13:52 ` Neil Armstrong
2025-03-26 17:40 ` [PATCH 2/4] mach-snapdragon: CapsuleUpdate: support all boot methods Caleb Connolly
2025-04-01 8:45 ` Neil Armstrong
2025-04-11 14:48 ` Caleb Connolly
2025-04-01 12:42 ` Ilias Apalodimas
2025-04-03 12:47 ` Caleb Connolly
2025-03-26 17:40 ` [PATCH 3/4] dfu: scsi: don't call scsi_scan() Caleb Connolly
2025-03-31 13:52 ` Neil Armstrong
2025-03-31 13:53 ` Ilias Apalodimas
2025-03-26 17:40 ` [PATCH 4/4] qcom_defconfig: enable capsule update support Caleb Connolly
2025-03-27 8:46 ` Peng Fan [this message]
2025-03-27 12:30 ` Caleb Connolly
2025-03-31 13:52 ` Ilias Apalodimas
2025-03-26 17:44 ` [PATCH 0/4] Qualcomm: expand " Caleb Connolly
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=20250327084603.GA5432@nxa18884-linux \
--to=peng.fan@oss.nxp.com \
--cc=caleb.connolly@linaro.org \
--cc=lukma@denx.de \
--cc=mkorpershoek@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=sumit.garg@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot-qcom@groups.io \
--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