From: Artem Bityutskiy <dedekind1@gmail.com>
To: jmintern@datacast.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Reporting nand bad blocks in Linux
Date: Thu, 02 Sep 2010 02:28:03 +0300 [thread overview]
Message-ID: <1283383683.2209.69.camel@brekeke> (raw)
In-Reply-To: <4C7E4540.9040203@datacast.com>
On Wed, 2010-09-01 at 08:21 -0400, Jonne Mintern wrote:
> To report nand bad blocks, I have been using cmd 'nand bad' from
> uboot. What Linux cmd will get thesame report from a Linux prompt? I'm
> using Denx eldk4.2 on an AMCC PPC440EPx. I'm not sure what nand chip.
Hmm, I think this utility does not exist, and you need to implement it,
but I am not 100% sure.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-09-01 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 12:21 Reporting nand bad blocks in Linux Jonne Mintern
2010-09-01 23:28 ` Artem Bityutskiy [this message]
2010-09-02 11:52 ` Jonne Mintern
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=1283383683.2209.69.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=jmintern@datacast.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).