From: Russ Dill <Russ.Dill@asu.edu>
To: linux-mtd@lists.infradead.org
Subject: using the DOC2000
Date: 23 Jan 2002 16:47:35 -0700 [thread overview]
Message-ID: <1011829656.1974.0.camel@timmy> (raw)
I've been using 2 MB of standard flash on an ARM system. The layout I've
been using is:
boot blocks
32k - boot loader (blob)
8k - journaled config
8k - journaled config
16k - static config
main blocks
128k * 3 - backup cramfs
128k * 12 - primary cramfs
both cramfs filesystems contain their own kernel, and the bootloader can
boot either. I'm trying to port this over to x86 using a DOC2000. I'm
trying to translate how I'm currently using MTD, to how I need to use a
DOC2000. the only writing that occurs to the flash is the initial flash
of everything, the periodic (every 4 hours to every few days) writing of
the journaled config blocks, and the updates to the primary fs (once
every few months). Currently as it stands, it seems for the DOC to be
usefull at all, I need to use NTFL, which I don't paticularly care for.
I'd like to mount my cramfs on a read only block device, as well as
control the writing of the journaled config, as well as their erase
blocks, so that I know what is going on with the flash in case power is
lost.
Does lilo need NTFL to be able to boot linux off of the device? does
grub? Can I control erase cycles for my journaled config if I am using
NTFL? What is all this talk about ECC?
reply other threads:[~2002-01-23 23:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1011829656.1974.0.camel@timmy \
--to=russ.dill@asu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox