mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] X86_NUMAQ build fix
Date: Fri, 21 Apr 2006 11:19:18 -0700	[thread overview]
Message-ID: <1145643558.3373.34.camel@localhost.localdomain> (raw)
In-Reply-To: <87irp2x69s.fsf@duaron.myhome.or.jp>

On Sat, 2006-04-22 at 01:06 +0900, OGAWA Hirofumi wrote:
> This patch fixes the build breakage of X86_NUMAQ. And this declares
> xquad_portio on only X86_NUMAQ.

What bug does this patch fix?  What is your .config?  I'm not having any
compile problems on my NUMAQ lately.

>  obj-$(CONFIG_PCI_DIRECT)       += direct.o
>  
>  pci-y                          := fixup.o
> -pci-$(CONFIG_ACPI)             += acpi.o
>  pci-y                          += legacy.o irq.o
>  
>  pci-$(CONFIG_X86_VISWS)                := visws.o fixup.o
>  pci-$(CONFIG_X86_NUMAQ)                := numa.o irq.o
>  
> +pci-$(CONFIG_ACPI)             += acpi.o

Am I reading this wrong, or does this just move the option down a bit?
Did you need to change the link order?  Why?

> +++ linux-2.6-hirofumi/arch/i386/boot/compressed/misc.c 2006-04-22 00:54:29.000000000 +0900
> @@ -122,7 +122,9 @@ static int vidport;
>  static int lines, cols;
>  
>  #ifdef CONFIG_X86_NUMAQ
> -static void * xquad_portio = NULL;
> +/* hack to avoid using xquad_portio=NULL */
> +#undef outb_p
> +#define outb_p         outb_local_p
>  #endif

It's really weird, but I'd hope that there was a reason for having two
xquad_portio.  Are you sure that this has no other consequences?

That said, it does boot on my 16-way NUMAQ, but I still have no real
idea what problem this is solving or what it is actually doing ;)

-- Dave


  reply	other threads:[~2006-04-21 21:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 16:06 OGAWA Hirofumi
2006-04-21 18:19 ` Dave Hansen [this message]
2006-04-21 18:50   ` OGAWA Hirofumi
2006-04-21 18:59     ` Dave Hansen
2006-04-21 19:31       ` OGAWA Hirofumi
2006-04-21 19:36         ` Dave Hansen
2006-04-21 20:03           ` OGAWA Hirofumi

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=1145643558.3373.34.camel@localhost.localdomain \
    --to=haveblue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®