qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Ben Collins <bcollins@ubuntu.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	PowerPC <qemu-ppc@nongnu.org>, qemu-devel <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] e500-pci: Factor into distinct mpc8540 and p4080 PCI Hosts
Date: Fri, 01 Jun 2012 17:17:17 +0200	[thread overview]
Message-ID: <4FC8DCFD.5020106@suse.de> (raw)
In-Reply-To: <503663EE-6BC1-4C3A-97B9-06737AAD8266@ubuntu.com>

Am 31.05.2012 01:25, schrieb Ben Collins:
> In order to provide a closer virtualization, factor out e500-pci into seperate
> PCI hosts, namely fsl,mpc8540-pci and fsl,p4080-pcie (to match the device-tree
> node naming).
> 
> Make use of the mpc8540 variant (basically a NOP) for ppce500_mpc8544 machine
> type. The p4080-pcie variant can be used later for a P4080DS specific machine
> description.
> 
> The major differences between the two are the host-bridge PCI device ID and the
> difference in starting slot number. Eventually I'd like to get the p4080 variant
> to support any valid slot number, and actually move the bus behind the host
> bridge as is done in the physical hardware.
> 
> Signed-off-by: Ben Collins <bcollins@ubuntu.com>

Please always cc qemu-devel on patches and the respective maintainers,
here ppc and pci.

Thanks,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

       reply	other threads:[~2012-06-01 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <503663EE-6BC1-4C3A-97B9-06737AAD8266@ubuntu.com>
2012-06-01 15:17 ` Andreas Färber [this message]
     [not found] ` <4FC7B66B.1020706@freescale.com>
2012-06-03 11:10   ` [Qemu-devel] [Qemu-ppc] [PATCH] e500-pci: Factor into distinct mpc8540 and p4080 PCI Hosts Ben Collins
2012-06-03 11:21     ` 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=4FC8DCFD.5020106@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=bcollins@ubuntu.com \
    --cc=mst@redhat.com \
    --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).