All of lore.kernel.org
 help / color / mirror / Atom feed
From: "" <simon@baydel.com>
To: "Damien GERANTON" <dgeranton@alpha3i.com>
Cc: "MTD mailing list" <linux-mtd@lists.infradead.org>
Subject: Re: JFFS/MTD and Raw access
Date: Fri, 29 Nov 2002 11:28:16 -0000	[thread overview]
Message-ID: <3DE74F50.30675.396F40@localhost> (raw)
In-Reply-To: <BNEJIGKFJNJLELKBCMDAMEFGCEAA.dgeranton@alpha3i.com>

I have hit exactly the same problem using JFFS2. I am no authority 
on this but, I thought the problem might be caused by the write 
generating different OOB data for input blocks, which are erased or 
only partially written. So I guess what needs to be done is to read 
and copy the DATA and OOB. I think you can do this with the 
nanddump and nandwrite utilities. I guess I will have to try it 
sometime. 

Cheers

Simon.
On 28 Nov 2002, at 17:21, Damien GERANTON wrote:

> Hello,
> 
> I face a strange problem, i use MTD with JFFS and i want to clone my
> systeme from one card to another. I thought that some think like : dd
> if=/dev/mtd0 of=/master.img
> 
> and
> 
> dd if=/master.img of=/dev/mtd0
> 
> But it does not work, if after i do
> 
> dd if=/dev/mtd0 of=/test.img
> diff test.img master.img
> i says they are different.
> 
> Is it normal.
> 
> Is RAW acces really RAW ?
> 
> Do i miss some think ?
> 
> Thanks
> 
> PS : I use MTD on 2.2.17 kernel
> 
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/


__________________________

Simon Haynes - Baydel 
Phone : 44 (0) 1372 378811
Email : simon@baydel.com
__________________________

  reply	other threads:[~2002-11-29 11:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-28 16:21 JFFS/MTD and Raw access Damien GERANTON
2002-11-29 11:28 ` simon [this message]
2002-11-29 12:35   ` Thomas Gleixner
2002-11-29 12:36 ` Kenneth Johansson
  -- strict thread matches above, loose matches on Subject: below --
2002-11-29 13:04 John Hall
2002-11-29 14:23 ` Thomas Gleixner

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=3DE74F50.30675.396F40@localhost \
    --to=simon@baydel.com \
    --cc=dgeranton@alpha3i.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.