From: Richard Weinberger <richard@nod.at>
To: "Bean Huo 霍斌斌 (beanhuo)" <beanhuo@micron.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: Alexander Kaplan <alex@nextthing.co>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
David Gstir <david@sigma-star.at>,
David Oberhollenzer <goliath@sigma-star.at>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [ANNOUNCE] MLC support for UBI/UBIFS
Date: Wed, 4 May 2016 11:18:41 +0200 [thread overview]
Message-ID: <5729BE71.5090708@nod.at> (raw)
In-Reply-To: <A765B125120D1346A63912DDE6D8B6310BF70101@NTXXIAMBX02.xacn.micron.com>
Bean,
Am 04.05.2016 um 10:55 schrieb Bean Huo 霍斌斌 (beanhuo):
> Hi, Richard
> Yes , different with "dis6 and dis3", but I think this is not a perfect
> Solution on paired-page distance detect. Because different vendor and different series NAND with different such paired-page distance function. as a result, this table will be bigger and bigger. I now want to do if we can probe this information from DTS.
Not sure if I understand you correctly.
Is it not possible to describe your pairing scheme in an algorithmic way?
Did you check Boris' paired pages patches for MTD?
Please try to implement it.
Having the pairing table in DT is IMHO not a good thing.
Thanks,
//richard
prev parent reply other threads:[~2016-05-04 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 14:28 [ANNOUNCE] MLC support for UBI/UBIFS Richard Weinberger
2016-05-04 7:40 ` Bean Huo 霍斌斌 (beanhuo)
2016-05-04 8:27 ` Richard Weinberger
2016-05-04 8:55 ` Bean Huo 霍斌斌 (beanhuo)
2016-05-04 9:17 ` Boris Brezillon
2016-05-04 18:59 ` Boris Brezillon
2016-05-04 9:18 ` Richard Weinberger [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=5729BE71.5090708@nod.at \
--to=richard@nod.at \
--cc=alex@nextthing.co \
--cc=beanhuo@micron.com \
--cc=boris.brezillon@free-electrons.com \
--cc=david@sigma-star.at \
--cc=dedekind1@gmail.com \
--cc=goliath@sigma-star.at \
--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).