From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Adrian Bunk <bunk@fs.tum.de>,
Christoph Hellwig <hch@infradead.org>,
wli@holomorphy.com, "David S. Miller" <davem@redhat.com>,
schwidefsky@de.ibm.com, linux390@de.ibm.com,
sparclinux@vger.kernel.org,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: architectures with their own "config PCMCIA"
Date: Sat, 7 Aug 2004 23:41:17 +0200 [thread overview]
Message-ID: <200408072341.17721.arnd@arndb.de> (raw)
In-Reply-To: <Pine.GSO.4.58.0408072234290.23642@waterleaf.sonytel.be>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Samstag, 7. August 2004 22:36, Geert Uytterhoeven wrote:
> I've been `fixing up' many of them lately. Please give it a try.
> Anyway, probably all additional clean ups you do for s390 are useful for m68k
> as well ;-)
Yes, most devices drivers that rely on ISA or PCI attachment now
appear to be gone.
However, I just tried and found that out of the 23 driver submenus, only
"Generic Driver Options", "Block devices", "SCSI device support",
"Multi-device support", "Networking support" and "Character devices"
make any sense at all. All others depend on some hardware that has
never been attached to an s390 box.
We could of course build some subsystems like MTD, ISDN or FB, but
there is still little point without any low-level drivers.
Arnd <><
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-07 21:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 17:01 architectures with their own "config PCMCIA" Adrian Bunk
2004-08-07 17:10 ` Christoph Hellwig
2004-08-07 17:25 ` Adrian Bunk
2004-08-07 18:12 ` Arnd Bergmann
2004-08-07 20:36 ` Geert Uytterhoeven
2004-08-07 21:41 ` Arnd Bergmann [this message]
2004-08-11 16:45 ` Christoph Hellwig
2004-08-11 20:17 ` Adrian Bunk
2004-08-11 21:40 ` Sam Ravnborg
2004-08-12 0:10 ` Adrian Bunk
2004-08-12 8:59 ` Roman Zippel
2004-08-14 20:47 ` Adrian Bunk
2004-08-15 17:32 ` Roman Zippel
2004-08-15 19:37 ` Geert Uytterhoeven
2004-08-15 20:15 ` Adrian Bunk
2004-08-15 23:01 ` Roman Zippel
2004-08-15 23:22 ` Adrian Bunk
2004-08-11 21:45 ` Roman Zippel
2004-08-12 0:18 ` Adrian Bunk
2004-08-12 2:19 ` Randy.Dunlap
2004-08-11 16:54 ` William Lee Irwin III
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=200408072341.17721.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=bunk@fs.tum.de \
--cc=davem@redhat.com \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux390@de.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=sparclinux@vger.kernel.org \
--cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox