From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: "Linux-Mtd" <linux-mtd@lists.infradead.org>
Subject: using multile partitions on one NAND chip
Date: Wed, 24 Nov 2004 15:40:37 +0100 [thread overview]
Message-ID: <NGENJJFPMHGLPILEKKAMMEAECFAA.Stephan.Linke@epygi.de> (raw)
Hi,
anyone tried using multiple partitions on a NAND flash?
I can't find the protection mechanism that protects lets say an erase on one block against a read command on the other block.
In my case I am using 2 YAFFS patitions and 1 partition that fakes a read-only NOR flash using the nand_read_ecc() function
(mtd->read_ecc()). I'm not shure if there is an efficient protection for this. It looks like nand_chip->chip_lock should do this job
but it only protects parts of the erase loop agains parts of the nand_chip->waitfunc() wait loop. It does not keep
nand_chip->cmdfunc() from sending a command while an erase command is still active in the nand chip.
Thanks, Stephan
next reply other threads:[~2004-11-24 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 14:40 Stephan Linke [this message]
2004-11-24 16:29 ` using multile partitions on one NAND chip Thomas Gleixner
[not found] <NGENJJFPMHGLPILEKKAMMEAFCFAA.Stephan.Linke@epygi.de>
2004-11-24 18:28 ` Stephan Linke
2004-11-24 20:05 ` Thomas Gleixner
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=NGENJJFPMHGLPILEKKAMMEAECFAA.Stephan.Linke@epygi.de \
--to=stephan.linke@epygi.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.