All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Lars Michael <lars.michael@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND device: all blocks bad after restart, how to recover?
Date: Thu, 31 Mar 2011 15:11:50 +0300	[thread overview]
Message-ID: <1301573510.2828.53.camel@localhost> (raw)
In-Reply-To: <759739.22764.qm@web30205.mail.mud.yahoo.com>

On Fri, 2011-03-25 at 07:03 -0700, Lars Michael wrote:
> We investigated more and have found that the FlexBus on the Coldfire
> can cause problems for the NAND device. When the FlexBus devices are
> removed
> the NAND device comes back to life, and is again accessible. So now I 
> can get back to the UBI part of the project :-)

Good! :-)

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2011-03-31 12:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.15984.1299679972.1534.linux-mtd@lists.infradead.org>
2011-03-09 16:39 ` NAND device: all blocks bad after restart, how to recover? Lars Michael
2011-03-10 13:06   ` Artem Bityutskiy
2011-03-25 14:03     ` Lars Michael
2011-03-31 12:11       ` Artem Bityutskiy [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=1301573510.2828.53.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=lars.michael@yahoo.com \
    --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 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.