From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [PATCH v10 11/11] sandbox: enable capsule update for testing
Date: Wed, 2 Dec 2020 15:37:54 +0100 [thread overview]
Message-ID: <ebae2cd9-2c7f-e0e7-d02c-7d317c2e9fd9@gmx.de> (raw)
In-Reply-To: <20201130091218.66413-12-takahiro.akashi@linaro.org>
On 11/30/20 10:12 AM, AKASHI Takahiro wrote:
> Add more configuration options to allow for efi capsule update
> on sandbox.
>
> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> ---
> configs/sandbox64_defconfig | 6 ++++++
> configs/sandbox_defconfig | 6 ++++++
> 2 files changed, 12 insertions(+)
This still does not build on Gitlab CI. As indicated before the
following warning must be fixed:
common/update.c:178:12: warning: ?update_flash? defined but not used
[-Wunused-function]
178 | static int update_flash(ulong addr_source, ulong addr_first,
ulong size)
| ^~~~~~~~~~~~
Best regards
Heinrich
>
> diff --git a/configs/sandbox64_defconfig b/configs/sandbox64_defconfig
> index dc993cd13aaa..661830763feb 100644
> --- a/configs/sandbox64_defconfig
> +++ b/configs/sandbox64_defconfig
> @@ -231,3 +231,9 @@ CONFIG_TEST_FDTDEC=y
> CONFIG_UNIT_TEST=y
> CONFIG_UT_TIME=y
> CONFIG_UT_DM=y
> +#
> +CONFIG_DFU_SF=y
> +CONFIG_EFI_RUNTIME_UPDATE_CAPSULE=y
> +CONFIG_EFI_CAPSULE_ON_DISK=y
> +CONFIG_EFI_CAPSULE_FIRMWARE_FIT=y
> +CONFIG_EFI_CAPSULE_FIRMWARE_RAW=y
> diff --git a/configs/sandbox_defconfig b/configs/sandbox_defconfig
> index f2a767a4cdea..e385425b7d91 100644
> --- a/configs/sandbox_defconfig
> +++ b/configs/sandbox_defconfig
> @@ -274,3 +274,9 @@ CONFIG_TEST_FDTDEC=y
> CONFIG_UNIT_TEST=y
> CONFIG_UT_TIME=y
> CONFIG_UT_DM=y
> +#
> +CONFIG_DFU_SF=y
> +CONFIG_EFI_RUNTIME_UPDATE_CAPSULE=y
> +CONFIG_EFI_CAPSULE_ON_DISK=y
> +CONFIG_EFI_CAPSULE_FIRMWARE_FIT=y
> +CONFIG_EFI_CAPSULE_FIRMWARE_RAW=y
>
next prev parent reply other threads:[~2020-12-02 14:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 9:12 [PATCH v10 00/11] efi_loader: add capsule update support AKASHI Takahiro
2020-11-30 9:12 ` [PATCH v10 01/11] efi_loader: define UpdateCapsule api AKASHI Takahiro
2020-11-30 9:12 ` [PATCH v10 02/11] efi_loader: capsule: add capsule_on_disk support AKASHI Takahiro
2021-02-16 10:24 ` Heinrich Schuchardt
2021-02-16 11:38 ` AKASHI Takahiro
2021-03-17 21:02 ` Heinrich Schuchardt
2020-11-30 9:12 ` [PATCH v10 03/11] efi_loader: capsule: add memory range capsule definitions AKASHI Takahiro
2020-11-30 9:12 ` [PATCH v10 04/11] efi_loader: capsule: support firmware update AKASHI Takahiro
2020-11-30 9:12 ` [PATCH v10 05/11] efi_loader: add firmware management protocol for FIT image AKASHI Takahiro
2020-11-30 9:12 ` [PATCH v10 06/11] efi_loader: add firmware management protocol for raw image AKASHI Takahiro
2020-11-30 9:12 ` [PATCH v10 07/11] cmd: add "efidebug capsule" command AKASHI Takahiro
2020-11-30 9:12 ` [PATCH v10 08/11] tools: add mkeficapsule command for UEFI capsule update AKASHI Takahiro
2020-11-30 9:12 ` [PATCH v10 09/11] test/py: efi_capsule: test for FIT image capsule AKASHI Takahiro
2020-11-30 9:12 ` [PATCH v10 10/11] test/py: efi_capsule: test for raw " AKASHI Takahiro
2020-11-30 9:12 ` [PATCH v10 11/11] sandbox: enable capsule update for testing AKASHI Takahiro
2020-12-02 14:37 ` Heinrich Schuchardt [this message]
2020-12-02 15:55 ` 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=ebae2cd9-2c7f-e0e7-d02c-7d317c2e9fd9@gmx.de \
--to=xypron.glpk@gmx.de \
--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