From: Lucas Stach <l.stach@pengutronix.de>
To: Andre Wagner <andre.wagner@richard-wolf.com>,
barebox@lists.infradead.org
Subject: Re: Support for QEMU virt ARM 32
Date: Thu, 30 Nov 2017 17:48:42 +0100 [thread overview]
Message-ID: <1512060522.17442.26.camel@pengutronix.de> (raw)
In-Reply-To: <0b235055-1329-a855-49c9-6bf7b4cefb72@richard-wolf.com>
Am Donnerstag, den 30.11.2017, 17:39 +0100 schrieb Andre Wagner:
>
> 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?
virt is a generic virtual platform and doesn't resemble any real
hardware. This is nice for some use-cases, as it doesn't have the
restrictions of real hardware systems, but then most of the peripherals
are virtio or mapped on a virtual PCI bus. Barebox is lacking driver
support for most of those peripherals, so the usefulness of this
machine is limited when used with Barebox.
See also: https://wiki.qemu.org/Documentation/Platforms/ARM
Regards,
Lucas
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-11-30 16:49 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
2017-11-30 16:48 ` Lucas Stach [this message]
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=1512060522.17442.26.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=andre.wagner@richard-wolf.com \
--cc=barebox@lists.infradead.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