From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Bin Meng <bmeng.cn@gmail.com>,
Stefan Reinauer <reinauer@chromium.org>,
Martin Roth <martinroth@chromium.org>,
Alper Nebi Yasak <alpernebiyasak@gmail.com>,
Daniel Schwierzeck <daniel.schwierzeck@gmail.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Kristian Amlie <kristian.amlie@northern.tech>
Subject: Re: [PATCH v4] gitlab/azure: x86: Add a coreboot test
Date: Sat, 29 Jan 2022 13:49:27 -0500 [thread overview]
Message-ID: <20220129184927.GZ7515@bill-the-cat> (raw)
In-Reply-To: <20220121102254.v4.1.I8f451123c2dd44a736c22995284b926cfdfe5ccd@changeid>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
On Fri, Jan 21, 2022 at 10:23:01AM -0700, Simon Glass wrote:
> Coreboot supports U-Boot as a payload and this recently got a bit of a
> facelist. Add a test for this.
>
> For now this uses a binary build of coreboot (v4.15). Future work could
> potentially build it from source, but we need to figure out the
> toolchain problems first, since coreboot uses its own toolchain. It
> turns out that this is tricky, because coreboot fails to build with a
> vanilla gcc.
>
> This needs some changes to the hooks scripts as well. An example build
> is at https://source.denx.de/u-boot/custodians/u-boot-dm/-/jobs/359687
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> Reviewed-by: Tom Rini <trini@konsulko.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-01-29 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 17:23 [PATCH v4] gitlab/azure: x86: Add a coreboot test Simon Glass
2022-01-21 18:10 ` Tom Rini
2022-01-29 18:49 ` Tom Rini [this message]
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=20220129184927.GZ7515@bill-the-cat \
--to=trini@konsulko.com \
--cc=alpernebiyasak@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=daniel.schwierzeck@gmail.com \
--cc=kristian.amlie@northern.tech \
--cc=martinroth@chromium.org \
--cc=reinauer@chromium.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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