public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC/PATCH 0/4] BCH8 support for OMAP3
Date: Thu, 28 Mar 2013 11:49:54 +0100	[thread overview]
Message-ID: <51542052.9020905@gmail.com> (raw)
In-Reply-To: <1353683657-23496-1-git-send-email-andreas.devel@googlemail.com>

On 11/23/2012 04:14 PM, Andreas Bie?mann wrote:
> This RFC series implements BCH8 for OMAP3 as provided by linux kernel in commit
> 0e618ef0a6a33cf7ef96c2c824402088dd8ef48c.
> This series is heavily influenced by Ilyas series 'NAND support for AM33XX'
> thus could share some code.

Any comments on that series? I would appreciate to get the BCH8 support
in for at least the tricorder board.

> I have managed to load kernel from an ubifs written by the kernel driver, but is
> far away from tested thoroughly.

We used that patchset for a while in-house and could not find obvious
issues. However we need to hack the SPL a bit to get the bigger
footprint into SRAM with 2013.01.
I would really appreciate if some other omap users could test it.
One thing is that most current NAND (even SLC) devices require at least
4Bit ecc for most sections.

> Cause my NAND device 'NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron
> NAND 512MiB 1,8V 16-bit)' does support 1bit ECC for first sector if erase is
> less than 1000, the rest requires 4bit ECC. Therefore the SPL needs to support
> BCH, the impact is about 9k for the SPL.

So my question here is if this series would be accepted for the upcoming
release. I could work on it next week full time, so if I get a go for
this release I would do so.

Best regards

Andreas Bie?mann

  parent reply	other threads:[~2013-03-28 10:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 15:14 [U-Boot] [RFC/PATCH 0/4] BCH8 support for OMAP3 Andreas Bießmann
2012-11-23 15:14 ` [U-Boot] [RFC/PATCH 1/4] omap3/cpu.h: add BCH support Andreas Bießmann
2012-11-23 15:14 ` [U-Boot] [RFC/PATCH 2/4] omap3/omap_gpmc.h: add ooblayout for BCH8 as in kernel Andreas Bießmann
2012-11-23 15:14 ` [U-Boot] [RFC/PATCH 3/4] omap_gpmc: add support for hw assisted BCH8 Andreas Bießmann
2012-11-26 21:09   ` Scott Wood
2012-11-23 15:14 ` [U-Boot] [RFC/PATCH 4/4] tricorder: enable hw assisted BCH8 in SPL and u-boot Andreas Bießmann
2013-03-28 10:49 ` Andreas Bießmann [this message]
2013-03-28 14:21   ` [U-Boot] [RFC/PATCH 0/4] BCH8 support for OMAP3 Tom Rini
2013-04-02  8:49     ` Andreas Bießmann
2013-04-02 16:13       ` Tom Rini
2013-04-02 16:05 ` [U-Boot] [PATCH v2 1/6] omap3/cpu.h: add BCH support Andreas Bießmann
2013-04-02 16:05   ` [U-Boot] [PATCH v2 2/6] asm/omap_gpmc.h: consolidate common defines Andreas Bießmann
2013-04-02 21:19     ` Tom Rini
2013-04-02 16:05   ` [U-Boot] [PATCH v2 3/6] omap3/omap_gpmc.h: add ooblayout for BCH8 as in kernel Andreas Bießmann
2013-04-02 21:19     ` Tom Rini
2013-04-02 16:05   ` [U-Boot] [PATCH v2 4/6] omap_gpmc: change nandecc command Andreas Bießmann
2013-04-02 21:19     ` Tom Rini
2013-04-03 14:50     ` [U-Boot] [PATCH v3 " Andreas Bießmann
2013-04-03 14:50       ` [U-Boot] [PATCH v3 5/6] omap_gpmc: add support for hw assisted BCH8 Andreas Bießmann
2013-04-05  8:13         ` Thomas Weber
2013-04-05  9:15           ` Andreas Bießmann
2013-04-05 11:44         ` Thomas Weber
2013-04-05 13:42           ` Andreas Bießmann
2013-04-05 14:55           ` [U-Boot] [PATCH v4 " Andreas Bießmann
2013-04-05  9:52       ` [U-Boot] [PATCH v4 4/6] omap_gpmc: change nandecc command Andreas Bießmann
2013-04-05 11:48         ` Thomas Weber
2013-04-05 13:39           ` Andreas Bießmann
2013-04-02 16:05   ` [U-Boot] [PATCH v2 5/6] omap_gpmc: add support for hw assisted BCH8 Andreas Bießmann
2013-04-02 21:19     ` Tom Rini
2013-04-02 16:05   ` [U-Boot] [PATCH v2 6/6] tricorder: enable hw assisted BCH8 in SPL and u-boot Andreas Bießmann
2013-04-02 21:19   ` [U-Boot] [PATCH v2 1/6] omap3/cpu.h: add BCH support Tom Rini
2013-04-08 16:58   ` 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=51542052.9020905@gmail.com \
    --to=andreas.devel@googlemail.com \
    --cc=u-boot@lists.denx.de \
    /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