public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Nikolai Vladychevski" <niko@isl.net.mx>
Cc: linux-mtd@lists.infradead.org
Subject: Re: duplicate DoC millenium with dd
Date: Tue, 11 Sep 2001 23:00:24 +0100	[thread overview]
Message-ID: <10449.1000245624@redhat.com> (raw)
In-Reply-To: <20010911205853.21285.qmail@qis>

niko@isl.net.mx said:
>  yes, this is the problem... right now I'm leaving 1 Meg for the
> linuxBIOS  and kernel and right now there is left as little as 40 K
> bytes free space of  that meg. 

Use modules?


>  If I update the  software on the chip once a week (it's an automatic
> update via remote  server), will it survive for 2 years without
> errors, for example ?  

It doesn't degrade over time. Using it the first time may lose the 
bad-block information which is put on it by the NAND flash chip 
manufacturer (Toshiba or Samsung, not M-Systems). After that there's no 
difference.

>  Wow! that sounds cool! I have to try it, but would linuxBIOS conflict
> with  it?  

No, should be fine. You could have it appear as three MTD devices - one for 
LinuxBIOS, one for the kernel, and one for cramfs.

Using cramfs directly on the NAND flash gives you no error correction and 
no facility to work around bad blocks. I wouldn't wan to do it like that in 
production, although in practice it'll work unless you have a chip with bad 
blocks.

--
dwmw2

  reply	other threads:[~2001-09-11 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-11 18:26 duplicate DoC millenium with dd Nikolai Vladychevski
2001-09-11 20:17 ` David Woodhouse
2001-09-11 20:13   ` Nikolai Vladychevski
2001-09-11 21:23     ` David Woodhouse
2001-09-11 20:58       ` Nikolai Vladychevski
2001-09-11 22:00         ` David Woodhouse [this message]
2001-09-11 22:20           ` Nikolai Vladychevski

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=10449.1000245624@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=niko@isl.net.mx \
    /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