From: Woody Wu <narkewoody@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Block numbers of BEB
Date: Mon, 06 Oct 2014 15:41:53 +0700 [thread overview]
Message-ID: <22ddcb2d-d790-4e3e-af60-6bae0465295a@email.android.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1410060950270.17221@lnxricardw1.se.axis.com>
On October 6, 2014 2:53:01 PM GMT+07:00, Ricard Wanderlof <ricard.wanderlof@axis.com> wrote:
>
>On Sun, 5 Oct 2014, Woody Wu wrote:
>
>> What I said of checking /proc is wrong. What I indeed checked was
>> /sys/class/ubi as you mentioned. The problem is, under the
>> /sys/class/ubi, there is no information about what blocks are marked
>as
>> bad, there is only information about the total number of bad blocks.
>
>I was thinking the mtd tool nanddump displayed which blocks were bad
>when
>dumping, but a quick test just now revealed that that doesn't seem to
>be
>the case.
>
>The information is available to userspace though, so it's fairly easy
>to
>hack together a userspace tool that gets the bad block information via
>ioctls.
Do you know in what kernel .c file that contain the information? Is it in mtd or ubi?
>
>/Ricard
--
sent from mobile
next prev parent reply other threads:[~2014-10-06 8:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 6:04 Block numbers of BEB Woody Wu
2014-10-05 15:41 ` Richard Weinberger
2014-10-05 15:49 ` Woody Wu
2014-10-05 15:53 ` Richard Weinberger
2014-10-05 15:58 ` Woody Wu
2014-10-05 16:00 ` Richard Weinberger
2014-10-05 16:17 ` Woody Wu
2014-10-05 16:21 ` Richard Weinberger
2014-10-05 16:40 ` Woody Wu
2014-10-06 7:53 ` Ricard Wanderlof
2014-10-06 8:41 ` Woody Wu [this message]
2014-10-06 8:59 ` Ricard Wanderlof
2014-10-06 11:25 ` Woody Wu
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=22ddcb2d-d790-4e3e-af60-6bae0465295a@email.android.com \
--to=narkewoody@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.com \
--cc=richard.weinberger@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