| To: | Christoph Hellwig <hch@lst.de> |
|---|---|
| Subject: | Re: [MIPS] Resolve compile issues with msp71xx configuration |
| From: | "Kevin D. Kissell" <kevink@paralogos.com> |
| Date: | Tue, 28 Apr 2009 12:50:04 +0200 |
| Cc: | Shane McDonald <mcdonald.shane@gmail.com>, Geert Uytterhoeven <geert@linux-m68k.org>, Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org |
| In-reply-to: | <20090428092137.GB2408@lst.de> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <E1LyQQX-00047N-6E@localhost> <20090427130952.GA30817@linux-mips.org> <10f740e80904270622u730ba067g660257847dc526de@mail.gmail.com> <b2b2f2320904272321l4cf30181rcde6b1d42a5b5547@mail.gmail.com> <20090428092137.GB2408@lst.de> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Thunderbird 2.0.0.21 (Windows/20090302) |
Christoph Hellwig wrote:
> 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.
>
I second that emotion.
Kevin K.
|
| Previous by Date: | Re: [MIPS] Resolve compile issues with msp71xx configuration, Christoph Hellwig |
|---|---|
| Next by Date: | Linux on Linksys PSUS4?, Andrew Wiley |
| Previous by Thread: | Re: [MIPS] Resolve compile issues with msp71xx configuration, Christoph Hellwig |
| Next by Thread: | Re: [MIPS] Resolve compile issues with msp71xx configuration, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |