From: Wesley Chow <wes@cortico.ai>
To: barebox@lists.infradead.org
Subject: qemu arm vexpress / virt32 support
Date: Tue, 14 Jan 2020 12:40:32 -0500 [thread overview]
Message-ID: <CAG=Azd9mtQJuweJaeJNxRWq2-6r7Yu0L5oS9zFX1YNvvXHoo=A@mail.gmail.com> (raw)
I see here that vexpress is supposed to be the 32 bit arm config of choice:
http://lists.infradead.org/pipermail/barebox/2017-November/031597.html
Is this still the case, ie there's no interest in supporting the 32 bit virt?
Using vexpress, I get this:
ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- make vexpress_defconfig
...
$ qemu-system-arm -M vexpress-a9 -cpu cortex-a9 -m 256 -nographic
-kernel images/barebox-vexpress-ca9.img
pulseaudio: set_sink_input_volume() failed
pulseaudio: Reason: Invalid argument
pulseaudio: set_sink_input_mute() failed
pulseaudio: Reason: Invalid argument
PFLASH: Possible BUG - Write block confirm
(then qemu exits)
This is with barebox head, qemu 2.11, but same results with qemu 4.2.0
too. I'm new to barebox -- is this the correct invocation?
Thanks,
Wes
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2020-01-14 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 17:40 Wesley Chow [this message]
2020-01-14 20:06 ` Lucas Stach
2020-01-14 22:15 ` Wesley Chow
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='CAG=Azd9mtQJuweJaeJNxRWq2-6r7Yu0L5oS9zFX1YNvvXHoo=A@mail.gmail.com' \
--to=wes@cortico.ai \
--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