From: Russ Dill <Russ.Dill@asu.edu>
To: "Henrik Nordström" <hno@marasystems.com>
Cc: Srinivasan.Ramasubramaniam@nokia.com, elf@buici.com,
kenneth.johansson@etx.ericsson.se, linux-mtd@lists.infradead.org
Subject: RE: Interest in DOC and YAFFS? --> YAFFS bootloading
Date: 25 Sep 2002 09:34:13 -0700 [thread overview]
Message-ID: <1032971654.13282.18.camel@russ> (raw)
In-Reply-To: <Pine.LNX.4.44.0209251531440.32689-100000@filer.marasystems.com>
On Wed, 2002-09-25 at 06:34, Henrik Nordström wrote:
> On 25 Sep 2002, Russ Dill wrote:
>
> > the compressed cramfs image will be loaded into ram, and then, from
> > there, as pages are needed, they will be decompressed again and put into
> > ram (but again, if memory is in a pinch, these pages can be dropped). I
> > don't know if an ext2 initrd will do XIP (execute in place), but I
> > somehow doubt that anyone has worked on that, meaning that the pages
> > would need to be copied again, in which case, a cramfs would use less
> > ram.
>
> I have never succeded in getting cramfs to work from a ramdisk.. it does
> something magic with blocksizes that seems to srew up the ramdisk data
> (first blocks get "forgotten").
the block size needs to be changed to 4k, there are patches floating
around
> As the ramdisk is living within the buffer cache a ext2 image most likely
> will do XIP.
I don't know about that, the data would need to be aligned to 4k, I
would think that the first part of most 4k pages would have fs
information or some such, someone can call me on this though
next prev parent reply other threads:[~2002-09-25 16:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 7:09 Interest in DOC and YAFFS? --> YAFFS bootloading Srinivasan.Ramasubramaniam
2002-09-25 8:38 ` Russ Dill
2002-09-25 13:34 ` Henrik Nordström
2002-09-25 16:34 ` Russ Dill [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-23 9:20 jffs2 and Doc 2000 eylon eyal
2002-09-24 0:03 ` Interest in DOC and YAFFS? Charles Manning
2002-09-24 3:44 ` Marc Singer
2002-09-24 3:58 ` Interest in DOC and YAFFS? --> YAFFS bootloading Charles Manning
2002-09-24 4:44 ` Marc Singer
2002-09-24 7:53 ` Russ Dill
2002-09-24 16:53 ` Marc Singer
2002-09-24 16:59 ` Russ Dill
2002-09-24 17:14 ` Marc Singer
2002-09-24 17:21 ` Brian J. Fox
2002-09-24 17:30 ` Russ Dill
2002-09-24 18:33 ` Marc Singer
2002-09-24 17:44 ` Kenneth Johansson
2002-09-24 18:37 ` Marc Singer
2002-09-24 18:47 ` Russ Dill
2002-09-24 20:22 ` Marc Singer
2002-09-24 20:41 ` Russ Dill
2002-09-24 7:23 ` Nick Bane
2002-09-24 16:55 ` Marc Singer
2002-09-24 18:23 ` Nick Bane
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=1032971654.13282.18.camel@russ \
--to=russ.dill@asu.edu \
--cc=Srinivasan.Ramasubramaniam@nokia.com \
--cc=elf@buici.com \
--cc=hno@marasystems.com \
--cc=kenneth.johansson@etx.ericsson.se \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.