From: Nick <nick@auriga.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: jffs-dev <jffs-dev@axis.com>, mtd <mtd@infradead.org>
Subject: Re: Finalized TODO list for NAND and JFFS...
Date: Wed, 27 Sep 2000 15:35:58 +0400 [thread overview]
Message-ID: <39D1DB9E.D1BAA64E@auriga.ru> (raw)
In-Reply-To: 21835.969974378@passion.cygnus.co.uk
David Woodhouse wrote:
> Also add a checkpointing system or some way of removing the necessity of
> scanning the whole of the flash on mount.
>
> For a 21MB filesystem, that takes over a minute.
>
> --
> dwmw2
By the way, can't we shorten mount time for Intel chips by rewriting read
routines in such a way that they don't send Read Status Register command when
chip->status is FL_READY?
I think we can. Acually, I have tried already and it shortens mount time
dramatically.
So the question, as I can see it, is can we be sure that Status Register has
7th bit set when chip->status == FL_READY?
Any comments?
Nick
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next parent reply other threads:[~2000-09-27 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39D091DC.3218DE2D@cotw.com>
[not found] ` <21835.969974378@passion.cygnus.co.uk>
2000-09-27 11:35 ` Nick [this message]
2000-09-27 11:57 ` Finalized TODO list for NAND and JFFS David Woodhouse
2000-09-27 13:21 ` Nick Ivanter
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=39D1DB9E.D1BAA64E@auriga.ru \
--to=nick@auriga.ru \
--cc=dwmw2@infradead.org \
--cc=jffs-dev@axis.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