From: "Mike Frysinger" <vapier.adi@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: pwilshire@cox.net, linux-embedded@vger.kernel.org
Subject: Re: initramfs size limitation
Date: Sun, 1 Jun 2008 20:25:11 -0400 [thread overview]
Message-ID: <8bd0f97a0806011725u3dc70e2cy1b317b2b6564f5c8@mail.gmail.com> (raw)
In-Reply-To: <200806011903.47135.rob@landley.net>
On Sun, Jun 1, 2008 at 8:03 PM, Rob Landley wrote:
> On Saturday 31 May 2008 07:44:14 Phil Wilshire wrote:
>> I hope this is the right place and the right sort of question.
>>
>> I work closely with the Blackfin systems and they have now integrated
>> the initramfs generation into their system build. The result is great
>> the root fs is ready to run from the page cache.
>
> Is it possible to get blackfin working with a vanilla gcc release yet, or do
> you still need out-of-tree patches? (I have a blackfin board I got at OLS,
> but it needs a toolchain I can't reproduce.)
there's plenty of usable binaries available
> fact it would be really nice if qemu grew blackfin support because messing
i imagine it would be ... too bad qemu lacks real documentation
>> There is one problem that I can see that may be more serious for
>> embedded users.
>> As far as I can tell the initramfs filesystem is not restricted in size.
>> You can keep writing files until it uses all available memory.
>
> Yup. There have intermittently been patches to make rootfs be tmpfs instead
> of ramfs, the most recent of which I remember was:
> http://lkml.org/lkml/2007/7/13/354
it wouldnt matter. tmpfs on NOMMU doesnt support any of the options
like MMU. look at mm/tiny-shmem.c and init/Kconfig.
-mike
next prev parent reply other threads:[~2008-06-02 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 12:44 initramfs size limitation Phil Wilshire
2008-06-02 0:03 ` Rob Landley
2008-06-02 0:25 ` Mike Frysinger [this message]
2008-06-02 0:42 ` Bryan Wu
2008-06-03 20:59 ` Rob Landley
2008-06-03 21:54 ` Mike Frysinger
2008-06-04 17:24 ` Rob Landley
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=8bd0f97a0806011725u3dc70e2cy1b317b2b6564f5c8@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=pwilshire@cox.net \
--cc=rob@landley.net \
/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).