From: Dan Malek <dan@mvista.com>
To: mgreer@mvista.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: If not CONFIG_ALL_PPC, you're broken
Date: Tue, 17 Oct 2000 00:57:39 -0400 [thread overview]
Message-ID: <39EBDC43.3F7E57B8@mvista.com> (raw)
In-Reply-To: 39EB8A67.E2F9C023@mvista.com
"Mark A. Greer" wrote:
>
> I've haven't been paying attention to this but it seems as though any
> platform that doesn't fit in CONFIG_ALL_PPC doesn't build anymore.
We don't even need CONFIG_ALL_PPC anymore. We can just rename
arch/ppc to arch/powermac_workstation, as that is all that works
right now. It sucks to have to build a 2 Mbyte kernel with USB,
keyboard, mouse, and tons of other stuff just to get a kernel that
will link when all you want is a serial and Ethernet port......and
then hack init functions that you didn't want anyway so they don't
try to touch hardware you don't have.
> ........ Yes, I know, I am lazy
> and should contribute more. Anyway, I think we all need to pay closer
> attention to the changes that are being put in, including me.
Well, putting in the time is only part of it. I am trying to support
about a dozen different PowerPC boards, none of which look like a
PowerMac. By the time I test a kernel across all of these platforms
and check in a few changes I am completely out of date and have to
start over.
> What's the best way to get the other platforms working again?
Fortunately, it looks like some people (Matt, Troy, others) have pushed
a few PReP and CHRP updates, and Paul has a CHRP workstation for testing.
Maybe when the PMac stuff slows down, we can catch up. Unfortunately,
we still have to build huge kernels with lots of stuff we don't need,
and I don't know how to fix that (well, I do but I don't think it
is likely to happen :-).
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-17 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-16 23:08 If not CONFIG_ALL_PPC, you're broken Mark A. Greer
2000-10-17 4:57 ` Dan Malek [this message]
2000-10-17 11:17 ` Matt Porter
2000-10-17 15:28 ` Dan Malek
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=39EBDC43.3F7E57B8@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mgreer@mvista.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;
as well as URLs for NNTP newsgroup(s).