All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bharat Bhushan <r65777@freescale.com>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, agraf@suse.de,
	afaerber@suse.de
Cc: Bharat Bhushan <bharat.bhushan@freescale.com>
Subject: [Qemu-devel] [PATCH 0/2 v2] e500: creating CCSR region and registering bar0
Date: Tue, 9 Oct 2012 23:49:08 +0530	[thread overview]
Message-ID: <1349806750-17652-1-git-send-email-Bharat.Bhushan@freescale.com> (raw)

From: Bharat Bhushan <bharat.bhushan@freescale.com>

The CCSR memory region is exported to pci device. The MSI interrupt
generation is the main reason to export the CCSR region to PCI device.
This put the requirement to move mpic under CCSR region, but logically
all devices should be under CCSR.
  
So First patch creates the CCSR region and places all emulated devices
under ccsr region.
 
PCI Root complex have TYPE-1 configuration header while PCI endpoint
have type-0 configuration header. The type-1 configuration header have
a BAR (BAR0). In Freescale PCI controller BAR0 is used for mapping pci
address space to CCSR address space.

The second patch maps the BAR0 to ccsr region.

Bharat Bhushan (2):
  e500: Adding CCSR memory region
  Adding BAR0 for e500 PCI controller

 hw/ppc/e500-ccsr.h |   17 +++++++++
 hw/ppc/e500.c      |  100 ++++++++++++++++++++++++++++++++++++++++------------
 hw/ppce500_pci.c   |   30 +++++++++++++++-
 3 files changed, 123 insertions(+), 24 deletions(-)
 create mode 100644 hw/ppc/e500-ccsr.h

             reply	other threads:[~2012-10-09 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 18:19 Bharat Bhushan [this message]
2012-10-09 18:19 ` [Qemu-devel] [PATCH 1/2 v2] e500: Adding CCSR memory region Bharat Bhushan
2012-10-09 18:47   ` Andreas Färber
2012-10-09 18:19 ` [Qemu-devel] [PATCH 2/2 v2] Adding BAR0 for e500 PCI controller Bharat Bhushan
2012-10-09 18:45   ` Andreas Färber
2012-10-09 22:37   ` Scott Wood
2012-10-10  1:22     ` Bhushan Bharat-R65777

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=1349806750-17652-1-git-send-email-Bharat.Bhushan@freescale.com \
    --to=r65777@freescale.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=bharat.bhushan@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.