From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Loeliger <linuxppc@jdl.com>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: PATCH powerpc: 00/04 Remove __pmac, etc, sections, merge sections.h
Date: Sun, 18 Sep 2005 11:25:35 +1000 [thread overview]
Message-ID: <1127006735.23095.4.camel@gaston> (raw)
In-Reply-To: <E1EGefQ-00072D-34@jdl.com>
On Sat, 2005-09-17 at 10:31 -0500, Jon Loeliger wrote:
> Here is a new patch that removes all notion of the pmac, prep,
> chrp and openfirmware initialization sections, and then unifies
> the sections.h files without those __pmac, etc, sections identifiers
> cluttering things up.
When did we decide to do that ? Some people are still using ppc machines
with rather small memory footprint (old ones), it's handy to get rid of
the code you don't need... It would make sense if we could compile
CHRP/PMAC/PREP in/out (like we can do with platforms on ppc64) so that
people who have tight memory requirements can build a PReP or CHRP
kernel without all of the pmac code.
Ben.
next prev parent reply other threads:[~2005-09-18 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 15:31 PATCH powerpc: 00/04 Remove __pmac, etc, sections, merge sections.h Jon Loeliger
2005-09-17 15:35 ` PATCH powerpc: 01/04 Remove sections use from ppc Jon Loeliger
2005-09-17 15:36 ` PATCH powerpc: 02/04 Remove sections use from ppc64 and drivers Jon Loeliger
2005-09-17 15:38 ` PATCH powerpc: 03/04 Remove section free() and linker script bits Jon Loeliger
2005-09-17 15:39 ` PATCH powerpc: 04/04 Merge simplified sections.h into asm-powerpc Jon Loeliger
2005-09-18 1:25 ` Benjamin Herrenschmidt [this message]
2005-09-18 17:50 ` PATCH powerpc: 00/04 Remove __pmac, etc, sections, merge sections.h Kumar Gala
2005-09-18 22:13 ` Benjamin Herrenschmidt
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=1127006735.23095.4.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=linuxppc@jdl.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).