From: Arnd Bergmann <arnd@arndb.de>
To: schwidefsky@de.ibm.com
Cc: Andi Kleen <ak@suse.de>,
linux-arch@vger.kernel.org, geert@linux-m68k.org,
Keir.Fraser@cl.cam.ac.uk, chrisw@sous-sol.org, matthew@wil.cx,
akpm@osdl.org
Subject: Re: [patch] s390 kconfig cleanup, 2nd version.
Date: Tue, 4 Jul 2006 01:15:16 +0200 [thread overview]
Message-ID: <200607040115.18194.arnd@arndb.de> (raw)
In-Reply-To: <1151677236.29984.11.camel@localhost>
On Friday 30 June 2006 16:20, Martin Schwidefsky wrote:
> There are still a few more config options:
> IPMI
> SERIAL_NONSTANDARD
> SCSI_SATA
>
> and numerous menues:
> "TPM devices" - PC_STYLE_HARDWARE
> "Hardware monitoring support" - PC_STYLE_HARDWARE
> "InfiniBand support" - don't think this is pc style hardware
> "ISDN subsystem" - PC_STYLE_HARDWARE
> "LED devices" - PC_STYLE_HARDWARE
> "Multimedia devices" - PC_STYLE_HARDWARE
> "MMC/SD Card support" - PC_STYLE_HARDWARE
> "PHY device support" - PC_STYLE_HARDWARE
> "Serial drivers" - PC_STYLE_HARDWARE
> "SPI support" - PC_STYLE_HARDWARE
> "Telephony Support" - PC_STYLE_HARDWARE
> "USB support" - PC_STYLE_HARDWARE
> "Graphics support" - PC_STYLE_HARDWARE
> "Dallas's 1-wire bus" - PC_STYLE_HARDWARE
> "Amateur Radio support" - PC_STYLE_HARDWARE
> "Bluetooth subsystem support" - PC_STYLE_HARDWARE
> "IrDA (infrared) subsystem support" - PC_STYLE_HARDWARE
> "EDAC - error detection and reporting" - PC_STYLE_HARDWARE
> "Sound" - PC_STYLE_HARDWARE
I would assume that all of these depend on memory mapped I/O
access. So they might be more correctly depend on CONFIG_MMIO.
> VT
> "Input device support" - ??
> "Misc devices" - PC_STYLE_HARDWARE
> "Memory Technology Devices (MTD)" - PC_STYLE_HARDWARE
> "Wireless LAN (non-hamradio)" - PC_STYLE_HARDWARE
> "Real Time Clock" - PC_STYLE_HARDWARE
For these, it's not so clear, so maybe just let the HW drivers
depend on CONFIG_MMIO, but not the architecture in dependant
parts.
Arnd <><
next prev parent reply other threads:[~2006-07-03 23:15 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 [this message]
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
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=200607040115.18194.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=matthew@wil.cx \
--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.