From: "Johan Adolfsson" <johan.adolfsson@axis.com>
To: "David Woodhouse" <dwmw2@infradead.org>,
"David S. Miller" <davem@redhat.com>
Cc: "Chris Wedgwood" <cw@f00f.org>,
"Jeff Garzik" <jgarzik@mandrakesoft.com>, <bjorn.wesen@axis.com>,
<linux-kernel@vger.kernel.org>, <linux-mtd@lists.infradead.org>
Subject: Re: Missing cache flush.
Date: Tue, 5 Jun 2001 11:43:39 +0200 [thread overview]
Message-ID: <018601c0eda3$fff76770$0a070d0a@axis.se> (raw)
In-Reply-To: <15132.22933.859130.119059@pizda.ninka.net> <13942.991696607@redhat.com> <3B1C1872.8D8F1529@mandrakesoft.com> <15132.15829.322534.88410@pizda.ninka.net> <20010605155550.C22741@metastasis.f00f.org> <25587.991730769@redhat.com>
Possibly saying something extremly stupid here,
how about simply "fakewriting" 0xFF to the flash
after an erase to update any caches?
> 2. Flash. A few writes of magic data to magic addresses and a whole erase
> block suddenly contains 0xFF. The CPU doesn't notice that either.
do_erase_stuff();
/* While verifying, update cache */
for (address = adr; address < (adr + size); address++) {
if ((verify = map->read8(map, address)) != 0xFF) {
error = 1;
break;
}
/* "Fake" write 0xFF's to the erased sector so that
caches are updated
* after we verified that uncached data is ok
*/
*(unsigned char*)CACHED(address) = 0xFF;
}
/Johan
next prev parent reply other threads:[~2001-06-05 9:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 23:16 David Woodhouse
2001-06-04 23:23 ` Jeff Garzik
2001-06-04 23:29 ` David Woodhouse
2001-06-05 2:03 ` David S. Miller
2001-06-05 3:55 ` Chris Wedgwood
2001-06-05 5:28 ` Linus Torvalds
2001-06-05 6:49 ` Alan Cox
2001-06-05 8:29 ` Ingo Molnar
2001-06-05 15:10 ` Ralf Baechle
2001-06-05 8:46 ` David Woodhouse
2001-06-05 9:05 ` David Woodhouse
2001-06-05 12:42 ` David Woodhouse
2001-06-05 12:52 ` David Woodhouse
2001-06-05 12:48 ` David S. Miller
2001-06-06 8:32 ` Albert D. Cahalan
2001-06-06 19:48 ` Pavel Machek
2001-06-05 9:11 ` David S. Miller
2001-06-05 9:29 ` kira brown
2001-06-05 17:16 ` Alan Cox
2001-06-06 19:44 ` Earyly Cyrix CPUs was " Pavel Machek
2001-06-08 16:00 ` Alan Cox
2001-06-05 9:43 ` Johan Adolfsson [this message]
2001-06-05 8:50 ` David S. Miller
2001-06-05 17:01 ` Jamie Lokier
2001-06-05 23:24 ` Chris Wedgwood
2001-06-06 8:43 ` James Sutherland
2001-06-05 4:01 ` David S. Miller
2001-06-05 2:04 ` David S. Miller
2001-06-05 9:17 ` Bjorn Wesen
2001-06-05 12:57 ` Chris Wedgwood
2001-06-05 15:17 ` Ralf Baechle
2001-06-05 17:41 ` Daniel Phillips
2001-06-05 14:22 ` Vipin Malik
2001-06-05 14:40 ` Chris Wedgwood
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='018601c0eda3$fff76770$0a070d0a@axis.se' \
--to=johan.adolfsson@axis.com \
--cc=bjorn.wesen@axis.com \
--cc=cw@f00f.org \
--cc=davem@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®