From: Fabio Estevam <fabioestevam@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/9] Nand mxc_nand add v1.1 controller support
Date: Thu, 14 Jan 2010 16:48:06 -0800 (PST) [thread overview]
Message-ID: <735134.6241.qm@web51002.mail.re2.yahoo.com> (raw)
In-Reply-To: <4b73d43f1001130850p6a5ea238q60f27f3ab380e382@mail.gmail.com>
Hi John,
--- On Wed, 1/13/10, John Rigby <jcrigby@gmail.com> wrote:
> From: John Rigby <jcrigby@gmail.com>
> Subject: Re: [U-Boot] [PATCH 4/9] Nand mxc_nand add v1.1 controller support
> To: "Fabio Estevam" <fabioestevam@yahoo.com>
> Cc: u-boot at lists.denx.de
> Date: Wednesday, January 13, 2010, 2:50 PM
> Fabio,
>
> Thanks for the input but there is a problem with your
> suggestion.? The
> kernel driver is in error.? I don't believe the driver
> as is will even
> work on i.MX25.? The register layout is wrong.? I
> can't go into all
> the details here but two quick examples I found are:
I am not talking about kernel driver functionality here. Only NAND controller revision naming.
...
> My understanding is that there really are 4 versions of the
> nfc ip 1,
> 1.1, 2 and 2.1.? The kernel driver is over simplifying
> the issue.
Are these NFC revision numbers for Freescale Power Architecture devices, such as MPC5121?
This is how the Freescale kernel names the NFC for different i.MX devices:
CONFIG_ARCH_MXC_HAS_NFC_V2_1 (For MX25 and MX35)
CONFIG_ARCH_MXC_HAS_NFC_V3_1 (For MX37)
CONFIG_ARCH_MXC_HAS_NFC_V3_2 (For MX51)
CONFIG_ARCH_MXC_HAS_NFC_V1 (For MX27 and MX31)
Regards,
Fabio Estevam
next prev parent reply other threads:[~2010-01-15 0:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 4:43 [U-Boot] [PATCH 0/9] Add support for i.MX25 SOC and TX25 board John Rigby
2010-01-13 4:43 ` [U-Boot] [PATCH 1/9] mxc_serial replace platform specific clock John Rigby
2010-01-13 4:43 ` [U-Boot] [PATCH 2/9] arm926ejs: add nand_spl boot support John Rigby
2010-01-13 4:43 ` [U-Boot] [PATCH 3/9] Add v1.1 support to nand_spl fsl nfc driver John Rigby
2010-01-13 4:43 ` [U-Boot] [PATCH 4/9] Nand mxc_nand add v1.1 controller support John Rigby
2010-01-13 4:43 ` [U-Boot] [PATCH 5/9] fec_mxc: cleanup and factor out imx27 dependencies John Rigby
2010-01-13 4:43 ` [U-Boot] [PATCH 6/9] Add support for Freescale MX25 SOC John Rigby
2010-01-13 4:43 ` [U-Boot] [PATCH 7/9] fec_mxc: add imx25 support John Rigby
2010-01-13 4:44 ` [U-Boot] [PATCH 8/9] env_nand.c: print error message and fail gracefully John Rigby
2010-01-13 4:44 ` [U-Boot] [PATCH 9/9] Add support for KARO TX25 board John Rigby
2010-01-13 15:26 ` Fabio Estevam
2010-01-15 15:20 ` Wolfgang Denk
2010-01-15 22:28 ` [U-Boot] [PATCH 8/9] env_nand.c: print error message and fail gracefully Scott Wood
2010-01-13 15:10 ` [U-Boot] [PATCH 4/9] Nand mxc_nand add v1.1 controller support Fabio Estevam
2010-01-13 16:50 ` John Rigby
2010-01-15 0:48 ` Fabio Estevam [this message]
2010-01-15 16:49 ` John Rigby
2010-01-15 22:36 ` Scott Wood
2010-01-15 23:32 ` John Rigby
2010-01-13 15:15 ` [U-Boot] [PATCH 3/9] Add v1.1 support to nand_spl fsl nfc driver Fabio Estevam
2010-01-15 23:13 ` Scott Wood
2010-01-15 23:30 ` John Rigby
2010-01-15 23:48 ` Scott Wood
2010-01-15 15:09 ` [U-Boot] [PATCH 0/9] Add support for i.MX25 SOC and TX25 board Wolfgang Denk
2010-01-15 15:14 ` Wolfgang Denk
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=735134.6241.qm@web51002.mail.re2.yahoo.com \
--to=fabioestevam@yahoo.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