qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Tobias Röhmel" <tobias.roehmel@rwth-aachen.de>
To: Ayan Kumar Halder <ayankuma@amd.com>, <peter.maydell@linaro.org>
Cc: <qemu-devel@nongnu.org>, <qemu-arm@nongnu.org>,
	"Stabellini, Stefano" <stefano.stabellini@amd.com>
Subject: Re: Cortex-R52 support in Qemu
Date: Fri, 5 May 2023 16:15:01 +0200	[thread overview]
Message-ID: <28bfa9ad-f8dd-d195-ec66-fbd2d78d170c@rwth-aachen.de> (raw)
In-Reply-To: <a1c45644-90d9-0fd2-c87b-f43f16b7e407@amd.com>

Hi Ayan,

as far as I know, there is no board/SoC that uses the Cortex-R52 in Qemu 
right now. If you want, I can try to find the one that I used
during development. I was able to run Zephyr in Qemu with that code.

Best regards,
Tobias

On 05.05.23 14:21, Ayan Kumar Halder wrote:
> Hi Tobias/Peter,
>
> Greetings.
>
> In the following commit, I see you have added R52 support in Qemu.
>
> commit 5f536d01d1141a56f5057b62c82fa94826d367f0
> Author: Tobias Röhmel <tobias.roehmel@rwth-aachen.de>
> Date:   Tue Dec 6 11:25:04 2022 +0100
>
>     target/arm: Add ARM Cortex-R52 CPU
>
>
> 1. Do you have quick instructions on how to build and test it ? I have 
> ported Xen for Cortex-R52 (using Arm FVP) and would like to see if it 
> works with Qemu as well.
>
> 2. Have you (or planning in near future) to add support for qemu-r52 
> in Zephyr ? I can see an old ticket
> https://github.com/zephyrproject-rtos/zephyr/issues/47330 , but don't 
> know if you have integrated qemu in Zephyr.
>
>
> Kind regards,
>
> Ayan
>


  reply	other threads:[~2023-05-05 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 12:21 Cortex-R52 support in Qemu Ayan Kumar Halder
2023-05-05 14:15 ` Tobias Röhmel [this message]
2023-05-09 10:31   ` Ayan Kumar Halder

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=28bfa9ad-f8dd-d195-ec66-fbd2d78d170c@rwth-aachen.de \
    --to=tobias.roehmel@rwth-aachen.de \
    --cc=ayankuma@amd.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@amd.com \
    /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).