From: llandre <r&d2@dave-tech.it>
To: sshahrom@micron.com
Cc: linux-mtd@lists.infradead.org
Subject: Micron NAND support in linux MTD
Date: Fri, 18 Jan 2008 11:18:07 +0100 [thread overview]
Message-ID: <47907CDF.30802@dave-tech.it> (raw)
Hi,
I found on MTD mailing list your patch that adds Micron manufacturer ID:
http://article.gmane.org/gmane.linux.drivers.mtd/17694
I'm going to use NAND Micron devices for a new project however I still
have a doubt about how MTD/JFFS2 handle bad blocks. To detect blocks
marked as bad it checks the 6th location of OOB area of first page, thus
it seems it is not able to handle Micron devices properly. In fact these
devices stores bad block marker in the first location of OOB of first or
second page (for example see page 50 of MT29F1GxxABB data sheet). Am I
misreading the datasheet? Could you help me to clear this point?
Thanks in advance,
llandre
DAVE Electronics System House - R&D Department
web: http://www.dave-tech.it
email: r&d2@dave-tech.it
next reply other threads:[~2008-01-18 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 10:18 llandre [this message]
2008-01-18 15:45 ` Micron NAND support in linux MTD Ram
2008-01-21 9:51 ` llandre
2008-01-21 10:06 ` Ricard Wanderlof
2008-01-21 11:21 ` llandre
2008-01-21 11:45 ` Ricard Wanderlof
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=47907CDF.30802@dave-tech.it \
--to=r&d2@dave-tech.it \
--cc=linux-mtd@lists.infradead.org \
--cc=sshahrom@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