From: Michael Walle <michael@walle.cc>
To: jan.kiszka@siemens.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Commit 9c9bb6c89d4 breaks code execution from flash
Date: Thu, 22 Apr 2010 23:38:06 +0200 [thread overview]
Message-ID: <201004222338.06194.michael@walle.cc> (raw)
Hi Jan,
your commit "Optimize consecutive CFI02 writes by remapping memory lazily"
breaks the code execution from flash.
If you write to the flash, the flash will switch into I/O mode. Now if code is
executed from this flash, a cpu_abort will be raised ("Trying to execute code
outside RAM or ROM").
--
wkr michael
---
Don't cry because it is over, smile because it happened.
next reply other threads:[~2010-04-22 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 21:38 Michael Walle [this message]
2010-04-23 7:23 ` [Qemu-devel] Re: Commit 9c9bb6c89d4 breaks code execution from flash Jan Kiszka
2010-05-07 20:57 ` Michael Walle
2010-05-12 7:56 ` Jan Kiszka
2010-05-12 23:02 ` Michael Walle
2010-05-13 7:38 ` Jan Kiszka
2010-05-13 10:58 ` Michael Walle
2010-05-13 11:46 ` Jan Kiszka
2010-05-13 11:57 ` Jan Kiszka
2010-05-13 12:38 ` Jan Kiszka
2010-05-13 13:51 ` Michael Walle
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=201004222338.06194.michael@walle.cc \
--to=michael@walle.cc \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).