From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Jon Povey <Jon.Povey@racelogic.co.uk>
Cc: "davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: How to stop mtd char device generating ECC on writes?
Date: Wed, 11 Aug 2010 11:43:05 +0200 [thread overview]
Message-ID: <4C6270A9.5090606@parrot.com> (raw)
In-Reply-To: <70E876B0EA86DD4BAF101844BC814DFE0903DC2323@Cloud.RL.local>
Hi,
Jon Povey a écrit :
> But I can't seem to write it back properly using nandwrite.
> Testing on another partition mtd6, If I do this:
> nandwrite -r -s 0x20000 /dev/mtd6 ubl0.dump
> then it seems my 64 bytes of "OOB" are skipped and I get a generated 24 bytes of 0xFF spare and 40 bytes of generated ECC.
>
> If I use --noecc --oob instead of -r, it looks like my 64 bytes of "OOB" does get written, but then hardware ECC is getting written OVER THE TOP, i.e. the last 40 bytes have various bits 0 that should be 1 (but no 1s that should be 0)
>
> I am looking through the nandwrite and drivers/mtd sources at the moment, but would love to get a clue if someone can tell me
>
> - Does MTD support what I'm trying to do from userland?
yes write in raw mode + MEMWRITEOOB. But you will need 2 number of program.
>
> - If yes, could this be a bug in the DaVinci NAND driver?
>
> - Or, is nandwrite supposed to support this? or do I need to modify it?
>
I don't know nandwrite
Matthieu.
next prev parent reply other threads:[~2010-08-11 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 9:30 How to stop mtd char device generating ECC on writes? Jon Povey
2010-08-11 9:43 ` Matthieu CASTET [this message]
2010-08-11 9:46 ` Jon Povey
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=4C6270A9.5090606@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=Jon.Povey@racelogic.co.uk \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--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.