public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
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:44:21 +0300	[thread overview]
Message-ID: <1210671861.5708.5.camel@sauron> (raw)
In-Reply-To: <bae050c10805092120u14177a03td46fa8175f89aa66@mail.gmail.com>

On Sat, 2008-05-10 at 12:20 +0800, Nancy wrote:
>        ubifs.img (generated by mkfs.ubifs) do contained unmapped LEBs.

This statement does not make sense. Mapped/unmapped is UBI notion, not
UBIFS.

>        #ubiupdatevol /dev/ubi0_0 ubifs.img   also write the unmapped
> LEBs to Nand flash.
It does not write them, but it creates them if the image size is less
then amount of space on the volume. What else do you expect?

>        Oh, There should have the same problem like I use nandwrite to
> write UBI image to Nand. But the practice tells everything is OK.

No, ubiupdatevol handles 0xFFs just fine.

> Example 2 shows
>        ubiupdatevol: error!: specify UBI device name and image file
> name as first 2 par
> ameters (use -h for help)
>        but
>        #ubiupdatevol /dev/ubi0_0 ubifs.img -t
>        instead, even the function do not need an input image file

Fixed, thanks for report.

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

  parent reply	other threads:[~2008-05-13  9:46 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
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 [this message]
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=1210671861.5708.5.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox