public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: omap: cm_t35: Fix: Re-add GPMC_NAND_ECC_LP_x8_LAYOUT
Date: Tue, 11 Mar 2014 19:42:28 +0200	[thread overview]
Message-ID: <531F4B04.80208@compulab.co.il> (raw)
In-Reply-To: <1394553885-7680-1-git-send-email-sr@denx.de>


On 03/11/14 18:04, Stefan Roese wrote:
> Patch a7e36fc9 (mtd: nand: omap: remove unused #defines from common
> omap_gpmc.h) removed some MTD related defines. Including
> GPMC_NAND_ECC_LP_x8_LAYOUT. But this define is also needed for the
> memory controller configuration (only the x8 defines are needed,
> the x16 defines are the default). Without it the NAND subsystem is
> not configured correctly and booting into U-Boot does not work.
> 
> Signed-off-by: Stefan Roese <sr@denx.de>
> Cc: Pekon Gupta <pekon@ti.com>
> Cc: Nikita Kiryanov <nikita@compulab.co.il>
> Cc: Igor Grinberg <grinberg@compulab.co.il>
> Cc: Tom Rini <trini@ti.com>

Acked-by: Igor Grinberg <grinberg@compulab.co.il>

> ---
>  include/configs/cm_t35.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/include/configs/cm_t35.h b/include/configs/cm_t35.h
> index cfc4f9b..aae05e0 100644
> --- a/include/configs/cm_t35.h
> +++ b/include/configs/cm_t35.h
> @@ -158,6 +158,8 @@
>  							/* CS0 */
>  #define CONFIG_SYS_MAX_NAND_DEVICE	1		/* Max number of NAND */
>  							/* devices */
> +#define GPMC_NAND_ECC_LP_x8_LAYOUT
> +
>  /* Environment information */
>  #define CONFIG_BOOTDELAY		3
>  #define CONFIG_ZERO_BOOTDELAY_CHECK
> 

-- 
Regards,
Igor.

  reply	other threads:[~2014-03-11 17:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11 16:04 [U-Boot] [PATCH] arm: omap: cm_t35: Fix: Re-add GPMC_NAND_ECC_LP_x8_LAYOUT Stefan Roese
2014-03-11 17:42 ` Igor Grinberg [this message]
2014-03-12 20:04 ` [U-Boot] " Tom Rini
2014-03-13 11:49 ` [U-Boot] [PATCH] " Gupta, Pekon
2014-03-13 11:59   ` Stefan Roese

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=531F4B04.80208@compulab.co.il \
    --to=grinberg@compulab.co.il \
    --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