All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Troy Kisky <troy.kisky@boundarydevices.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/5] mtd: nand: move layout structure into nand_ecc_ctrl
Date: Thu, 14 May 2009 11:08:07 -0700	[thread overview]
Message-ID: <200905141108.08113.david-b@pacbell.net> (raw)
In-Reply-To: <4A0C5A8F.10908@boundarydevices.com>

On Thursday 14 May 2009, Troy Kisky wrote:
> David Brownell wrote:
> > On Wednesday 13 May 2009, Troy Kisky wrote:
> >> +static const struct nand_ecclayout atmel_oobinfo_large __initdata = {
> > 
> > Doesn't this give you section warnings?  __initconst is what
> > I usually end up needing in such cases...
> 
> Only if the same file has a non const __initdata variable.
> Is __initconst the preferred method ?

Yes; it will always work, but __initdata won't always work.


> > Also, for the davinci_nand driver this is going to need to
> > switch away from the ecclayout struct in the driver-private
> > area ... that's in a patch that (still) hasn't merged into
> > the MTD tree, but was stored there for the same reason that
> > you're submitting this patch:  the original code, using the
> > annoying ECC_HW_SYNDROME support, computed the layout.
> > 
> > - Dave
> 
> Is ECC_HW_SYNDROME only needed because the eccpos array is too small??

No; it uses different algorithms to read/write, which
completely ignore ecclayout.  AFAICT ECC_HW_SYNDROME is
largely unused/untested except for single-chunk mode.

The size issue is that a 4-bit ECC code producing 10 bytes
of ECC per 512 bytes of data needs 80 bytes with 4K pages,
which obviously can't fit into the 64 bytes in ecclayout.

- Dave


> I'll have to review that prepad  and ECC_HW_SYNDROME
> Thanks
> 
> Troy
> 
> 

  reply	other threads:[~2009-05-14 18:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1242270008-1552-1-git-send-email-troy.kisky@boundarydevices.com>
2009-05-14  4:42 ` [PATCH 1/5] mtd: nand: move layout structure into nand_ecc_ctrl David Brownell
2009-05-14 17:53   ` Troy Kisky
2009-05-14 18:08     ` David Brownell [this message]
     [not found] ` <1242270008-1552-2-git-send-email-troy.kisky@boundarydevices.com>
2009-05-14  5:10   ` [PATCH 2/5] mtd: nand: Calculate better default ecc layout David Brownell
2009-05-14 17:59     ` Troy Kisky
     [not found]   ` <1242270008-1552-3-git-send-email-troy.kisky@boundarydevices.com>
2009-05-14  5:12     ` [PATCH 3/5] mtd: nand: atmel: use " David Brownell
2009-05-14  8:23       ` Haavard Skinnemoen
2009-05-14 18:08         ` Troy Kisky
2009-05-15  7:26           ` Richard Genoud
2009-05-15 19:57             ` Richard Genoud
2009-05-15 22:15               ` Troy Kisky
2009-05-15 22:38                 ` Richard Genoud
2009-05-15 23:04                   ` Troy Kisky
2009-05-14 18:04       ` Troy Kisky
2009-05-20 15:19       ` Nicolas Ferre
2009-05-20 18:28         ` Troy Kisky
     [not found]     ` <1242270008-1552-4-git-send-email-troy.kisky@boundarydevices.com>
2009-05-14  5:18       ` [PATCH 4/5] mtd: nand: cafe_nand: " David Brownell
2009-05-14 21:18         ` Troy Kisky

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=200905141108.08113.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-mtd@lists.infradead.org \
    --cc=troy.kisky@boundarydevices.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.