From: Andre Wagner <andre.wagner@richard-wolf.com>
To: Lucas Stach <l.stach@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: Support for QEMU virt ARM 32
Date: Thu, 30 Nov 2017 17:39:30 +0100 [thread overview]
Message-ID: <0b235055-1329-a855-49c9-6bf7b4cefb72@richard-wolf.com> (raw)
In-Reply-To: <1512053584.17442.19.camel@pengutronix.de>
On 30.11.2017 15:53, Lucas Stach wrote:
> Hi André,
>
> Am Donnerstag, den 30.11.2017, 15:29 +0100 schrieb Andre Wagner:
>> Hello everyone,
>>
>> I'm trying to add support for the Qemu virt ARM32 machine (qemu
>> version
>> 2.10) based on the existing Qemu virt ARM64 support. In my
>> understanding
>> the emulated CPU is only a ARMv7 CPU instead of a ARMv8 CPU. Is this
>> correct?
> VExpress is the generic ARM32 QEMU platform. Barebox already supports
> that. Check out the last release (as it has some improvements in that
> area), and build the vexpress_defconfig.
>
> To run the emulated platform take a look at Documentation/boards/arm-
> qemu-vexpress.rst
>
> Regards,
> Lucas
Thank you very much for the fast reply, I got a barebox working with
vexpress on Qemu now! Just a question (little bit off topic): The Qemu
virt ARM64 barebox version is called with: qemu-system-aarch64 -m 2048M
-cpu cortex-a57 -machine virt -display none -serial stdio -kernel
../barebox/barebox (according to
http://barebox.org/doc/latest/boards/aarch64-qemu-virt.html). The first
tests I did were starting my broken barebox version with qemu-system-arm
-m 2048M -cpu cortex-a15 -machine virt -display none -serial stdio
-kernel ../barebox/barebox. Is this 'virt' machine not the _real_ Qemu
virt ARM32?
Greetings,
André
+++
Richard Wolf GmbH, Pforzheimer Strasse 32, 75438 Knittlingen
Managing Directors: Juergen Pfab, Juergen Steinbeck. Trade Register: Mannheim HRB 510031
+++
Richard Wolf GmbH routinely monitors the content of e-mail sent and received via its network for the purposes of ensuring compliance with its policies and procedures. Richard Wolf GmbH is not responsible for any changes made to the message after it has been sent. Where opinions are expressed, they are not necessarily those of Richard Wolf GmbH. This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you are not the intended addressee, or the person responsible for delivering it to them, you may not copy, forward, disclose, or otherwise use it or any part of it in any way. To do so may be unlawful. If you receive this e-mail by mistake, please advise the sender immediately.
+++
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-11-30 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 14:29 Andre Wagner
2017-11-30 14:53 ` Lucas Stach
2017-11-30 16:39 ` Andre Wagner [this message]
2017-11-30 16:48 ` Lucas Stach
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=0b235055-1329-a855-49c9-6bf7b4cefb72@richard-wolf.com \
--to=andre.wagner@richard-wolf.com \
--cc=barebox@lists.infradead.org \
--cc=l.stach@pengutronix.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