From: Helmut Raiger <helmut.raiger@hale.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mxc_nand: fix a problem writing more than 32MB
Date: Wed, 20 Jul 2011 08:55:00 +0200 [thread overview]
Message-ID: <4E267BC4.8040608@hale.at> (raw)
In-Reply-To: <1309971881-3797-1-git-send-email-helmut.raiger@hale.at>
On 07/06/2011 07:04 PM, helmut.raiger at hale.at wrote:
> From: Helmut Raiger<helmut.raiger@hale.at>
>
> When writing 0x4000 to the unlockend_blkaddr register, large writes to
> a 2k page NAND sometimes fail. The current kernel driver writes 0xFFFF
> to this register for V2 of the nand controller.
>
> However on an i.MX31 this also fixes writes larger than 32MB.
> The datasheet is very unspecific, but (0x4000=16384)*2000
> roughly fits the limits we're encountering with NAND writes.
> This problem might be NAND chip specific.
Any comments?
Helmut
--
Scanned by MailScanner.
next prev parent reply other threads:[~2011-07-20 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 17:04 [U-Boot] [PATCH] mxc_nand: fix a problem writing more than 32MB helmut.raiger at hale.at
2011-07-20 6:55 ` Helmut Raiger [this message]
2011-07-20 17:53 ` Scott Wood
2011-08-02 20:12 ` Scott Wood
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=4E267BC4.8040608@hale.at \
--to=helmut.raiger@hale.at \
--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