From: Artem Bityutskiy <dedekind@infradead.org>
To: Nancy <nancydreaming@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: ubifs image file confusion!
Date: Tue, 13 May 2008 12:48:45 +0300 [thread overview]
Message-ID: <1210672125.5708.9.camel@sauron> (raw)
In-Reply-To: <bae050c10805100031u25a233ffi65e39705ea778fcc@mail.gmail.com>
On Sat, 2008-05-10 at 15:31 +0800, Nancy wrote:
> I think UBIFS will reserved some logic block number for interal use.
> To keep a simple logic to build tool like ubiupdatevol
> ubifs.img(generated by mkfs.ubifs) should contains those reserved
> unused LEBs and fill them with data 0xFF.
> In our situation:
> After Nand flash is burned, product test begin. During those
> test, all volumes are READONLY. Then final check goes to Volume
> content CRC check. I need a
> volume read tool to read the whole volume content and generate CRC.
> Then have a comparition with the original volume image CRC. This tool
> is quite similar to ubidumpvol.
dd if=/dev/mtd5 of=file
or
dd if=/dev/ubi0_0 of=file
> VFAT give me a hint, the file system reserved space are all
> 0x00. Like you allocate a space: reserved=malloc( 3LEBsize ); Though
> you do not use it now, but you can init it memset(reserved, 0x00,
> 3LEBsize); And if like that, the file system reserved space will
> become mapped.
> Would you mind do this?
Sorry, I still do not understand what is this all about. I do not
understand the problem.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-05-13 9:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 9:17 ubifs image file confusion! Nancy
2008-05-08 9:56 ` Nancy
2008-05-14 13:23 ` Artem Bityutskiy
2008-05-08 10:48 ` Artem Bityutskiy
2008-05-09 7:05 ` Nancy
2008-05-10 4:20 ` Nancy
2008-05-10 7:31 ` Nancy
2008-05-13 9:48 ` Artem Bityutskiy [this message]
2008-05-13 12:52 ` Nancy
2008-05-14 13:45 ` Artem Bityutskiy
2008-05-15 4:06 ` Nancy
2008-05-13 9:44 ` Artem Bityutskiy
2008-05-13 12:41 ` Nancy
2008-05-14 13:20 ` Artem Bityutskiy
2008-05-15 3:18 ` Nancy
2008-07-08 10:45 ` Artem Bityutskiy
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=1210672125.5708.9.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nancydreaming@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 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.