qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Alistair Francis" <Alistair.Francis@wdc.com>,
	"Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>,
	"Palmer Dabbelt" <palmerdabbelt@google.com>,
	"Sagar Karandikar" <sagark@eecs.berkeley.edu>,
	qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Subject: [PATCH v2 0/4] riscv: Upgrade OpenSBI to v0.6 and add 32-bit sifive_u bios image
Date: Mon, 24 Feb 2020 05:39:40 -0800	[thread overview]
Message-ID: <1582551584-20093-1-git-send-email-bmeng.cn@gmail.com> (raw)


This series advances the roms/opensbi submodule to the v0.6 release,
and builds and captures platform firmware binaries from that release.

A 32-bit sifive_u bios image has also been added, so that we can have
32-bit test coverage for SiFive specific drivers that cannot be done
with the 'virt' machine.

Two GitLab CI jobs are added to build the OpenSBI firmware binaries.

Changes in v2:
- new patch: Upgrade opensbi from v0.5 to v0.6
- Update the 32-bit sifive_u bios image to OpenSBI v0.6
- new patch: Add GitLab jobs to build OpenSBI firmware binaries

Bin Meng (4):
  roms: opensbi: Upgrade from v0.5 to v0.6
  roms: opensbi: Add 32-bit firmware image for sifive_u machine
  riscv: sifive_u: Update BIOS_FILENAME for 32-bit
  gitlab-ci.yml: Add jobs to build OpenSBI firmware binaries

 .gitlab-ci-opensbi.yml                       |  63 +++++++++++++++++++++++++++
 .gitlab-ci.d/opensbi/Dockerfile              |  33 ++++++++++++++
 .gitlab-ci.yml                               |   1 +
 Makefile                                     |   2 +-
 hw/riscv/sifive_u.c                          |   6 ++-
 pc-bios/opensbi-riscv32-sifive_u-fw_jump.bin | Bin 0 -> 49472 bytes
 pc-bios/opensbi-riscv32-virt-fw_jump.bin     | Bin 40984 -> 41280 bytes
 pc-bios/opensbi-riscv64-sifive_u-fw_jump.bin | Bin 49160 -> 53760 bytes
 pc-bios/opensbi-riscv64-virt-fw_jump.bin     | Bin 45064 -> 49664 bytes
 roms/Makefile                                |   7 +++
 roms/opensbi                                 |   2 +-
 11 files changed, 111 insertions(+), 3 deletions(-)
 create mode 100644 .gitlab-ci-opensbi.yml
 create mode 100644 .gitlab-ci.d/opensbi/Dockerfile
 create mode 100644 pc-bios/opensbi-riscv32-sifive_u-fw_jump.bin

-- 
2.7.4



             reply	other threads:[~2020-02-24 13:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 13:39 Bin Meng [this message]
2020-02-24 13:39 ` [PATCH v2 1/4] roms: opensbi: Upgrade from v0.5 to v0.6 Bin Meng
2020-02-24 16:58   ` Alistair Francis
2020-02-24 13:39 ` [PATCH v2 2/4] roms: opensbi: Add 32-bit firmware image for sifive_u machine Bin Meng
2020-02-24 18:33   ` Alistair Francis
2020-02-24 13:39 ` [PATCH v2 3/4] riscv: sifive_u: Update BIOS_FILENAME for 32-bit Bin Meng
2020-02-24 13:39 ` [PATCH v2 4/4] gitlab-ci.yml: Add jobs to build OpenSBI firmware binaries Bin Meng
2020-02-24 19:15   ` Alistair Francis
2020-03-06  0:02   ` Palmer Dabbelt
2020-03-01  2:47 ` [PATCH v2 0/4] riscv: Upgrade OpenSBI to v0.6 and add 32-bit sifive_u bios image Bin Meng
2020-03-06  0:06 ` Palmer Dabbelt

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=1582551584-20093-1-git-send-email-bmeng.cn@gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=Alistair.Francis@wdc.com \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=palmerdabbelt@google.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=sagark@eecs.berkeley.edu \
    /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;
as well as URLs for NNTP newsgroup(s).