From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/1] rsa: fix retrieving public exponent on big-endian systems
Date: Mon, 12 Oct 2020 07:41:07 -0400 [thread overview]
Message-ID: <20201012114107.GV14816@bill-the-cat> (raw)
In-Reply-To: <5ff30fd6-2790-64c8-70b2-df14a0aa4c0d@prevas.dk>
On Mon, Oct 12, 2020 at 09:04:28AM +0200, Rasmus Villemoes wrote:
> On 09/10/2020 15.08, Tom Rini wrote:
> > On Wed, Oct 07, 2020 at 12:17:56AM +0200, Rasmus Villemoes wrote:
> >> On 07/10/2020 00.02, Simon Glass wrote:
> >>>
> >>> Reviewed-by: Simon Glass <sjg@chromium.org>
> >>>
> >>> Is there a way to add a test for this?
> >>
> >> Not that I can think of, other than finding some BE board and hooking it
> >> up in some CI. Apparently not very many people use verified boot on BE
> >> platforms :( or at least they don't follow upstream U-Boot closely.
> >
> > We have tests for verified boot for sandbox. Can we not expand them to
> > run on qemu* including ppce500?
>
> Perhaps. I didn't know sandbox was supposed to be buildable for other
> arches than x86ish. I just tried doing the naive thing,
>
> $ export ARCH=powerpc
> $ export CROSS_COMPILE=powerpc-linux-gnu-
> $ make sandbox_defconfig
> $ make -j8
> include/config_distro_bootcmd.h:335:3: error: #error "sandbox EFI
> support is only supported on ARM and x86"
>
> After trimming the .config to git rid of that, I get a million other
> warnings and errors, so that doesn't seem to be the right way.
Sorry, I meant the literal QEMU targets that we use.
> Can we please apply the patch to unbreak actual boards even if there's
> no regression test for it?
Yes, sorry it wasn't clear. I will pick this up soon, with a bunch of
other stuff.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201012/d1a1c679/attachment.sig>
next prev parent reply other threads:[~2020-10-12 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 14:10 verified boot changes since 2020.04 Rasmus Villemoes
2020-10-06 10:09 ` [PATCH 0/1] fix verified boot on BE hosts Rasmus Villemoes
2020-10-06 10:09 ` [PATCH 1/1] rsa: fix retrieving public exponent on big-endian systems Rasmus Villemoes
2020-10-06 22:02 ` Simon Glass
2020-10-06 22:17 ` Rasmus Villemoes
2020-10-09 13:08 ` Tom Rini
2020-10-12 7:04 ` Rasmus Villemoes
2020-10-12 11:41 ` Tom Rini [this message]
2020-10-12 16:54 ` Simon Glass
2020-10-13 14:07 ` Tom Rini
2020-10-12 3:34 ` verified boot changes since 2020.04 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=20201012114107.GV14816@bill-the-cat \
--to=trini@konsulko.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