From: Dan Malek <dan@mvista.com>
To: Matt Porter <mporter@mvista.com>
Cc: mgreer@mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: If not CONFIG_ALL_PPC, you're broken
Date: Tue, 17 Oct 2000 11:28:49 -0400 [thread overview]
Message-ID: <39EC7031.A17F4366@mvista.com> (raw)
In-Reply-To: 20001017041751.A9882@cx258813-a.chnd1.az.home.com
Matt Porter wrote:
> My solution for creating a slim embedded PPC kernel in 2.2 was to
> stub out all the calls to Mac/CHRP specific routines that were made
> in head.S and setup.c.
I think that is fine, but we have lost the configuration options that
indicate this should happen. I first want to get a set of options
that makes sense, rework the code so we can selectively build the
kernels again (with CONFIG_ALL_PPC a sum of the options), and be able
to select processor core/processor type separately (i.e. I need to
select CONFIG_6xx and CONFIG_8260 at the same time...there are more
of these coming from both Mot and IBM).
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-10-17 15:28 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
2000-10-17 11:17 ` Matt Porter
2000-10-17 15:28 ` Dan Malek [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=39EC7031.A17F4366@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mgreer@mvista.com \
--cc=mporter@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).