From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Marteo Tim <tim.marteo@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: about using UBI on MLC Nand flash
Date: Mon, 31 Jul 2006 13:19:27 +0400 [thread overview]
Message-ID: <44CDCB1F.3050005@yandex.ru> (raw)
In-Reply-To: <91b24a870607310205w7fa0d847wb652da7a1b0c52c7@mail.gmail.com>
Marteo Tim wrote:
> OK, I'm glad to send it to you, include SAMSUNG&TOSHIBA's MLC NAND
> flash datasheet, please check your email, :)
Thanks!
> Due to cheap price, MLC NAND flash maybe use more and more popular,
> especially in bulky flash. Yaffs2 can already support MLC chips by
> zero page rewrites, and I want UBI can support it too. :)
Well, UBI works in this case as well. But it anyway needs 2 write
operations. So, in your case, we'll spend 4K for UBI headers in each
eraseblock... It's wastful, agree, but may be appropriate in some
applications.
--
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.
prev parent reply other threads:[~2006-07-31 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 3:33 about using UBI on MLC Nand flash Marteo Tim
2006-07-28 7:18 ` Artem B. Bityutskiy
2006-07-31 9:05 ` Marteo Tim
2006-07-31 9:13 ` Vitaly Wool
2006-07-31 9:19 ` Artem B. Bityutskiy [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=44CDCB1F.3050005@yandex.ru \
--to=dedekind@yandex.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=tim.marteo@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