qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: David Gibson <david@gibson.dropbear.id.au>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: [for-6.0 PATCH 0/3] ppc: e500: Bump ppce500 u-boot to v2021.04
Date: Tue,  6 Apr 2021 16:15:10 +0800	[thread overview]
Message-ID: <20210406081513.1013372-1-bmeng.cn@gmail.com> (raw)

This series bumps the u-boot.e500 to v2021.04, which fixed a long
overdue broken pci issue caused by QEMU changes since Nov 2014.

While we are here, add a reST documentation for the ppce500 machine.

Please pull the full contents (binary) from https://github.com/lbmeng/qemu/
ppc branch.


Bin Meng (3):
  roms/Makefile: Update ppce500 u-boot build directory name
  roms/u-boot: Bump ppce500 u-boot to v2021.04 to fix broken pci support
  docs/system: ppc: Add documentation for ppce500 machine

 docs/system/ppc/ppce500.rst | 156 ++++++++++++++++++++++++++++++++++++
 docs/system/target-ppc.rst  |   1 +
 pc-bios/u-boot.e500         | Bin 349148 -> 406920 bytes
 roms/Makefile               |   8 +-
 roms/u-boot                 |   2 +-
 5 files changed, 162 insertions(+), 5 deletions(-)
 create mode 100644 docs/system/ppc/ppce500.rst

-- 
2.25.1



             reply	other threads:[~2021-04-06  8:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06  8:15 Bin Meng [this message]
2021-04-06  8:15 ` [for-6.0 PATCH 1/3] roms/Makefile: Update ppce500 u-boot build directory name Bin Meng
2021-04-06  8:15 ` [for-6.0 PATCH 2/3] roms/u-boot: Bump ppce500 u-boot to v2021.04 to fix broken pci support Bin Meng
2021-04-06  8:15 ` [for-6.0 PATCH 3/3] docs/system: ppc: Add documentation for ppce500 machine Bin Meng
2021-04-08  2:39 ` [for-6.0 PATCH 0/3] ppc: e500: Bump ppce500 u-boot to v2021.04 David Gibson
2021-04-08  3:07   ` Bin Meng
2021-04-08  3:14     ` David Gibson

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=20210406081513.1013372-1-bmeng.cn@gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --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).