From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org
Subject: [Qemu-devel] [PATCH 0/9] PPC: e500: Use u-boot as firmware
Date: Thu, 15 May 2014 18:32:41 +0200 [thread overview]
Message-ID: <1400171570-21284-1-git-send-email-agraf@suse.de> (raw)
Today we don't run any firmware on our e500 platform. You're either running
a Linux kernel directly through -kernel or you don't boot the VM at all.
This is bad for multiple reasons. The normal firmware on e500 based systems
is u-boot. Some OSes (IIRC FreeBSD) rely on u-boot for their 2nd stage boot
loader. Since that relies on interfaces u-boot provides we can't execute it
today.
The other case where we're falling short of expectations that I'm aware of
is network boot. With a firmware you can actually pxe boot a virtual machine.
This patch set implements all the pieces necessary to run u-boot as the
firmware for our e500 platforms: mpc8544ds and e500plat. It is based on upstream
u-boot code that implements a target specific for the simplified system QEMU
implements.
Due to popular demand the default -kernel booting has *not* been changed from
directly booting into the kernel. This is possible because we don't need to run
firmware to provide run time services.
However, whenever the user explicitly defines a -bios blob, we run it.
That means if you want to route a -kernel boot through u-boot you have to pass
in -bios pc-bios/u-boot.e500 -kernel uImage.
Please try out as many things as you're able to try.
Known missing bits:
- -boot doesn't get interpreted yet
- pflash is missing, so the environment is volatile
- no block drivers available (ata_piix is broken in u-boot and virtio-blk
is missing)
- KVM patches to support u-boot are probably going to hit 3.16
Alex
Alexander Graf (9):
PPC: Make all e500 CPUs SVR aware
PPC: Add definitions for GIVORs
PPC: Fix SPR access control of L1CFG0
PPC: Add L1CFG1 SPR emulation
PPC: Properly emulate L1CSR0 and L1CSR1
PPC: Add dcbtls emulation
PPC: e500: Expose kernel load address in dt
PPC: Add u-boot firmware for e500
PPC: e500: Move to u-boot as firmware
.gitmodules | 3 +
hw/ppc/e500.c | 134 ++++++++++++++++++++++++++++++--------------
pc-bios/README | 5 ++
pc-bios/u-boot.e500 | Bin 0 -> 264848 bytes
roms/u-boot | 1 +
target-ppc/cpu-models.c | 28 ++++-----
target-ppc/cpu.h | 19 +++++++
target-ppc/translate.c | 12 ++++
target-ppc/translate_init.c | 30 +++++++---
9 files changed, 168 insertions(+), 64 deletions(-)
create mode 100755 pc-bios/u-boot.e500
create mode 160000 roms/u-boot
--
1.8.1.4
next reply other threads:[~2014-05-15 16:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 16:32 Alexander Graf [this message]
2014-05-15 16:32 ` [Qemu-devel] [PATCH 1/9] PPC: Make all e500 CPUs SVR aware Alexander Graf
2014-05-15 16:32 ` [Qemu-devel] [PATCH 2/9] PPC: Add definitions for GIVORs Alexander Graf
2014-05-15 16:32 ` [Qemu-devel] [PATCH 3/9] PPC: Fix SPR access control of L1CFG0 Alexander Graf
2014-05-15 16:32 ` [Qemu-devel] [PATCH 4/9] PPC: Add L1CFG1 SPR emulation Alexander Graf
2014-05-15 16:32 ` [Qemu-devel] [PATCH 5/9] PPC: Properly emulate L1CSR0 and L1CSR1 Alexander Graf
2014-05-15 16:32 ` [Qemu-devel] [PATCH 6/9] PPC: Add dcbtls emulation Alexander Graf
2014-05-15 16:32 ` [Qemu-devel] [PATCH 7/9] PPC: e500: Expose kernel load address in dt Alexander Graf
2014-05-15 16:32 ` [Qemu-devel] [PATCH 8/9] PPC: Add u-boot firmware for e500 Alexander Graf
2014-05-16 6:06 ` Gerd Hoffmann
2014-05-16 11:09 ` Alexander Graf
2014-05-16 13:11 ` Gerd Hoffmann
2014-05-16 13:43 ` Alexander Graf
2014-05-16 14:08 ` Gerd Hoffmann
2014-05-16 14:21 ` Alexander Graf
2014-05-15 16:32 ` [Qemu-devel] [PATCH 9/9] PPC: e500: Move to u-boot as firmware Alexander Graf
2014-05-15 16:38 ` [Qemu-devel] [Qemu-ppc] [PATCH 0/9] PPC: e500: Use " Alexander Graf
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=1400171570-21284-1-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).