From: Cort Dougan <cort@fsmlabs.com>
To: Dan Malek <dan@netx4.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: feature_init
Date: Mon, 24 Apr 2000 12:54:23 -0600 [thread overview]
Message-ID: <20000424125423.Z1544@medea.fsmlabs.com> (raw)
In-Reply-To: <3903A49C.B0BB90EB@embeddededge.com>; from Dan Malek on Sun, Apr 23, 2000 at 09:34:20PM -0400
CONFIG_PREP, CONFIG_CHRP and CONFIG_PMAC are gone in 2.3. They've been
replaced with CONFIG_ALL_PPC. It's a bad name, I know, but it was already
in place. In 2.5 (perhaps 2.4 after testing) I was going to rename it and
clean up the dependencies based on that a bit.
} OK. I did it. The feature_init call in setup.c is only relevant to OF
} machines, so I put a CONFIG_ALL_PPC around it. Then it hit me (it
} hasn't happened in a while :-)........Does this mean CONFIG_PREP,
} CONFIG_CHRP, CONFIG_PMAC are becoming obsolete? They seem to be
} combined now. Maybe this is why I can't build a kernel for my Macs
} because I still select PowerMac instead of "all PPC"?
}
} Guess I'll go chase some Easter Bunnies......
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-04-24 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-24 1:34 feature_init Dan Malek
2000-04-24 18:54 ` Cort Dougan [this message]
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=20000424125423.Z1544@medea.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).