From: Jacky Lam <jackylam@gsl.com.hk>
To: linux-mtd@lists.infradead.org
Subject: Some problem in real application
Date: Mon, 12 Jan 2009 16:57:19 +0800 [thread overview]
Message-ID: <496B05EF.7060401@gsl.com.hk> (raw)
Dear all,
I am new to UBI and want to apply it in a real production application.
However, I have a technical problem and hope anyone can give me some advice.
I use NFTL before. While in production, we use some self-made IO
programmer to program the NAND flash. We first write the data and ecc
(in spare area), and then read then back. After verify it with ECC, we
can tell whether the data is written correctly or not.
However, in UBI, it doesn't use spare area and embedded the ECC
information in main area. Will it be difficult to extract the ECC
information from the read back data in order to do verification? I am
worry about our self-made IO programmer is too slow for handling UBI.
(Or any other clever way to do that?)
If my question is not clear or even wrong, please point me out. Thanks
very much for help.
BR,
Jacky
Disclaimer: This email and attachments are confidential. If you are not the intended recipient, you must not pursue, use, disseminate, distribute or copy this message, whether in whole or in part. If you have received this message in error, please notify us immediately by email or telephone us at (852) 2832 8228 and delete this message from your system. We do not represent that this email may not be interfered with, may not contain computer viruses or other defects and may not be successfully replicated on other system.
next reply other threads:[~2009-01-12 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 8:57 Jacky Lam [this message]
2009-01-13 8:53 ` Some problem in real application Artem Bityutskiy
2009-01-13 14:46 ` Artem Bityutskiy
[not found] ` <496D3E5B.5040206@gmail.com>
2009-01-14 12:34 ` 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=496B05EF.7060401@gsl.com.hk \
--to=jackylam@gsl.com.hk \
--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