public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: linux-mtd@lists.infradead.org
Subject: Re: [RFC] Handling of errors for AMD NOR (cfi_cmdset_0002) chips
Date: Fri, 11 Mar 2011 09:25:52 +0100	[thread overview]
Message-ID: <4D79DC90.6070600@aimvalley.nl> (raw)
In-Reply-To: <4D797E23.6070409@emcraft.com>

On 03/11/11 02:42, Ilya Yanok wrote:
> Hello,
>
> current cfi_cmdset_0002.c code does not implement handling of error statuses reported by the chip during write/erase and just waits for a software timeout instead.
>
> We think that proper handling of these conditions could help us to debug the issue we have with the NOR flash and UBIFS so we'd like to implement such handling.
>
> I've tried to do this, please see my initial patch below. For now errors are just reported via pr_debug().
>
> I'd like to hear any comments. Am I doing things right or not? Maybe I'm missing something?
>


What issue you have with NOR flash and UBIFS ?

---
N. van Bolhuis.

  reply	other threads:[~2011-03-11  8:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11  1:42 [RFC] Handling of errors for AMD NOR (cfi_cmdset_0002) chips Ilya Yanok
2011-03-11  8:25 ` Norbert van Bolhuis [this message]
2011-03-23 15:47   ` Detlev Zundel
2011-03-23 17:33     ` Artem Bityutskiy
2011-03-24  7:35     ` Norbert van Bolhuis
2011-03-24  9:27       ` Detlev Zundel
2011-03-24 10:48         ` Norbert van Bolhuis
2011-03-15  8:01 ` Markus Niebel
2011-03-23 16:16   ` Detlev Zundel
2011-03-23 18:27   ` Ilya Yanok
2011-03-24  7:45 ` Alexander Stein
2011-03-24  7:55   ` Artem Bityutskiy

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=4D79DC90.6070600@aimvalley.nl \
    --to=nvbolhuis@aimvalley.nl \
    --cc=linux-mtd@lists.infradead.org \
    /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