From: David Woodhouse <dwmw2@infradead.org>
To: Joakim Tjernlund <Joakim.Tjernlund@lumentis.se>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Fwd: Cache mappings and invalidate
Date: Tue, 27 Nov 2001 11:07:48 +0000 [thread overview]
Message-ID: <16674.1006859268@redhat.com> (raw)
In-Reply-To: <0111260908050D.28381@jocke.lumentis.se>
Joakim.Tjernlund@lumentis.se said:
> It is almost like burst reads are disabled, but if I mess with the
> burst HW init sequence, I get a lot of errors, so I take it that
> burst reads are enabled.
What flash chip are you using, and have you actually put the flash chip in
to synchronous read mode?
--
dwmw2
next prev parent reply other threads:[~2001-11-27 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 15:53 Fwd: Cache mappings and invalidate Joakim Tjernlund
2001-11-13 16:08 ` David Woodhouse
2001-11-13 17:05 ` Joakim Tjernlund
2001-11-13 17:09 ` David Woodhouse
2001-11-14 1:15 ` Bjorn Wesen
2001-11-13 23:35 ` David Woodhouse
2001-11-26 8:08 ` Joakim Tjernlund
2001-11-27 11:07 ` David Woodhouse [this message]
2001-11-27 12:58 ` Joakim Tjernlund
2001-12-01 9:36 ` David Woodhouse
2001-12-03 10:24 ` Joakim Tjernlund
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=16674.1006859268@redhat.com \
--to=dwmw2@infradead.org \
--cc=Joakim.Tjernlund@lumentis.se \
--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