From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cfi_flash: don't hide write/erase errors
Date: Mon, 06 Oct 2014 14:09:51 +0200 [thread overview]
Message-ID: <5432868F.9000604@denx.de> (raw)
In-Reply-To: <20141006113229.GC4299@sapphire.tkos.co.il>
On 06.10.2014 13:32, Baruch Siach wrote:
>> Could you please summarize again, what the real problem with this compare
>> is. What is the error exactly in your case (which flash chip is used and
>> which command was issued?)?
>
> The Micron StrataFlash datasheet says this on Status Register bit 7 (Device
> status):
>
> 0 = Device is busy; SR[9,8,6:1] are invalid, SR[0] is valid
> 1 = Device is ready; SR[9:8], SR[6:1] are valid
>
> This is was the original code behaviour, since your commit
> 79b4cda076069d04122f. This commit log explicitly says:
>
> * Changes/fixes for drivers/cfi_flash.c:
> We *should* check if there are any error bits if the previous call
> returned ERR_OK (Otherwise we will have output an error message in
> flash_status_check() already.) The original code would only check for
> error bits if flash_status_check() returns ERR_TIMEOUT.
> Patch by Marcus Hall, 23 Aug 2005
>
> Currently U-Boot is just silent about NOR flash write errors.
Okay. Thanks for the summary. I'll prepare a pull request.
Thanks,
Stefan
next prev parent reply other threads:[~2014-10-06 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 9:23 [U-Boot] [PATCH] cfi_flash: don't hide write/erase errors Baruch Siach
2014-10-06 6:19 ` Baruch Siach
2014-10-06 8:20 ` Stefan Roese
2014-10-06 11:32 ` Baruch Siach
2014-10-06 12:09 ` Stefan Roese [this message]
2014-10-06 16:28 ` Edward L Swarthout
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=5432868F.9000604@denx.de \
--to=sr@denx.de \
--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.