linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Shane McDonald <mcdonald.shane@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-mips@linux-mips.org
Subject: Re: [MIPS] Resolve compile issues with msp71xx configuration
Date: Tue, 28 Apr 2009 17:09:42 +0200	[thread overview]
Message-ID: <20090428150942.GA28519@linux-mips.org> (raw)
In-Reply-To: <b2b2f2320904280748q3a45ecf6r46dcb536877663c@mail.gmail.com>

On Tue, Apr 28, 2009 at 08:48:52AM -0600, Shane McDonald wrote:

> > If the rootfs really is in ram only (and thus you discard any changes to
> > it) you can just use an initramfs which is a lot simpler than any of the
> > cramfs and squashfs hacks and supported by platform-independent code.
> The rootfs is ram only with a union mount of a jffs2 filesystem to retain
> changes.  The target system is a resource-constrained router board, and we
> were trying to keep everything as small as possible.  If I remember
> correctly, this code originally came over from an internal 2.4 port on an
> even more resource-constrained platform; perhaps there are better options in
> today's world.
> 
> I will look into a better solution to this problem.  In the meantime, I'm
> hesitant to remove the existing code -- I think I prefer to leave it
> uncompilable until that solution is found.

You may want to chainsaw it into a shape were it's usable in some way -
for example with NFS root until you have a chance to sort this out.

  Ralf

  parent reply	other threads:[~2009-04-28 15:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 12:59 [MIPS] Resolve compile issues with msp71xx configuration Shane McDonald
2009-04-27 13:09 ` Ralf Baechle
2009-04-27 13:18   ` Sergei Shtylyov
2009-04-28  5:36     ` Shane McDonald
2009-04-27 13:22   ` Geert Uytterhoeven
2009-04-28  6:21     ` Shane McDonald
2009-04-28  7:16       ` Geert Uytterhoeven
2009-04-28  9:21       ` Christoph Hellwig
2009-04-28 10:50         ` Kevin D. Kissell
2009-04-28  9:20     ` Christoph Hellwig
2009-04-28 14:48       ` Shane McDonald
2009-04-28 15:05         ` Florian Fainelli
2009-04-28 15:55           ` Shane McDonald
2009-04-28 15:09         ` Ralf Baechle [this message]
2009-04-27 13:27 ` Christoph Hellwig

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=20090428150942.GA28519@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=geert@linux-m68k.org \
    --cc=hch@lst.de \
    --cc=linux-mips@linux-mips.org \
    --cc=mcdonald.shane@gmail.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).