linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: [RFC/PATCH 2/4] Allow for non-Intel MSI implementations
Date: Fri, 18 Aug 2006 18:13:29 +1000	[thread overview]
Message-ID: <20060818081330.9ADC867B55@ozlabs.org> (raw)

From: Jake Moilanen <moilanen@austin.ibm.com>

This allows an architecture to provide its own MSI implementation
instead of msi.c and msi-apic.c.  We will need this on IBM System-p
machines where the hypervisor controls the assignment and setup of
MSIs.  A following patch will provide an MSI implementation for these
machines.

Signed-off-by: Jake Moilanen <moilanen@austin.ibm.com>
---

 drivers/pci/Makefile |    8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

Index: git/drivers/pci/Makefile
===================================================================
--- git.orig/drivers/pci/Makefile
+++ git/drivers/pci/Makefile
@@ -27,9 +27,11 @@ obj-$(CONFIG_PPC64) += setup-bus.o
 obj-$(CONFIG_MIPS) += setup-bus.o setup-irq.o
 obj-$(CONFIG_X86_VISWS) += setup-irq.o
 
-msiobj-y := msi.o msi-apic.o
-msiobj-$(CONFIG_IA64_GENERIC) += msi-altix.o
-msiobj-$(CONFIG_IA64_SGI_SN2) += msi-altix.o
+msiobj-$(CONFIG_X86) := msi.o msi-apic.o
+msiobj-$(CONFIG_IA64) := msi.o msi-apic.o
+msiobj-$(CONFIG_IA64_GENERIC) := msi-altix.o
+msiobj-$(CONFIG_IA64_SGI_SN2) := msi-altix.o
+
 obj-$(CONFIG_PCI_MSI) += $(msiobj-y)
 
 #

             reply	other threads:[~2006-08-18  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18  8:13 Michael Ellerman [this message]
2006-08-18 13:03 ` [RFC/PATCH 2/4] Allow for non-Intel MSI implementations Segher Boessenkool

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=20060818081330.9ADC867B55@ozlabs.org \
    --to=michael@ellerman.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).