From: Artem Bityutskiy <dedekind1@gmail.com>
To: twebb <taliaferro62@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubi attach failure
Date: Sun, 10 Jan 2010 13:34:44 +0200 [thread overview]
Message-ID: <1263123284.30988.5.camel@localhost.localdomain> (raw)
In-Reply-To: <dbdb2ea61001051516n4eb50374m809720d68c214cba@mail.gmail.com>
On Tue, 2010-01-05 at 18:16 -0500, twebb wrote:
> I get the error shown below when attempting to attach to an mtd device
> on a Marvell PXA-based platform. The flash is MLC NAND from Samsung
> K9LBG08U0D (4G x 8-bit).
>
> I don't know if it's related, but one thing that stands out is that I
> only see the error on two platforms whose bad block table has >28
> entries (other tested boards have approx. 2-8 bad blocks).
>
> Any suggestion as to what would cause error and whether it may be
> related to the high number of bad blocks?
What did you use to flash your image? It looks like it was not flashed
properly.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-01-10 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 23:16 ubi attach failure twebb
2010-01-10 11:34 ` 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=1263123284.30988.5.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=taliaferro62@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox