From: Christoph Hellwig <hch@lst.de>
To: Shane McDonald <mcdonald.shane@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: [MIPS] Resolve compile issues with msp71xx configuration
Date: Tue, 28 Apr 2009 11:21:37 +0200 [thread overview]
Message-ID: <20090428092137.GB2408@lst.de> (raw)
In-Reply-To: <b2b2f2320904272321l4cf30181rcde6b1d42a5b5547@mail.gmail.com>
On Tue, Apr 28, 2009 at 12:21:09AM -0600, Shane McDonald wrote:
> 4. Remove the entire get_ramroot() code, both squashfs and cramfs, as
> Christoph has suggested. I am hesitant to do this as it also affects code
> in the MTD subsystem (file maps/pmcmsp-ramroot.c), and it also loses some
> functionality on the PMC boards (putting the rootfs in RAM immediately
> following the kernel). Perhaps there's a better way to handle this?
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.
next prev parent reply other threads:[~2009-04-28 9:21 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 [this message]
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
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=20090428092137.GB2408@lst.de \
--to=hch@lst.de \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=mcdonald.shane@gmail.com \
--cc=ralf@linux-mips.org \
/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).