public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Manning <manningc2@actrix.gen.nz>
To: Luca Ceresoli <luca@lucaceresoli.net>
Cc: linux-omap@vger.kernel.org, notasas@gmail.com
Subject: Re: UbiFS + HWECC(?) + BeagleBoard = fail
Date: Wed, 8 Dec 2010 13:19:24 +1300	[thread overview]
Message-ID: <201012081319.24319.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <LD1ZTZ$A8E18B744A1EDB29645809E1CAA11B96@aruba.it>

On Tuesday 07 December 2010 23:29:59 Luca Ceresoli wrote:
> Luca Ceresoli wrote:
> > While I thank you for you proposed solution, I see it does not work here.
> > In fact I commented the #define CONFIG_MTD_NAND_OMAP_HWECC and left
> > MTD_NAND_OMAP_PREFETCH disabled as it previously was, and got compilation
> > errors:
>
> Wrong, sorry. Your solution compiles and works. I had another change in
> that file that broke compilation.

Luca, I have been having similar problems on a hacked Overo kernel.

I have no problems with 2.6.35.

I tried just commenting out the define and disabling PREFETCH and did not get 
a good boot due to ubi not finding the volume info.

Are you loading up a UBI image with uboot?

Are you using the ubi volume as rootfs?

>
> Nevertheless, it's not clear to me whether the long-term direction is to
> switch to HWECC, and if it is expected to work in current builds, or if
> SWECC in here to stay.
>

Clearly HWECC has some advantages, but UBI and HWECC need some effort to get 
working together.

-- Charles

  reply	other threads:[~2010-12-08  0:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 10:29 UbiFS + HWECC(?) + BeagleBoard = fail Luca Ceresoli
2010-12-08  0:19 ` Charles Manning [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-09  8:30 Luca Ceresoli
2010-12-15  4:13 ` Charles Manning
2010-12-15 17:35   ` Charles Manning
2010-12-06 17:51 Luca Ceresoli
2010-11-07  7:40 [AvataR]
2010-11-08 11:08 ` Grazvydas Ignotas

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=201012081319.24319.manningc2@actrix.gen.nz \
    --to=manningc2@actrix.gen.nz \
    --cc=linux-omap@vger.kernel.org \
    --cc=luca@lucaceresoli.net \
    --cc=notasas@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