All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
To: Shane Volpe <shanevolpe@gmail.com>
Cc: linux-mtd@lists.infradead.org,
	Adam Yergovich <ayergo@jkmicro.com>, Jon Ringle <jon@ringle.org>
Subject: Re: buffer write error (status 0x90)
Date: Wed, 25 Aug 2010 14:21:19 +0200	[thread overview]
Message-ID: <OF0FF7D4F4.BB0FA8ED-ONC125778A.0043A5C9-C125778A.0043DEAC@transmode.se> (raw)
In-Reply-To: <AANLkTin+Av3=MPjxFX12m9_T5T7fY7o11CmfxACdb_a5@mail.gmail.com>

Shane Volpe <shanevolpe@gmail.com> wrote on 2010/08/25 13:58:06:
>
> On Tue, Aug 24, 2010 at 7:18 PM, Joakim Tjernlund
> <joakim.tjernlund@transmode.se> wrote:
> > It states :
> > When customer uses [...] block unlock, the block lock status might be
> > altered inadvertently. Lock status might be set to either 01h or 03h
> > unexpectedly (00h as expected data), which leads to program/erase failure
> > on certain blocks.
> >
> > Easy to work around.
>
> Joakim,
> Do you have a patch or an example on how to work around this?
> Regards,
> Shane

See u-boot:
http://lists.denx.de/pipermail/u-boot/2010-August/075727.html

  reply	other threads:[~2010-08-25 12:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09 21:02 buffer write error (status 0x90) Jon Ringle
2010-08-09 21:21 ` Adam Yergovich
2010-08-10  3:46   ` Jon Ringle
2010-08-24 19:48     ` Shane Volpe
2010-08-24 23:18       ` Joakim Tjernlund
2010-08-25 11:58         ` Shane Volpe
2010-08-25 12:21           ` Joakim Tjernlund [this message]
2010-08-25 14:00             ` Shane Volpe
2010-08-25 14:08               ` Joakim Tjernlund

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=OF0FF7D4F4.BB0FA8ED-ONC125778A.0043A5C9-C125778A.0043DEAC@transmode.se \
    --to=joakim.tjernlund@transmode.se \
    --cc=ayergo@jkmicro.com \
    --cc=jon@ringle.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shanevolpe@gmail.com \
    /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.