From: David Woodhouse <dwmw2@infradead.org>
To: "Dvir Oren" <dviro@lucidvon.com>
Cc: mtd@infradead.org
Subject: Re: Hardware RO & delays [DOC2000]
Date: Fri, 07 Jan 2000 16:10:23 +0000 [thread overview]
Message-ID: <E126byk-0007n8-00@devel2.axiom.internal> (raw)
In-Reply-To: <E126bft-00065J-00@infradead.org>
dviro@lucidvon.com said:
> 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?
Yes. Of course you don't need more than one NFTL if you can have _all_ your
filesystem read-only.
> Is there a way to tell the flash chip itself not to touch certain
> areas?
Not really.
> > 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?
I think it is.
> 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?
During read, yes. When the flash isn't mounted, no.
> How long does it take it to finish?
A week or so of working time, which I'm not going to get for a month or two.
Are you volunteering?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-01-07 16:04 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
2000-01-07 16:10 ` David Woodhouse [this message]
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=E126byk-0007n8-00@devel2.axiom.internal \
--to=dwmw2@infradead.org \
--cc=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