From: Blue Swirl <blauwirbel@gmail.com>
To: Juergen Lock <qemu-l@jelal.kn-bremen.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] (master, stable-0.13) zaurus: workaround for io base address rounded down
Date: Wed, 13 Oct 2010 19:45:19 +0000 [thread overview]
Message-ID: <AANLkTikY54E9yBE3Cojt0xZN7MwUpf1Fgxg2EqdGzCvy@mail.gmail.com> (raw)
In-Reply-To: <20101013191250.GA59919@triton8.kn-bremen.de>
On Wed, Oct 13, 2010 at 7:12 PM, Juergen Lock <qemu-l@jelal.kn-bremen.de> wrote:
> The 2nd scoop's base address (0x08800040) now gets rounded down to
> start of page which causes its io read/write callbacks to be passed
> addresses 0x40 higher than the code expects: (as witnessed by
> "Bad register offset" messages and failure to attach the internal
> CF disk aka microdrive at least.)
>
> [There may be more bugs of this kind hiding in other targets, this
> was just the one I tested...]
The devices are passed an offset to base address. Perhaps the real
problem is that scoop_init registers too much MMIO: 0x1000, when the
real range should be only 0x28. Also the registers are in 4 byte
intervals and any access to address between the registers also
triggers a warning.
What were the messages exactly?
next prev parent reply other threads:[~2010-10-13 20:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 22:15 [Qemu-devel] [RFT] qemu 0.13.0-rc3 Anthony Liguori
2010-10-11 23:45 ` [Qemu-devel] " Luiz Capitulino
2010-10-12 0:02 ` Anthony Liguori
2010-10-12 15:43 ` [Qemu-devel] " Rick Vernam
2010-10-12 16:27 ` Stefan Weil
2010-10-12 21:34 ` Juergen Lock
2010-10-12 22:00 ` Anthony Liguori
2010-10-13 3:28 ` Juergen Lock
2010-10-13 19:12 ` [Qemu-devel] [PATCH] (master, stable-0.13) zaurus: workaround for io base address rounded down Juergen Lock
2010-10-13 19:45 ` Blue Swirl [this message]
2010-10-13 21:30 ` Juergen Lock
2010-10-13 19:24 ` [Qemu-devel] [RFT] qemu 0.13.0-rc3 Juergen Lock
2010-10-13 9:41 ` Amit Shah
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=AANLkTikY54E9yBE3Cojt0xZN7MwUpf1Fgxg2EqdGzCvy@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-l@jelal.kn-bremen.de \
/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).