qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <alistair.francis@wdc.com>
To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: alistair23@gmail.com, palmer@sifive.com, alistair.francis@wdc.com
Subject: [PATCH v2 0/7]  RISC-V: Add more machine memory
Date: Thu, 26 Sep 2019 17:44:17 -0700	[thread overview]
Message-ID: <cover.1569545046.git.alistair.francis@wdc.com> (raw)


This series aims to improve the use of QEMU for developing boot code. It
does a few things:

 - sifive_u machine:
   - Adds a chunk of memory in the Flash area. This allows boot loaders
   to use this memory. I can't find details on the QSPI flash used on
   the real board, so this is the best bet at the moment.
   - Adds a chunk of memory in the L2-LIM area. This is actualy the L2
   cache and should shrink as the L2 cache is enalbed. Unfortunatley I
   don't see a nice way to shrink this memory.
   - Adds a property that allows users to specify if QEMU should jump to
   flash or DRAM after the ROM code.

 - virt machine:
   - Add the pflash_cfi01 flash device. This is based on the ARM virt
   board implementation
   - Adjusts QEMU to jump to the flash if a user has speciefied any
   pflash.

Both machines have been tested with oreboot, but this should also help
the coreboot developers.

v2:
 - Address comments
 - Fixup addresses
 - Don't use macro for machine definition of RISC-V virt machine



Alistair Francis (7):
  riscv/sifive_u: Add L2-LIM cache memory
  riscv/sifive_u: Add QSPI memory region
  riscv/sifive_u: Manually define the machine
  riscv/sifive_u: Add the start-in-flash property
  riscv/virt: Manually define the machine
  riscv/virt: Add the PFlash CFI01 device
  riscv/virt: Jump to pflash if specified

 hw/riscv/Kconfig            |   1 +
 hw/riscv/sifive_u.c         |  95 +++++++++++++++++++++++----
 hw/riscv/virt.c             | 127 ++++++++++++++++++++++++++++++++++--
 include/hw/riscv/sifive_u.h |  11 +++-
 include/hw/riscv/virt.h     |  10 ++-
 5 files changed, 222 insertions(+), 22 deletions(-)

-- 
2.23.0



             reply	other threads:[~2019-09-27  0:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27  0:44 Alistair Francis [this message]
2019-09-27  0:44 ` [PATCH v2 1/7] riscv/sifive_u: Add L2-LIM cache memory Alistair Francis
2019-09-27  7:56   ` Bin Meng
2019-09-27 21:47     ` Alistair Francis
2019-09-27  0:44 ` [PATCH v2 2/7] riscv/sifive_u: Add QSPI memory region Alistair Francis
2019-09-27  7:56   ` Bin Meng
2019-09-27  0:44 ` [PATCH v2 3/7] riscv/sifive_u: Manually define the machine Alistair Francis
2019-09-27  7:56   ` Bin Meng
2019-09-27  0:44 ` [PATCH v2 4/7] riscv/sifive_u: Add the start-in-flash property Alistair Francis
2019-09-27  7:57   ` Bin Meng
2019-09-30 18:04     ` Alistair Francis
2019-10-08 20:12       ` Palmer Dabbelt
2019-10-08 20:33         ` Alistair Francis
2019-10-08 20:12   ` Palmer Dabbelt
2019-09-27  0:44 ` [PATCH v2 5/7] riscv/virt: Manually define the machine Alistair Francis
2019-09-27  7:57   ` Bin Meng
2019-09-27  0:44 ` [PATCH v2 6/7] riscv/virt: Add the PFlash CFI01 device Alistair Francis
2019-09-27  7:57   ` Bin Meng
2019-09-27  0:44 ` [PATCH v2 7/7] riscv/virt: Jump to pflash if specified Alistair Francis
2019-09-27  7:57   ` Bin Meng

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=cover.1569545046.git.alistair.francis@wdc.com \
    --to=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=palmer@sifive.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    /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).