From: Boris Brezillon <bbrezillon@kernel.org>
To: "Bean Huo (beanhuo)" <beanhuo@micron.com>
Cc: "richard@nod.at" <richard@nod.at>,
"boris.brezillon@bootlin.com" <boris.brezillon@bootlin.com>,
"Zoltan Szubbocsev \(zszubbocsev\)" <zszubbocsev@micron.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [EXT] Re: [RESEND PATCH V2 2/2] mtd: core: NAND filling block
Date: Fri, 25 Jan 2019 15:10:41 +0100 [thread overview]
Message-ID: <20190125151041.47928c62@bbrezillon> (raw)
In-Reply-To: <BYAPR08MB45339AB26F5CC0FC6378C4E3DB9B0@BYAPR08MB4533.namprd08.prod.outlook.com>
On Fri, 25 Jan 2019 13:39:13 +0000
"Bean Huo (beanhuo)" <beanhuo@micron.com> wrote:
> >> >
> >> it is still 15 pages, page0~page14. But it is now odd pages, there
> >> will one less odd pages than even pages.
> >
> >Why only odd pages? You did not reply to this question yet, and I really want to
> >understand why.
> >
>
> Programming only odd pages will be effective, while reducing the number of programmed pages.
> This is related to the proprietary device architecture and erase procedure.
>
I'm clearly not happy with this explanation, but it looks like I don't
have a choice here. Please add a comment explaining that this is Micron
black-magic and we have no choice but to trust you on that one because
it's *confidential*. I hope you're right in your analysis...
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-01-25 14:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 22:12 [RESEND PATCH V2 2/2] mtd: core: NAND filling block Bean Huo (beanhuo)
2019-01-18 22:39 ` Boris Brezillon
2019-01-20 17:31 ` Boris Brezillon
2019-01-21 12:28 ` [EXT] " Bean Huo (beanhuo)
2019-01-21 12:44 ` Boris Brezillon
2019-01-25 13:39 ` Bean Huo (beanhuo)
2019-01-25 14:10 ` Boris Brezillon [this message]
2019-01-18 23:01 ` Boris Brezillon
2019-01-21 10:04 ` [EXT] " Bean Huo (beanhuo)
2019-01-21 10:12 ` Boris Brezillon
2019-01-25 13:31 ` Bean Huo (beanhuo)
2019-01-25 14:15 ` Boris Brezillon
2019-01-20 15:59 ` Miquel Raynal
2019-01-24 15:47 ` [EXT] " Bean Huo (beanhuo)
2019-01-24 20:02 ` Miquel Raynal
2019-01-20 17:36 ` Boris Brezillon
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=20190125151041.47928c62@bbrezillon \
--to=bbrezillon@kernel.org \
--cc=beanhuo@micron.com \
--cc=boris.brezillon@bootlin.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=zszubbocsev@micron.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