From: Sascha Hauer <s.hauer@pengutronix.de>
To: Richard Weinberger <richard@nod.at>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
linux-mtd@lists.infradead.org, kernel@pengutronix.de,
Daniel Walter <dwalter@sigma-star.at>
Subject: Re: Pass -EUCLEN to userspace?
Date: Mon, 25 Apr 2016 07:28:57 +0200 [thread overview]
Message-ID: <20160425052857.GA7860@pengutronix.de> (raw)
In-Reply-To: <571A47D3.6040602@nod.at>
On Fri, Apr 22, 2016 at 05:48:35PM +0200, Richard Weinberger wrote:
> Sascha, Boris,
>
> Am 22.04.2016 um 17:28 schrieb Boris Brezillon:
> >>> I am currently working on a program similar to ubihealthd, just for raw
> >>> mtd pages, not UBI. Basically I want to find out in userspace if my Nand needs
> >>> scrubbing. Is it possible somehow to get this information in userspace?
> >>
> >> Actually we discussed that a year ago with Richard. I told him that we
> >> should put the read/write/erase statistics at the MTD level so that
> >> other MTD users (including userspace programs) could use the same infra
> >> for non-UBI partitions (I need that for the UBOOT and SPL partitions).
> >>
> >> My suggestion was to store those information at the MTD level, and let
> >> UBI implement its own scrubbing layer on top of that, but Richard
> >> decided to go for a simpler approach for its first implementation.
>
> Yeah, I did a first implementation on UBI layer as it had everything we need
> and I didn't want to replicate UBI at MTD level.
> Another reason is that we were not sure how sophisticated ubihealthd needs to be.
>
> Sasha, what exactly is your use case and why is the UBI approach not sufficient for you?
> On Linux MTD access should only happen through UBI and UBOOT/SPL partitions stay untouched.
On i.MX6 the Bootloader in Nand can indeed be redundant, so it's
possible to scrub the pages. This is exactly our usecase, we want to be
able to detect bitflips in the bootloader area.
Note that on i.MX6 the first page in the first n blocks on Nand contains
a structure called FCB (flash control block). This is not encoded with
the standard ECC algorithm used on the other areas in Nand. Reading
these pages will always return -EBABDMSG, they have to be read in raw
mode. That just to say that a "maximum bitflips per block" might not be
sufficient.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2016-04-25 5:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 13:25 Pass -EUCLEN to userspace? Sascha Hauer
2016-04-22 15:24 ` Boris Brezillon
2016-04-22 15:28 ` Boris Brezillon
2016-04-22 15:48 ` Richard Weinberger
2016-04-22 16:11 ` Boris Brezillon
2016-04-22 18:20 ` Richard Weinberger
2016-04-22 18:39 ` Boris Brezillon
2016-04-25 5:28 ` Sascha Hauer [this message]
2016-04-25 7:50 ` Boris Brezillon
2016-04-25 8:22 ` Sascha Hauer
2016-04-25 8:40 ` Boris Brezillon
2016-04-25 9:14 ` Sascha Hauer
2016-04-25 9:26 ` Boris Brezillon
2016-04-25 14:11 ` Boris Brezillon
2016-04-26 7:13 ` Pass -EUCLEAN " Sascha Hauer
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=20160425052857.GA7860@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=boris.brezillon@free-electrons.com \
--cc=dwalter@sigma-star.at \
--cc=kernel@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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