From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Simon Glass <sjg@chromium.org>
Cc: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
u-boot@lists.denx.de, Sughosh Ganu <sughosh.ganu@linaro.org>,
AKASHI Takahiro <takahiro.akashi@linaro.org>
Subject: Re: [PATCH 1/1] sandbox: enable CONFIG_EFI_CAPSULE_AUTHENTICATE
Date: Wed, 19 Apr 2023 09:05:32 +0300 [thread overview]
Message-ID: <ZD+ErJ2s5duwi9kc@hera> (raw)
In-Reply-To: <CAPnjgZ0GdSp5Jm3YzN-raDcQBP+Pjp2A0K0542D4KYb8iE+45g@mail.gmail.com>
On Tue, Apr 18, 2023 at 10:47:24AM -0600, Simon Glass wrote:
> Hi Heinrich,
>
> On Fri, 14 Apr 2023 at 02:39, Heinrich Schuchardt
> <heinrich.schuchardt@canonical.com> wrote:
> >
> > Without CONFIG_EFI_CAPSULE_AUTHENTICATE=y the following tests are skipped:
> >
> > * test/py/tests/test_efi_capsule/test_capsule_firmware_signed_fit.py
> > * test/py/tests/test_efi_capsule/test_capsule_firmware_signed_raw.py
> >
> > Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> > ---
> > configs/sandbox_defconfig | 1 +
> > configs/sandbox_flattree_defconfig | 1 +
> > 2 files changed, 2 insertions(+)
> >
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>
> This still has the problem that it reboots in the middle of the test.
> Can we get that fixed? If someone at Linaro isn't interested I could
> take a look at it.
I think we discussed this in the past. We *need* to reboot as that's what
the EFI describes. Why is it a problem?
Regards
/Ilias
>
> Regards,
> Simon
next prev parent reply other threads:[~2023-04-19 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 8:39 [PATCH 1/1] sandbox: enable CONFIG_EFI_CAPSULE_AUTHENTICATE Heinrich Schuchardt
2023-04-18 8:44 ` Ilias Apalodimas
2023-04-18 16:47 ` Simon Glass
2023-04-19 6:05 ` Ilias Apalodimas [this message]
2023-04-19 22:40 ` Simon Glass
2023-04-20 6:30 ` Ilias Apalodimas
2023-04-20 7:12 ` AKASHI Takahiro
2023-04-20 7:34 ` Heinrich Schuchardt
2023-04-24 19:42 ` Simon Glass
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=ZD+ErJ2s5duwi9kc@hera \
--to=ilias.apalodimas@linaro.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=takahiro.akashi@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.