linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maramaopercheseimorto@gmail.com (Alberto Panizzo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mx31pdk: Add NAND support
Date: Thu, 25 Feb 2010 12:12:13 +0100	[thread overview]
Message-ID: <1267096333.2722.44.camel@realization> (raw)
In-Reply-To: <48285.22454.qm@web51005.mail.re2.yahoo.com>

Hi Fabio,

On mer, 2010-02-24 at 16:58 -0800, Fabio Estevam wrote:
> Add NAND support to MX31PDK board.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  arch/arm/mach-mx3/mach-mx31_3ds.c |    7 +++++++
>  1 files changed, 7 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/arm/mach-mx3/mach-mx31_3ds.c b/arch/arm/mach-mx3/mach-mx31_3ds.c
> index b88c18a..2d78754 100644
> --- a/arch/arm/mach-mx3/mach-mx31_3ds.c
> +++ b/arch/arm/mach-mx3/mach-mx31_3ds.c
> @@ -34,6 +34,7 @@
>  #include <mach/board-mx31pdk.h>
>  #include <mach/imx-uart.h>
>  #include <mach/iomux-mx3.h>
> +#include <mach/mxc_nand.h>
>  #include "devices.h"
>  
>  /*!
> @@ -80,6 +81,11 @@ static struct resource smsc911x_resources[] = {
>  	},
>  };
>  
> +static struct mxc_nand_platform_data mx31pdk_nand_board_info = {
> +	.width = 1,
> +	.hw_ecc = 1,
> +};
> +

Are you sure that this works? Don't you see a lot of Bad blocks reports
in boot messages?


-- 
Alberto!

        Be Persistent!
                - Greg Kroah-Hartman (FOSDEM 2010)

  parent reply	other threads:[~2010-02-25 11:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25  0:58 [PATCH] mx31pdk: Add NAND support Fabio Estevam
2010-02-25 10:58 ` Alberto Panizzo
2010-02-25 22:09   ` Fabio Estevam
2010-02-26  9:36     ` Uwe Kleine-König
2010-02-26 10:19       ` Alberto Panizzo
2010-02-26 10:46         ` Uwe Kleine-König
2010-02-26 11:05           ` Alberto Panizzo
2010-02-26 13:14             ` Ivo Clarysse
2010-02-25 11:12 ` Alberto Panizzo [this message]
2010-02-25 21:59   ` Fabio Estevam
2010-02-25 22:19     ` Alberto Panizzo
2010-02-26  9:56     ` Juergen Beisert
2010-02-26 10:33       ` Alberto Panizzo
2010-02-26 11:48         ` Juergen Beisert
2010-02-26 13:29           ` Alberto Panizzo
2010-02-26 13:40             ` Juergen Beisert
2010-02-27  1:34 ` Fabio Estevam
2010-02-27 14:25   ` Alberto Panizzo
2010-02-27 15:38     ` Fabio Estevam
2010-02-27 16:17       ` Alberto Panizzo
  -- strict thread matches above, loose matches on Subject: below --
2010-02-25 22:22 Fabio Estevam
2010-02-25 22:33 ` Alberto Panizzo
2010-02-25 22:52   ` Fabio Estevam

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=1267096333.2722.44.camel@realization \
    --to=maramaopercheseimorto@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).