linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
	Arnd Bergmann <arnd@arndb.de>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: PATCH powerpc: Merge asm-ppc*/sections.h
Date: Sun, 18 Sep 2005 11:28:35 +1000	[thread overview]
Message-ID: <1127006916.23095.6.camel@gaston> (raw)
In-Reply-To: <20050915205709.GA31156@iram.es>


> So yes, I object strongly object if I don't have a way 
> of removing useless PMAC code. The kernel is already very 
> bloated compared with the 2.2 we started with, which was 
> well below 1MB with the minimal setup: serial console, root 
> on NFS, no swap, some locally modules to control the PCI<->VME 
> bridge and what is behind on the VME bus. 

I think we should have the ability to not build some platforms like we
have on ppc64. That would allow you to build a PReP kernel without CHRP
and PMAC code.

Ben.

      parent reply	other threads:[~2005-09-18  1:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 20:43 PATCH powerpc: Merge asm-ppc*/sections.h Jon Loeliger
2005-09-14  2:35 ` Arnd Bergmann
2005-09-14 13:46   ` Jon Loeliger
2005-09-15 11:09     ` Paul Mackerras
2005-09-15 17:07       ` Jon Loeliger
2005-09-15 17:28       ` Kumar Gala
2005-09-15 20:57       ` Gabriel Paubert
2005-09-15 21:21         ` Dan Malek
2005-09-15 22:00         ` Paul Mackerras
2005-09-15 22:37           ` Gabriel Paubert
2005-09-16 14:46             ` Jon Loeliger
2005-09-18  1:28         ` Benjamin Herrenschmidt [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=1127006916.23095.6.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=paubert@iram.es \
    /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).