public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ivan Djelic <ivan.djelic@parrot.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Matteo Mattei <matteo.mattei@gmail.com>,
	Matthieu Castet <matthieu.castet@parrot.com>
Subject: Re: UBI/UBIFS issue: corrupt empty space => switched to read-only mode
Date: Tue, 17 Apr 2012 10:48:30 +0200	[thread overview]
Message-ID: <20120417084830.GA4421@parrot.com> (raw)
In-Reply-To: <1334406762.2263.35.camel@koala>

On Sat, Apr 14, 2012 at 01:32:40PM +0100, Artem Bityutskiy wrote:
> On Sat, 2012-04-14 at 14:11 +0200, Ivan Djelic wrote:
> > On Fri, Apr 13, 2012 at 04:20:45PM +0100, Artem Bityutskiy wrote:
> > > > > On Fri, 2012-03-16 at 17:14 +0100, Matteo Mattei wrote:
> > > > > > Hi guys,
> > > > > > 
> > > > > > I am working hard on UBIFS to make it works on 2.6.32 and OMAP3530.
> > > > > > 
> > > > > > I already posted some requests to TI forum but I have no answers up to now:
> > > > > > http://e2e.ti.com/support/embedded/linux/f/354/t/171839.aspx#627875
> > 
> > Hello Matteo,
> > 
> > I have been using a very similar setup (2.6.32 + OMAP3630), and I added BCH support
> > (8-bit correction) to the mtd omap2 driver, using the BCH library (not TI implementation).
> > My patch corrects bitflips on empty space (erased pages), so that UBIFS does not choke on corrupted empty space.
> > 
> > I posted a patch a while ago, albeit for a more recent kernel version:
> > http://lists.infradead.org/pipermail/linux-mtd/2011-October/038207.html
> > bit I did not get much feedback from TI maintainers.
> > 
> > If you have some trouble backporting this patch to your kernel, let me know, I may
> > have an old 2.6.32 version of the patch somewhere on my hdd :).
> 
> If we have a "tested-by" - we can make them go in via the MTD tree. It
> looks like Matthieu successfully tested them?

Yes; I guess I'll need to submit a patch to linux-omap first, because OMAP GPMC related code
(needed for ecc) has been moved from the mtd driver to arch/arm/mach-omap2.
Also, I wrote the patch for 2.6.35, and I don't have much resources to run it on a recent
kernel. If Matteo or anybody interested could test it, that would be great.

BR,
--
Ivan

      reply	other threads:[~2012-04-17  8:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 16:14 UBI/UBIFS issue: corrupt empty space => switched to read-only mode Matteo Mattei
2012-03-19  9:28 ` Matteo Mattei
2012-03-20 10:40   ` Artem Bityutskiy
2012-03-20 10:39 ` Artem Bityutskiy
2012-03-29 15:48   ` Matteo Mattei
2012-03-29 16:28     ` Matthieu CASTET
2012-04-13 15:20     ` Artem Bityutskiy
2012-04-14 12:11       ` Ivan Djelic
2012-04-14 12:32         ` Artem Bityutskiy
2012-04-17  8:48           ` Ivan Djelic [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=20120417084830.GA4421@parrot.com \
    --to=ivan.djelic@parrot.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=matteo.mattei@gmail.com \
    --cc=matthieu.castet@parrot.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