From: Thomas Gleixner <tglx@linutronix.de>
To: David Woodhouse <dwmw2@infradead.org>, ?? <kevin@gv.com.tw>
Cc: linux-mtd@lists.infradead.org
Subject: Re: do i have to "eraseall" first?
Date: Wed, 31 Jul 2002 20:33:52 +0200 [thread overview]
Message-ID: <0H04006C5M7GUI@smtp-out.bhp.t-online.de> (raw)
In-Reply-To: <10399.1028120646@redhat.com>
On Wednesday, 31. July 2002 15:04, David Woodhouse wrote:
> kevin@gv.com.tw said:
> > now it report many "magic bitmask not found" do i have to do
> > something like "eraseall /dev/mtdblock1" before "cp test.img /dev/
> > mtdblock1"?
>
> Yes. eraseall /dev/mtd1. I don't remember how you are supposed to write the
> images so the ECC is correct. Thomas?
cp test.img /dev/mtdblock1 should write ecc correct, if it's configured
correctly. See
http://www.linux-mtd.infradead.org/tech/nand.html
But eraseall does not set the block is erased and "jffs2 formatted" info in
the OOB area, which leads to "magic bitmask not found".
We decided some time ago, that erase, invoked from the shell, _CANNOT_ do
this on it's own, because it will not know, which filesystem is going to be
mounted.
The information is set, when erase is controlled by jffs2.
The only safe way to do it, is
cd yourstuff
cp -r * /mnt/bla
or you tell your bootloader to do it.
--
Thomas
___________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2002-07-31 18:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <010c01c2388d$05af1660$1b0448c0@gv.com.tw>
2002-07-31 8:06 ` can i use jffs2 directly on /dev/mtdblock? ??
2002-07-31 8:15 ` David Woodhouse
[not found] ` <6562.1028118221@redhat.com>
2002-07-31 12:41 ` do i have to "eraseall" first? ??
2002-07-31 13:00 ` how to init and mount jffs2? ??
2002-07-31 13:04 ` do i have to "eraseall" first? David Woodhouse
2002-07-31 18:33 ` Thomas Gleixner [this message]
2002-08-01 3:23 ` ??
2002-08-01 9:28 ` Thomas Gleixner
2002-08-01 12:30 ` thanks , after this patch , i mount jffs2 successfully ??
2002-08-02 2:50 ` error when writing to jffs2 ??
2002-08-05 9:54 ` David Woodhouse
2002-08-05 10:18 ` error when writing to jffs2 (scan.c v1.79 20020725) ??
2002-08-05 10:25 ` David Woodhouse
2002-08-06 4:06 ` error when writing to jffs2 (success in another evb) ??
2002-08-06 6:13 ` what't the max partition(single file size) jffs2/mtd can support?(64MB? or 2GB? or 8GB?) ??
2002-08-06 8:26 ` David Woodhouse
2002-08-06 11:43 ` fail to rm files when jffs2 is full ??
2002-08-06 12:26 ` David Woodhouse
2002-08-06 13:03 ` No free space left for GC(test2 with log) ??
2002-08-06 13:07 ` David Woodhouse
2002-08-06 14:08 ` Thomas Gleixner
2002-08-07 10:05 ` David Woodhouse
2002-08-06 9:46 ` error when writing to jffs2 (success in another evb) Thomas Gleixner
2002-10-24 10:31 ` does mtd support both toshiba and samsung 128MBytes (1GBits) nand flash? ??
2002-10-24 12:28 ` Thomas Gleixner
2002-09-09 9:42 ` any function/ioctl to get compression ratio of a single file in jffs2? ??
2002-09-13 1:59 ` any comment about following news at http://www.handhelds.org/ ? ??
2002-09-13 7:23 ` David Woodhouse
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=0H04006C5M7GUI@smtp-out.bhp.t-online.de \
--to=tglx@linutronix.de \
--cc=dwmw2@infradead.org \
--cc=kevin@gv.com.tw \
--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