From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mxsboot : Support of 224-bytes OOB area length
Date: Mon, 19 Jan 2015 09:10:29 +0100 [thread overview]
Message-ID: <54BCBBF5.2040702@denx.de> (raw)
In-Reply-To: <1420733682-6555-1-git-send-email-acoffignal@geral.com>
Hi Alexandre,
On 08/01/2015 17:14, Alexandre Coffignal wrote:
> Add support for the NAND Flash chip with page size of 4096+224-bytes OOB area length
>
> For example Micron MT29F4G08 NAND flash device defines a OOB area which is
> 224 bytes long (oobsize).
>
> Signed-off-by: Alexandre Coffignal <acoffignal@geral.com>
> ---
> tools/mxsboot.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tools/mxsboot.c b/tools/mxsboot.c
> index 90b2173..6d48cfb 100644
> --- a/tools/mxsboot.c
> +++ b/tools/mxsboot.c
> @@ -142,6 +142,9 @@ static inline uint32_t mx28_nand_get_ecc_strength(uint32_t page_data_size,
>
> if (page_oob_size == 218)
> return 16;
> +
> + if (page_oob_size == 224)
> + return 16;
> }
>
> return 0;
> @@ -269,6 +272,9 @@ static struct mx28_nand_fcb *mx28_nand_get_fcb(uint32_t size)
> } else if (nand_oobsize == 218) {
> fcb->ecc_block_n_ecc_type = 8;
> fcb->ecc_block_0_ecc_type = 8;
> + } else if (nand_oobsize == 224) {
> + fcb->ecc_block_n_ecc_type = 8;
> + fcb->ecc_block_0_ecc_type = 8;
> }
> }
I have not your use case, but it looks ok for me and I merge it.
Applied to -u-boot-imx, thanks !
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
prev parent reply other threads:[~2015-01-19 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 16:14 [U-Boot] [PATCH] mxsboot : Support of 224-bytes OOB area length Alexandre Coffignal
2015-01-19 8:10 ` Stefano Babic [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=54BCBBF5.2040702@denx.de \
--to=sbabic@denx.de \
--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 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.