All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: acpi-devel@lists.sourceforge.net, Adam Litke <agl@us.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [ACPI] 2.6.14-rc4 ACPI/PCI compile problem
Date: Wed, 12 Oct 2005 12:00:50 -0600	[thread overview]
Message-ID: <20051012180050.GC5103@parisc-linux.org> (raw)
In-Reply-To: <200510111717.01887.bjorn.helgaas@hp.com>

On Tue, Oct 11, 2005 at 05:17:01PM -0600, Bjorn Helgaas wrote:
> Please try the following patch and confirm whether it works.
> 
> [i386 kbuild] Don't clobber pci-y when X86_VISWS or X86_NUMAQ
> 
> Previously, enabling CONFIG_X86_VISWS or CONFIG_X86_NUMAQ
> clobbered any previous contents of pci-y, because they used
> ":=" instead of "+=".

This isn't correct.  We want to get rid of some of the current contents
of pci-y when NUMAQ or VISWS are enabled.  I'm not quite sure what the
right fix is here.  Maybe something like ...

--- arch/i386/pci/Makefile      14 Sep 2005 12:54:20 -0000      1.3
+++ arch/i386/pci/Makefile      12 Oct 2005 17:51:19 -0000
@@ -4,11 +4,11 @@ obj-$(CONFIG_PCI_BIOS)                += pcbios.o
 obj-$(CONFIG_PCI_MMCONFIG)     += mmconfig.o
 obj-$(CONFIG_PCI_DIRECT)       += direct.o
 
-pci-y                          := fixup.o
-pci-$(CONFIG_ACPI)             += acpi.o
-pci-y                          += legacy.o irq.o
+acpi-$(CONFIG_ACPI)            := acpi.o
+
+pci-y                          := fixup.o $(acpi-y) legacy.o irq.o
 
 pci-$(CONFIG_X86_VISWS)                := visws.o fixup.o
-pci-$(CONFIG_X86_NUMAQ)                := numa.o irq.o
+pci-$(CONFIG_X86_NUMAQ)                := numa.o $(acpi-y) irq.o
 
 obj-y                          += $(pci-y) common.o

This mess really needs some more eyes on it.  For example, should fixups.o
really be enabled on visws but disabled on numaq?  I suspect both want
legacy.o disabled.  Does it make sense to enable ACPI on a NUMAQ system?
I don't know enough about them.

And it /really/ needs some commentary.  Here's my first cut at it, based
on my memories of editing it several years ago:

# A little more complex than most Makefiles.
# Neither the VISWS nor the NUMAQ configs want to see legacy.o compiled in.
# VISWS doesn't have ACPI to worry about, but NUMAQ might
# Order is important -- don't rearrange the order of files here.

Help most gratefully received from people who really understand these boxes!

      parent reply	other threads:[~2005-10-12 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11 22:28 2.6.14-rc4 ACPI/PCI compile problem Adam Litke
     [not found] ` <1129069727.27663.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-10-11 23:17   ` Bjorn Helgaas
2005-10-11 23:17     ` [ACPI] " Bjorn Helgaas
2005-10-12 14:34     ` Adam Litke
2005-10-12 18:00     ` Matthew Wilcox [this message]

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=20051012180050.GC5103@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=agl@us.ibm.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-kernel@vger.kernel.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.