From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] NAND: Updating the NAND README
Date: Tue, 01 Dec 2009 17:38:26 -0600 [thread overview]
Message-ID: <4B15A8F2.7060107@freescale.com> (raw)
In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D945E4865@dlee01.ent.ti.com>
Paulraj, Sandeep wrote:
>>> +At this point of time it appears as if the entire common folder
>>> +needs to be updated with 64 bit values.
>> Yeah... If you want to put a concise note about this here, I'll add it,
>> though an actual bug tracking system would be nice. :-)
>
> Again let me know what sections are not required.
>> -Scott
>
> I'll send an updated patch after your reply.
Just keep it short and simple. Maybe something like:
64-bit offsets (i.e. devices which are 4GiB or larger) are not yet fully
supported -- in particular, the code in common/cmd_nand.c and
common/env_nand.c will have problems.
-Scott
prev parent reply other threads:[~2009-12-01 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 18:06 [U-Boot] [PATCH] NAND: Updating the NAND README s-paulraj at ti.com
2009-12-01 23:28 ` Scott Wood
2009-12-01 23:33 ` Paulraj, Sandeep
2009-12-01 23:38 ` 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=4B15A8F2.7060107@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox