qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Atish Patra <atish.patra@wdc.com>
To: qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org,
	Sagar Karandikar <sagark@eecs.berkeley.edu>,
	Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
	Atish Patra <atish.patra@wdc.com>,
	Alistair Francis <Alistair.Francis@wdc.com>,
	Alexander Richardson <Alexander.Richardson@cl.cam.ac.uk>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Bin Meng <bmeng.cn@gmail.com>
Subject: [PATCH v3 0/3] Add OpenSBI dynamic firmware support
Date: Thu, 25 Jun 2020 17:33:10 -0700	[thread overview]
Message-ID: <20200626003313.715355-1-atish.patra@wdc.com> (raw)

This series adds support OpenSBI dynamic firmware support to Qemu.
Qemu loader passes the information about the DT and next stage (i.e. kernel
or U-boot) via "a2" register. It allows the user to build bigger OS images
without worrying about overwriting DT. It also unifies the reset vector code
in rom and dt placement. Now, the DT is copied directly in DRAM instead of ROM.

The changes have been verified on following qemu machines.

64bit:
 - spike, sifive_u, virt
32bit:
 - virt

I have also verified fw_jump on all the above platforms to ensure that this
series doesn't break the existing setup.

Changes from v2->v3:
1. Removed redundant header includes.

Changes from v1->v2:
1. Rebased on top of latest upstream Qemu (with MSEL changes for sifive_u).
2. Improved the code organization

Atish Patra (3):
riscv: Unify Qemu's reset vector code path
RISC-V: Copy the fdt in dram instead of ROM
riscv: Add opensbi firmware dynamic support

hw/riscv/boot.c                 | 103 ++++++++++++++++++++++++++++++++
hw/riscv/sifive_u.c             |  46 ++++++++------
hw/riscv/spike.c                |  55 +++++------------
hw/riscv/virt.c                 |  54 +++++------------
include/hw/riscv/boot.h         |   8 +++
include/hw/riscv/boot_opensbi.h |  58 ++++++++++++++++++
6 files changed, 228 insertions(+), 96 deletions(-)
create mode 100644 include/hw/riscv/boot_opensbi.h

--
2.26.2



             reply	other threads:[~2020-06-26  0:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26  0:33 Atish Patra [this message]
2020-06-26  0:33 ` [PATCH v3 1/3] riscv: Unify Qemu's reset vector code path Atish Patra
2020-06-26 10:25   ` Bin Meng
2020-06-26  0:33 ` [PATCH v3 2/3] RISC-V: Copy the fdt in dram instead of ROM Atish Patra
2020-06-26 11:49   ` Bin Meng
2020-06-26 16:58     ` Atish Patra
2020-06-27  2:54       ` Bin Meng
2020-06-27  4:37         ` Atish Patra
2020-06-27  5:22           ` Alistair Francis
2020-06-27  9:55           ` Bin Meng
2020-06-27 10:03             ` Bin Meng
2020-06-29 18:50             ` Atish Patra
2020-06-30  1:04               ` Bin Meng
2020-06-26  0:33 ` [PATCH v3 3/3] riscv: Add opensbi firmware dynamic support Atish Patra
2020-06-26 12:17   ` Bin Meng
2020-06-26 18:48     ` Atish Patra

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=20200626003313.715355-1-atish.patra@wdc.com \
    --to=atish.patra@wdc.com \
    --cc=Alexander.Richardson@cl.cam.ac.uk \
    --cc=Alistair.Francis@wdc.com \
    --cc=bmeng.cn@gmail.com \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=palmer@dabbelt.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).