From: Artem Bityutskiy <dedekind1@gmail.com>
To: Mike Dunn <mikedunn@newsguy.com>
Cc: Peter Horton <phorton@bitbox.co.uk>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2] MTD: modify mtd api to return bitflip info on read operations
Date: Mon, 05 Dec 2011 08:07:12 +0200 [thread overview]
Message-ID: <1323065234.2316.2.camel@koala> (raw)
In-Reply-To: <4EDB89E9.6070306@newsguy.com>
On Sun, 2011-12-04 at 06:55 -0800, Mike Dunn wrote:
> So you're thinking that the driver would supply both ecc_strength and
> "scrublevel" (or maybe bb_threshold)? Would these go into struct mtd_info?
Probably yes. After all, UBI has no idea about what kind of flash is
that and what kind of ECC it uses and what bit-flip level needs
scrubbing. So I think this kind of information should come from the
driver or from the user via mtd sysfs files. What do you think?
Artem.
next prev parent reply other threads:[~2011-12-05 6:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 20:20 [PATCH v2] MTD: modify mtd api to return bitflip info on read operations Mike Dunn
2011-12-04 8:43 ` Peter Horton
2011-12-04 13:52 ` Mike Dunn
2011-12-04 14:43 ` Artem Bityutskiy
2011-12-04 14:55 ` Mike Dunn
2011-12-05 6:07 ` Artem Bityutskiy [this message]
2011-12-05 16:58 ` Mike Dunn
2011-12-05 17:09 ` Peter Horton
2011-12-05 18:57 ` Mike Dunn
2011-12-06 21:52 ` Robert Jarzmik
2011-12-07 2:16 ` Mike Dunn
2011-12-07 8:01 ` Ricard Wanderlof
2011-12-07 18:32 ` Mike Dunn
2011-12-12 12:48 ` Artem Bityutskiy
2011-12-14 20:46 ` Mike Dunn
2011-12-16 10:09 ` Artem Bityutskiy
2011-12-07 9:42 ` Peter Horton
2011-12-07 18:33 ` Mike Dunn
2011-12-04 14:33 ` Artem Bityutskiy
2011-12-05 6:23 ` Artem Bityutskiy
2011-12-05 18:13 ` Mike Dunn
2011-12-05 21:16 ` Artem Bityutskiy
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=1323065234.2316.2.camel@koala \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mikedunn@newsguy.com \
--cc=phorton@bitbox.co.uk \
/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.