All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Correct corrupted NAND Flash access on KARO TX25 modules
Date: Fri, 6 Apr 2012 15:16:21 -0500	[thread overview]
Message-ID: <4F7F4F15.4040203@freescale.com> (raw)
In-Reply-To: <4F7AECE3.60406@denx.de>

On 04/03/2012 07:28 AM, Stefano Babic wrote:
> On 03/04/2012 07:26, Gachet Daniel wrote:
>> Hi Stefano,
>
> Hi Daniel,
>
>>
>> No problem, I will do it with the inverse logic, using a
>> CONFIG_NAND_MXC_NFC_TWO_CYCLES, and adapt the tx25.h file. But could
>> you tell me in which README file I should add the description for
>> that switch? I have a look at all README, but no one has any
>> description about NAND flash configuration flags (like
>> CONFIG_NAND_MXC, CONFIG_NAND_MXC_V1_1  or CONFIG_MXC_NAND_HWECC).
>
> You have found missing documentation ;-(. Maybe it was not checked
> before, but you're right: there is no documentation for this driver.
> Even worse, there is no "NAND Support" at all.
>
> Please feel free to add a section. I think the right place is under "Low
> Level (hardware related) configuration options", adding a part for the
> MXC Nand driver. And if you want to integrate it with the missing
> documentation for the other CONFIG_NAND_MXC options, it will be highly
> appreciated.

There is doc/README.nand that would be appropriate for this, or it could 
go in an MXC-specific file.

-Scott

      reply	other threads:[~2012-04-06 20:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 20:55 [U-Boot] [PATCH v2] Correct corrupted NAND Flash access on KARO TX25 modules Gachet Daniel
2012-04-02 21:08 ` Marek Vasut
2012-04-02 21:56   ` stefano babic
2012-04-02 21:54 ` stefano babic
2012-04-03  5:26   ` Gachet Daniel
2012-04-03 12:28     ` Stefano Babic
2012-04-06 20:16       ` Scott Wood [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=4F7F4F15.4040203@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.