From: Peter Crosthwaite <crosthwaitepeter@gmail.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/3] target-xtensa: xtfpga: attach FLASH to system IO
Date: Sun, 27 Sep 2015 11:36:05 -0700 [thread overview]
Message-ID: <CAPokK=oSaX30TDi9A2Fm3kT3GiTw-WR2so9Mr4fKqeiUwGwjbg@mail.gmail.com> (raw)
In-Reply-To: <CAMo8Bf+XsA5CupQ50vFLwN4Ptj6Pr2f5SeqMVpTofjexVOhT5A@mail.gmail.com>
On Sun, Sep 27, 2015 at 11:01 AM, Max Filippov <jcmvbkbc@gmail.com> wrote:
> On Sun, Sep 27, 2015 at 8:42 PM, Peter Crosthwaite
> <crosthwaitepeter@gmail.com> wrote:
>> On Sun, Sep 27, 2015 at 10:16 AM, Max Filippov <jcmvbkbc@gmail.com> wrote:
>>> XTFPGA FLASH is tied to XTFPGA system IO block. It's not very important
>>> for systems with MMU where system IO block is visible at single
>>> location,
>>
>> Are your relying on a matching change in the guest for MMU setup here?
>>
>> Can you explain a little more how the MMU allows a physical address
>> remap of the underlying hardware as this looks like a non
>> backwards-compatible board design rev.
>
> No change is needed as this change doesn't affect memory map.
> It only detaches FLASH from the system memory and attaches it
> to the system IO region, at the same physical address as before.
>
Ok I get it now :). Commit message confused me a little with the MMU
stuff but reading it again it makes sense. Change looks good. I'll
wait for resolution on P1 before putting an RB.
Regards,
Peter
> --
> Thanks.
> -- Max
next prev parent reply other threads:[~2015-09-27 18:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 17:16 [Qemu-devel] [PATCH 0/3] target-xtensa: xtfpga: support cores without MMU Max Filippov
2015-09-27 17:16 ` [Qemu-devel] [PATCH 1/3] pflash_cfi01: add pflash_cfi01_init Max Filippov
2015-09-27 17:25 ` Peter Crosthwaite
2015-09-27 17:51 ` Max Filippov
2015-09-27 18:32 ` Peter Crosthwaite
2015-09-27 18:43 ` Max Filippov
2015-09-27 17:16 ` [Qemu-devel] [PATCH 2/3] target-xtensa: xtfpga: attach FLASH to system IO Max Filippov
2015-09-27 17:42 ` Peter Crosthwaite
2015-09-27 18:01 ` Max Filippov
2015-09-27 18:36 ` Peter Crosthwaite [this message]
2015-09-27 17:16 ` [Qemu-devel] [PATCH 3/3] target-xtensa: xtfpga: support noMMU cores Max Filippov
2015-09-27 17:38 ` Peter Crosthwaite
2015-09-27 18:13 ` Max Filippov
2015-09-27 18:43 ` Peter Crosthwaite
2015-09-27 19:01 ` Max Filippov
2015-09-27 21:28 ` Peter Crosthwaite
2015-09-27 21:48 ` Max Filippov
2015-09-27 21:59 ` Peter Crosthwaite
2015-09-29 10:34 ` Max Filippov
2015-09-29 19:20 ` Peter Crosthwaite
2015-09-30 17:41 ` Max Filippov
2015-09-29 20:42 ` Peter Maydell
2015-09-30 20:17 ` Max Filippov
2015-09-30 20:45 ` Peter Maydell
2015-09-30 20:54 ` Max Filippov
2015-09-30 21:02 ` Peter Crosthwaite
2015-09-30 22:07 ` Max Filippov
2015-09-30 22:23 ` Peter Crosthwaite
2015-09-30 22:33 ` Peter Crosthwaite
2015-09-30 22:42 ` Max Filippov
2015-10-01 18:06 ` Peter Crosthwaite
2015-10-01 18:25 ` Max Filippov
2015-10-01 19:18 ` Peter Crosthwaite
2015-10-01 20:13 ` Max Filippov
2015-10-01 21:19 ` Peter Crosthwaite
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='CAPokK=oSaX30TDi9A2Fm3kT3GiTw-WR2so9Mr4fKqeiUwGwjbg@mail.gmail.com' \
--to=crosthwaitepeter@gmail.com \
--cc=jcmvbkbc@gmail.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).