From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, Alexander Graf <agraf@suse.de>
Subject: [PATCH v2 0/3] powerpc/fsl: PCI refactoring and QEMU paravirt platform
Date: Tue, 10 Jul 2012 19:26:46 -0500 [thread overview]
Message-ID: <1341966409-22660-1-git-send-email-scottwood@freescale.com> (raw)
The QEMU stuff is related to the PCI refactoring because currently
we have a hard time selecting a primary bus under QEMU, and also because
the generic qemu e500 platform wants a full list of FSL PCI compatibles
to check.
Patchset rebased on Kumar's next branch.
Scott Wood (3):
powerpc/fsl-pci: get PCI init out of board files
powerpc/e500: add paravirt QEMU platform
powerpc/mpc85xx_ds: convert to unified PCI init
arch/powerpc/platforms/85xx/Kconfig | 16 +++++
arch/powerpc/platforms/85xx/Makefile | 1 +
arch/powerpc/platforms/85xx/mpc85xx_ds.c | 97 +++++++++---------------------
arch/powerpc/platforms/85xx/qemu_e500.c | 72 ++++++++++++++++++++++
arch/powerpc/platforms/Kconfig.cputype | 4 +
arch/powerpc/sysdev/fsl_pci.c | 71 +++++++++++++++++++++-
arch/powerpc/sysdev/fsl_pci.h | 8 +++
7 files changed, 200 insertions(+), 69 deletions(-)
create mode 100644 arch/powerpc/platforms/85xx/qemu_e500.c
--
1.7.5.4
next reply other threads:[~2012-07-11 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 0:26 Scott Wood [this message]
2012-07-11 0:26 ` [PATCH v2 1/3] powerpc/fsl-pci: get PCI init out of board files Scott Wood
2012-07-11 12:58 ` Kumar Gala
2012-07-11 0:26 ` [PATCH v2 2/3] powerpc/e500: add paravirt QEMU platform Scott Wood
2012-07-11 12:57 ` Kumar Gala
2012-07-11 0:26 ` [PATCH v2 3/3] powerpc/mpc85xx_ds: convert to unified PCI init Scott Wood
2012-07-11 12:57 ` Kumar Gala
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=1341966409-22660-1-git-send-email-scottwood@freescale.com \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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).