From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] SPEAr: Configure FSMC driver for NAND interface
Date: Wed, 29 Feb 2012 12:03:20 -0600 [thread overview]
Message-ID: <4F4E6868.2020403@freescale.com> (raw)
In-Reply-To: <4F4DF9D5.4070001@st.com>
On 02/29/2012 04:11 AM, Amit Virdi wrote:
> Hello Scott,
>
> On 2/28/2012 4:02 AM, Scott Wood wrote:
>> On 02/27/2012 04:02 AM, Stefan Roese wrote:
> [...]
>>>
>>> You also need the following define for this to work with the latest NAND
>>> subsystem:
>>>
>>> #define CONFIG_MTD_ECC_SOFT
>>>
>>> Not sure about SPEAr3xx. Most likely this needs it as well.
>>
>> This is going to be reverted for now -- I meant to leave it out of the
>> last patchset because of the need to update all boards (which the patch
>> did not do).
>>
>
> Sorry, I didn't get you. Could you please elaborate?
It was intended to reduce U-Boot code size in cases where soft ECC is
not needed. However, the patch that introduced it did not update the
boards to select it when necessary, so it is being reverted for now.
It can be resubmitted with proper documentation and board config file
updates.
-Scott
next prev parent reply other threads:[~2012-02-29 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 9:38 [U-Boot] [PATCH 0/3] mtd/NAND: Support for FSMC controller Amit Virdi
2012-02-27 9:38 ` [U-Boot] [PATCH 1/3] mtd/NAND: Add FSMC driver support Amit Virdi
2012-03-01 21:27 ` Scott Wood
2012-03-02 11:16 ` Amit Virdi
2012-03-05 23:39 ` Scott Wood
2012-02-27 9:38 ` [U-Boot] [PATCH 2/3] SPEAr: Configure FSMC driver for NAND interface Amit Virdi
2012-02-27 10:02 ` Stefan Roese
2012-02-27 10:15 ` Amit Virdi
2012-02-27 22:32 ` Scott Wood
2012-02-29 10:11 ` Amit Virdi
2012-02-29 18:03 ` Scott Wood [this message]
2012-03-02 11:24 ` Amit Virdi
2012-03-02 13:44 ` Stefan Roese
2012-03-02 17:19 ` Scott Wood
2012-02-29 10:09 ` Amit Virdi
2012-02-27 9:38 ` [U-Boot] [PATCH 3/3] mtd/NAND: Remove obsolete SPEAr specific NAND drivers Amit Virdi
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=4F4E6868.2020403@freescale.com \
--to=scottwood@freescale.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 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.