From: Tom Rini <trini@ti.com>
To: matti kaasinen <matti.kaasinen@gmail.com>
Cc: meta-arago@arago-project.org, Pekon Gupta <pekon@ti.com>
Subject: Re: ubifs crossupport between Linux and U-Boot
Date: Tue, 4 Feb 2014 15:39:19 -0500 [thread overview]
Message-ID: <52F14FF7.5090103@ti.com> (raw)
In-Reply-To: <20140129162314.GP6814@edge>
On 01/29/2014 11:23 AM, Denys Dmytriyenko wrote:
> +Tom Rini
>
> Tom, can you please comment? Thanks.
>
>
> On Wed, Jan 29, 2014 at 05:20:26PM +0200, matti kaasinen wrote:
>> In short:
>> If I create UBIFS partition on Linux side, it works quite fine. I can
>> create directories, files update them without problems. But if I open this
>> volume on U-Boot side, I'll get thousands of ecc error messages. Now, if I
>> try to access this same volume from Linux side after this episode, it also
>> provides these ecc errors. Therefore, Linux created UBIFS partition gets
>> corrupted by accessing it from U-Boot side. Volume opening is enough for
>> this. This I have experienced by Angstrom distribution with Linux 3.8.13
>> and it possibly was U-Boot 10.04. Anyhow, as it seems that you are now
>> working with Linux 3.12 - U-Boot 2013-10 combination, you'll need patching
>> to cope with this issue. By my understanding required patching is not made
>> before U-Boot 2014-01 and Linux 3.14.
If you do not have sufficient malloc space in U-Boot (and by default, we
do not right now on TI armv7 platforms, in some cases, I will be fixing
this shortly), UBI/UBIFS support can go whacky. I've not seen ECC
errors, but I've seen other things.
Also you made sure that step one was a 'nand erase' on the whole of the
area you're going to be using, right?
--
Tom
prev parent reply other threads:[~2014-02-04 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 14:29 ubifs crossupport between Linux and U-Boot matti kaasinen
2014-01-29 2:53 ` Denys Dmytriyenko
2014-01-29 15:20 ` matti kaasinen
2014-01-29 16:23 ` Denys Dmytriyenko
2014-02-04 20:39 ` Tom Rini [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=52F14FF7.5090103@ti.com \
--to=trini@ti.com \
--cc=matti.kaasinen@gmail.com \
--cc=meta-arago@arago-project.org \
--cc=pekon@ti.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.