From: Brad Boyer <flar@allandria.com>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
uClinux development list <uclinux-dev@uclinux.org>,
linux-m68k@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [uClinux-dev] [PATCH] m68k: reorganize Kconfig options to improve mmu/non-mmu selections
Date: Thu, 11 Aug 2011 21:30:22 -0700 [thread overview]
Message-ID: <20110812043022.GB4940@cynthia.pants.nu> (raw)
In-Reply-To: <4E437A0B.3030201@snapgear.com>
On Thu, Aug 11, 2011 at 04:43:23PM +1000, Greg Ungerer wrote:
> >Do you really need EISA, MCA and PCMIA? They have no promt thus cannot be selected by the user.
>
> Yes, your right, they don't look like than can be selected at all.
> None of the default configs seem to reference them either.
> Geert: do you know why these options might still be around?
>
It still hasn't been cleaned up enough to go in, but somebody posted
a trex driver which would need PCMCIA. It was a driver for the card
slots in the Macintosh PowerBook 190.
In theory some other m68k systems have PCMCIA slots that could be
supported as well. I'm sure they're almost as broken and non-standards
compliant as what Apple did.
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2011-08-12 4:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 5:10 [PATCH] m68k: reorganize Kconfig options to improve mmu/non-mmu selections gerg
2011-08-11 6:15 ` [uClinux-dev] " Sam Ravnborg
2011-08-11 6:43 ` Greg Ungerer
2011-08-12 4:30 ` Brad Boyer [this message]
2011-08-15 0:53 ` Greg Ungerer
2011-08-15 15:49 ` Lennart Sorensen
2011-08-15 22:17 ` [uClinux-dev] " Brad Boyer
2011-08-13 9:46 ` Geert Uytterhoeven
2011-08-15 0:54 ` Greg Ungerer
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=20110812043022.GB4940@cynthia.pants.nu \
--to=flar@allandria.com \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=uclinux-dev@uclinux.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