From: "Dvir Oren" <dviro@lucidvon.com>
To: MTD <mtd@infradead.org>
Subject: Re: Hardware RO & delays [DOC2000]
Date: Fri, 7 Jan 2000 17:55:38 +0200 [thread overview]
Message-ID: <E126bft-00065J-00@infradead.org> (raw)
In-Reply-To: <E126VUj-0006ne-00@devel2.axiom.internal>
> > 1. Is there a way to tell the flash (DoC2000) to mark a certain part
> > of it as read only? I know I can mount a certain partition as read
> > only, but can I protect it at a lower level?
> Not per partition, but per NFTL. Yes - if you modify nftl.c to register the
> blockdevice as readonly, then refuse to process any writes to that device,
> you'll be fine.
What's the difference between per partition and per NFTL? Do you
mean that there should be /dev/nftla1 and /dev/nftlb1, as opposed
to /dev/nftla1 and /dev/nftla2?
Is there a way to tell the flash chip itself not to touch certain areas?
> > 2. Does the driver block the system? I'm experience delays in
> Yes, it does all its flash access, even waiting for erases to finish, with
> interrupts disabled.
Do you know if this is true for M-Systems' driver as well?
Are the interrupts disabled during read operations as well? Could it
be that the driver disables the interrupts even if the flash is not
mounted?
How long does it take it to finish?
---------
Dvir Oren <dvir@lucidvon.com>
Lucid VON Ltd. <http://www.lucidvon.com>
Twin Towers 2, Suite 406, P.O.Box 159
35 Jabotinsky street, Ramat-Gan 52511, ISRAEL
Tel:+972 3 6137214 Fax:+972 3 6137215
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-01-07 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-04 21:45 Hardware RO & delays [DOC2000] Dvir Oren
2000-01-07 2:01 ` Brendan J Simon
2000-01-07 15:55 ` Dvir Oren
2000-01-07 9:15 ` David Woodhouse
2000-01-07 15:55 ` Dvir Oren [this message]
2000-01-07 16:10 ` David Woodhouse
2000-01-14 1:37 ` i hope to write open source's firmware jyllyj
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=E126bft-00065J-00@infradead.org \
--to=dviro@lucidvon.com \
--cc=mtd@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