All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: matti kaasinen <matti.kaasinen@gmail.com>
Cc: meta-arago@arago-project.org, trini@ti.com, Pekon Gupta <pekon@ti.com>
Subject: Re: ubifs crossupport between Linux and U-Boot
Date: Wed, 29 Jan 2014 11:23:14 -0500	[thread overview]
Message-ID: <20140129162314.GP6814@edge> (raw)
In-Reply-To: <CADnUhn3EbUhYYo4TjxVi+dDM9n-62SOk65kCH-ehe_-Ax4DGZg@mail.gmail.com>

+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.
> 
> Patching required include:
> Quote from Pekon's answer to me:
> 
> "
> I don't think any earlier kernel versions ever supported beaglebone
> Its only recently that a major patch-series of NAND driver was
> accepted and  tested on beaglebone.
> The patches  are currently in l2-mtd.git tree which should make into
> 3.13 kernel, before being in linux-next for sometime.
> (a) Reference:
> http://lists.infradead.org/pipermail/linux-mtd/2013-October/049462.html
> 
> (b) In addition to above series, you might need beaglebone DTS updates
> which you can refer from below ..
> http://lists.infradead.org/pipermail/linux-mtd/2013-October/049438.html
> "
> 
> U-Boot patching over U-Boot 2013-10 should be found from:
> http://patchwork.ozlabs.org/project/uboot/list/?submitter=17320&state=*.
> 
> I'm not sure how valid above link is anymore. Maybe Pekon can comment that.
> 
> -Matti
> 
> 2014-01-29 Denys Dmytriyenko <denys@ti.com>
> 
> > On Mon, Jan 20, 2014 at 04:29:52PM +0200, matti kaasinen wrote:
> > > Hi!
> > >
> > > I Have been using Angstrom distribution for my beaglebone (+ nand flash)
> > > based board. Problem with Angstrom baked Linux/U-boot images is that
> > > whereas both support ubifs partition on nand flash they both seem to
> > handle
> > > it in their own ways. Does Aragon distribution have this same problem?
> >
> > Can you please provide more detailed report for the issue? Otherwise it's
> > quite difficult to give any recommendations. Thanks.
> >
> > --
> > Denys
> >


  reply	other threads:[~2014-01-29 16:23 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 [this message]
2014-02-04 20:39       ` Tom Rini

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=20140129162314.GP6814@edge \
    --to=denys@ti.com \
    --cc=matti.kaasinen@gmail.com \
    --cc=meta-arago@arago-project.org \
    --cc=pekon@ti.com \
    --cc=trini@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.