From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:34469) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TLeW2-0005Up-DB for qemu-devel@nongnu.org; Tue, 09 Oct 2012 14:26:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TLeW0-00031d-Jx for qemu-devel@nongnu.org; Tue, 09 Oct 2012 14:26:50 -0400 From: Bharat Bhushan Date: Tue, 9 Oct 2012 23:49:08 +0530 Message-ID: <1349806750-17652-1-git-send-email-Bharat.Bhushan@freescale.com> MIME-Version: 1.0 Content-Type: text/plain Subject: [Qemu-devel] [PATCH 0/2 v2] e500: creating CCSR region and registering bar0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, agraf@suse.de, afaerber@suse.de Cc: Bharat Bhushan From: Bharat Bhushan 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