public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: twebb <taliaferro62@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: change in how ubiformat works
Date: Fri, 26 Nov 2010 18:03:28 +0200	[thread overview]
Message-ID: <1290787408.2552.28.camel@localhost> (raw)
In-Reply-To: <AANLkTi=rE+u0OiGXj=HxGYRB9F4p228GpHzGadJm+982@mail.gmail.com>

On Fri, 2010-11-12 at 13:47 -0500, twebb wrote:
> I use a sequence as follows: " flash_erase - ubiformat - nanddump -
> verify " to confirm that a UBI image was properly stored in NAND
> flash.  I realize that flash_erase is not recommended because it
> destroys erase counters, but this is only done on virgin flash so
> should not be an issue.
> 
> However, I recently upgraded the mtd-utils, and particularly ubiformat
> from 1.4 to 1.5, and now I see that what I read back (via nanddump)
> does not match the original UBI image.  Can anyone confirm whether
> ubiformat.c changes sometime between 1.4 and 1.5 would result in this
> behavior?  I have looked at ubiformat.c changes and am wondering if it
> has to do with image sequence number support.


Ok, just define your own sequence number. Use, say, --image-seq=100 both
with ubinize and ubiformat.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      parent reply	other threads:[~2010-11-26 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 18:47 change in how ubiformat works twebb
2010-11-26 15:56 ` Artem Bityutskiy
2010-11-26 16:03 ` Artem Bityutskiy [this message]

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=1290787408.2552.28.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=taliaferro62@gmail.com \
    /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