public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Dobson <colpatch@us.ibm.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NUMA-Q xquad_portio declaration
Date: Thu, 15 Aug 2002 15:48:48 -0700	[thread overview]
Message-ID: <3D5C2FD0.6060003@us.ibm.com> (raw)
In-Reply-To: 1253454051.1028629435@[10.10.2.3]

[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

Alan & Martin,
	How does this look?  I've combined what Martin suggested with what Alan has in 
his tree...  Comments?

-Matt

Martin J. Bligh wrote:
>>>The STANDALONE thing? I'm not convinced that's really any cleaner,
>>>it makes even more of a mess of io.h than there was already (though
>>>we could consider that a lost cause ;-)). 
>>>
>>>What's your objection to just throwing in a defn of xquad_portio?
>>>A preference for burying the messy stuff in header files? Seems to
>>>me that as you have to define STANDALONE now, the point is moot.
>>
>>Because you are assuming there will be -one- kind of wackomatic PC
>>system - IBM's. The chances are there will be more than one as other
>>vendors like HP, Compaq and Dell begin shipping stuff. Having
>>__STANDALONE__ works for all the cases instead of exporting xquad this
>>hpmagic that and compaq the other in an ever growing cess pit
> 
> 
> OK, fair enough. Would a simpler approach to what you've done be
> to do in io.h something like:
> 
> #ifdef CONFIG_MULTIQUAD
>  #ifdef STANDALONE
>   #define xquad_portio 0
>  #else
>   extern void *xquad_portio;    /* Where the IO area was mapped */
>  #endif
> #endif /* CONFIG_MULTIQUAD */
> 
> Or something along these lines ... ? Would make the changeset
> somewhat smaller. Seems to work from 30 seconds thought, but 
> haven't tried it (yet).
> 
> M.
> 
> 


[-- Attachment #2: xquad_fixup-2531.patch --]
[-- Type: text/plain, Size: 1252 bytes --]

diff -Nur linux-2.5.31-vanilla/arch/i386/boot/compressed/misc.c linux-2.5.31-xquad/arch/i386/boot/compressed/misc.c
--- linux-2.5.31-vanilla/arch/i386/boot/compressed/misc.c	Sat Aug 10 18:41:40 2002
+++ linux-2.5.31-xquad/arch/i386/boot/compressed/misc.c	Thu Aug 15 14:28:33 2002
@@ -9,6 +9,8 @@
  * High loaded stuff by Hans Lermen & Werner Almesberger, Feb. 1996
  */
 
+#define STANDALONE
+
 #include <linux/linkage.h>
 #include <linux/vmalloc.h>
 #include <linux/tty.h>
@@ -120,10 +122,6 @@
 static int vidport;
 static int lines, cols;
 
-#ifdef CONFIG_MULTIQUAD
-static void * const xquad_portio = NULL;
-#endif
-
 #include "../../../../lib/inflate.c"
 
 static void *malloc(int size)
diff -Nur linux-2.5.31-vanilla/include/asm-i386/io.h linux-2.5.31-xquad/include/asm-i386/io.h
--- linux-2.5.31-vanilla/include/asm-i386/io.h	Sat Aug 10 18:41:28 2002
+++ linux-2.5.31-xquad/include/asm-i386/io.h	Thu Aug 15 15:17:31 2002
@@ -303,7 +303,11 @@
 #endif
 
 #ifdef CONFIG_MULTIQUAD
-extern void *xquad_portio;    /* Where the IO area was mapped */
+ #ifdef STANDALONE
+  #define xquad_portio 0
+ #else /* !STANDALONE */
+  extern void *xquad_portio;    /* Where the IO area was mapped */
+ #endif /* STANDALONE */
 #endif /* CONFIG_MULTIQUAD */
 
 /*

      reply	other threads:[~2002-08-15 22:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 23:53 [PATCH] NUMA-Q xquad_portio declaration Martin J. Bligh
2002-08-06 14:04 ` Alan Cox
2002-08-06 13:47   ` Martin J. Bligh
2002-08-06 16:05     ` Alan Cox
2002-08-06 15:06       ` Martin J. Bligh
2002-08-06 17:54         ` Alan Cox
2002-08-06 17:23           ` Martin J. Bligh
2002-08-15 22:48             ` Matthew Dobson [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=3D5C2FD0.6060003@us.ibm.com \
    --to=colpatch@us.ibm.com \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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