From: Matthew Wilcox <matthew@wil.cx>
To: Arnd Bergmann <arnd@arndb.de>
Cc: schwidefsky@de.ibm.com, Andi Kleen <ak@suse.de>,
linux-arch@vger.kernel.org, geert@linux-m68k.org,
Keir.Fraser@cl.cam.ac.uk, chrisw@sous-sol.org, akpm@osdl.org
Subject: Re: [patch] s390 kconfig cleanup, 2nd version.
Date: Tue, 4 Jul 2006 12:09:53 -0600 [thread overview]
Message-ID: <20060704180953.GI1605@parisc-linux.org> (raw)
In-Reply-To: <200607041442.03913.arnd@arndb.de>
On Tue, Jul 04, 2006 at 02:42:03PM +0200, Arnd Bergmann wrote:
> On Tuesday 04 July 2006 01:35, Matthew Wilcox wrote:
> > We don't (yet) have a CONFIG_MMIO. ?If we were to have one, I would
> > expect it to be akin to SCSI_SYM53C8XX_MMIO, VIA_RHINE_MMIO,
> > SUNDANCE_MMIO and TULIP_MMIO. ?ie indicating a preference between PIO
> > and MMIO rather than indicating the availability of MMIO.
>
> Hmm, maybe my terminology wasn't so good, at least you misunderstood
> what I wanted to express. PIO is more or less a 386ism, so I tend to
> view that as a special case of MMIO. The point with s390 is that there
> is neither PIO nor MMIO, which really makes it impossible to use most
> of the device drivers, even if you could connect the hardware ;-).
I understood what you wanted; I was just explaining why it's a bad name.
CONFIG_STD_IO might be a good name. CONFIG_PCI_IO might be confusing.
next prev parent reply other threads:[~2006-07-04 18:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 12:26 [patch] s390 kconfig cleanup, 2nd version Martin Schwidefsky
2006-06-30 12:39 ` Geert Uytterhoeven
2006-06-30 12:54 ` Martin Schwidefsky
2006-06-30 12:44 ` Andi Kleen
2006-06-30 13:04 ` Martin Schwidefsky
2006-06-30 13:09 ` Andi Kleen
2006-06-30 13:20 ` Geert Uytterhoeven
2006-06-30 13:28 ` Martin Schwidefsky
2006-06-30 14:05 ` Andi Kleen
2006-06-30 14:15 ` Geert Uytterhoeven
2006-06-30 14:20 ` Martin Schwidefsky
2006-07-03 23:15 ` Arnd Bergmann
2006-07-03 23:35 ` Matthew Wilcox
2006-07-04 12:42 ` Arnd Bergmann
2006-07-04 13:08 ` Geert Uytterhoeven
2006-07-04 15:23 ` Arnd Bergmann
2006-07-04 18:09 ` Matthew Wilcox [this message]
2006-07-01 2:38 ` Paul Mackerras
2006-06-30 14:13 ` Kyle McMartin
2006-06-30 14:20 ` Andi Kleen
2006-06-30 17:41 ` Andrew Morton
2006-06-30 18:28 ` Andi Kleen
2006-07-03 9:10 ` Martin Schwidefsky
2006-07-03 9:20 ` Andrew Morton
2006-07-03 10:35 ` Martin Schwidefsky
2006-07-07 16:19 ` [Kconfig] add disable command (was Re: [patch] s390 kconfig cleanup, 2nd version) Martin Schwidefsky
2006-07-07 19:27 ` Andrew Morton
2006-07-07 16:19 ` [Kconfig] use " Martin Schwidefsky
2006-07-07 19:48 ` Matthew Wilcox
2006-07-08 23:42 ` Ralf Baechle
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=20060704180953.GI1605@parisc-linux.org \
--to=matthew@wil.cx \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=chrisw@sous-sol.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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.