linux-mips
[Top] [All Lists]

Re: [MIPS] Resolve compile issues with msp71xx configuration

To: Shane McDonald <mcdonald.shane@gmail.com>
Subject: Re: [MIPS] Resolve compile issues with msp71xx configuration
From: Ralf Baechle <ralf@linux-mips.org>
Date: Tue, 28 Apr 2009 17:09:42 +0200
Cc: Christoph Hellwig <hch@lst.de>, Geert Uytterhoeven <geert@linux-m68k.org>, linux-mips@linux-mips.org
In-reply-to: <b2b2f2320904280748q3a45ecf6r46dcb536877663c@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <E1LyQQX-00047N-6E@localhost> <20090427130952.GA30817@linux-mips.org> <10f740e80904270622u730ba067g660257847dc526de@mail.gmail.com> <20090428092005.GA2408@lst.de> <b2b2f2320904280748q3a45ecf6r46dcb536877663c@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.18 (2008-05-17)
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

<Prev in Thread] Current Thread [Next in Thread>