From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] rootfs.ubifs not able to mount by kernel
Date: Sun, 30 Jan 2011 15:20:21 +0100 [thread overview]
Message-ID: <20110130152021.4073fd79@surf> (raw)
In-Reply-To: <4D453DDE.7000007@googlemail.com>
Hello Marcus,
On Sun, 30 Jan 2011 11:30:54 +0100
Marcus Osdoba <marcus.osdoba@googlemail.com> wrote:
> Writing a ubiFS on NAND (with RAW u-boot command) and mounting
> afterwards is not possible. The produced ubiFS must be ubinized to a UBI
> image.
Correct. But Nataraj did create the UBI volume with U-Boot, and has
written the UBIFS image inside this UBI volume.
> I must admit, that I did not exactly understand the diffrence between
> ubifs and ubi, but as explained on the mtd-utils page, the ubifs is the
> FS layer to the kernel in a traditional sense (like ext2FS) and ubi is a
> technical layer between RAW NAND and FS.
> http://www.linux-mtd.infradead.org/doc/ubi.html
> http://www.linux-mtd.infradead.org/doc/ubifs.html
UBI is a bit like a LVM (Logical Volume Manager) for MTD devices. On
top of physical erase blocks, it creates volumes composed of virtual
erase blocks. This level of indirection allows UBI to handle bad block
replacement, wear leveling and other low-level flash issues.
Note that since recently, Buildroot is capable of generating a
ubinize'd UBI filesystem image, thanks to the work done by Julien
Boibessot from Armadeus. This is available in Buildroot git, and will
be part of the next Buildroot release.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-01-30 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 8:45 [Buildroot] rootfs.ubifs not able to mount by kernel nataraj at vaaraahi.com
2011-01-30 10:30 ` Marcus Osdoba
2011-01-30 14:20 ` Thomas Petazzoni [this message]
2011-01-31 21:18 ` Marcus Osdoba
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=20110130152021.4073fd79@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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