From: "mar.krzeminski" <mar.krzeminski@gmail.com>
To: Peter Crosthwaite <crosthwaitepeter@gmail.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Adding secondary ARM processor
Date: Tue, 1 Sep 2015 20:27:18 +0200 [thread overview]
Message-ID: <55E5EE06.8020804@gmail.com> (raw)
In-Reply-To: <CAPokK=pztp84VjNa2qzo346ftA_heZFoowJ6OJkKNB2EWJ1nYg@mail.gmail.com>
W dniu 01.09.2015 o 19:45, Peter Crosthwaite pisze:
> On Tue, Sep 1, 2015 at 10:19 AM, mar.krzeminski
> <mar.krzeminski@gmail.com> wrote:
>> Hello,
>>
>> I have board with A9 processor (playing with vexpress model),
>> for test I want to also add to this setup M3 processor.
>> The problem is that secondary CPU sees the same device (eg. UART) with
>> different address.
> How far into the boot are you? Does A9 have MMU turned on?
>
> info mtree from the monitor should show the view of the address maps.
> Anything weird there?
I mess my question, sorry.
I meant that address seen from M3 are different by design,
eg. UART0 seen from M3 has base address 0x100, but same UART0 from A9 is
mapped at 0x200 and I want to emulate this.
This required some remapping at sysbus level (I think), and I do not
know how to do that - even where to start, that is why I need your help.
>> I can not figure out, how should I do that. Is it possible in qemu?
> Yes it should be possible.
>
>> If yes, could you point me where I should start to look at it?
>>
> xlnx-zynqmp board, which does something similar with A53 and R5. It is
> mixed with a combo of MMU and no-MMU capable CPUs.
I saw this board, but my basic problem is with address mapping.
>
> Regards,
> Peter
>
>> Regards,
>> Marcin
>>
next prev parent reply other threads:[~2015-09-01 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 17:19 [Qemu-devel] Adding secondary ARM processor mar.krzeminski
2015-09-01 17:45 ` Peter Crosthwaite
2015-09-01 18:27 ` mar.krzeminski [this message]
2015-09-01 20:12 ` Peter Crosthwaite
2015-09-02 5:06 ` Marcin Krzemiński
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=55E5EE06.8020804@gmail.com \
--to=mar.krzeminski@gmail.com \
--cc=crosthwaitepeter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.