From: David Woodhouse <dwmw2@infradead.org>
To: Jarkko Lavinen <jlavi@iki.fi>
Cc: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: Preparation for sync with Linus.
Date: Thu, 20 Sep 2001 10:58:42 +0100 [thread overview]
Message-ID: <5023.1000979922@redhat.com> (raw)
In-Reply-To: <20010920123922.A8940@kosh.hut.fi>
jlavi@iki.fi said:
> if the chip has sectors locked after cold boot, currently I have to
> either run unlock command or add a call to unlock function into the
> map driver.
> Should chip driver unlock sectors if chip is detected and the sectors
> are suspected to be locked?
There are two possible types of mishap which the locking can protect us
from:
1. Kernel bugs where misdirected memory accesses could write to or erase
parts of the flash.
2. User error leading to the erasure of important flash partitions, like
mounting the boot loader partition as JFFS2.
If we care primarily about #1, we should keep the sectors locked at all
times and unlock them only when we want to access them.
If we care primarily about #2, then we should unlock sectors _only_ when
explicitly requested to do so by the user.
I think that the facility to switch Vpp off while the chip is idle, coupled
with the complexity of the sequence of writes necessary to actually write to
a flash chip, makes it unlikely that #1 is a serious concern - so we
currently unlock sectors only when explicitly requested to do so by the
user.
--
dwmw2
prev parent reply other threads:[~2001-09-20 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 22:49 Preparation for sync with Linus David Woodhouse
2001-09-20 9:39 ` Jarkko Lavinen
2001-09-20 9:58 ` David Woodhouse [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=5023.1000979922@redhat.com \
--to=dwmw2@infradead.org \
--cc=jlavi@iki.fi \
--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