mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <dev@lynxeye.de>
To: Wesley Chow <wes@cortico.ai>, barebox@lists.infradead.org
Subject: Re: qemu arm vexpress / virt32 support
Date: Tue, 14 Jan 2020 21:06:22 +0100	[thread overview]
Message-ID: <5d1c6ffa63be590d5135dadf9200405cd5a28ba0.camel@lynxeye.de> (raw)
In-Reply-To: <CAG=Azd9mtQJuweJaeJNxRWq2-6r7Yu0L5oS9zFX1YNvvXHoo=A@mail.gmail.com>

Hi Wesley,

Am Dienstag, den 14.01.2020, 12:40 -0500 schrieb Wesley Chow:
> 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?

I wouldn't say there is no interest in supporting the virt platform in
Barebox. It's true that none of the current developers have a strong
interest in the virt platform.

If someone from the community shows an interest and implements all the
virtio infrastructure and related drivers, I see no reason why those
patches wouldn't be considered for mainline inclusion.

I guess that's an elaborate way to say: patches welcome!

> 
> 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?

I've just built barebox -next and using qemu 4.1.1 the documented
(Documentation/boards/arm-qemu-vexpress.rst) commandline
"qemu-system-arm -m 1024M -machine vexpress-a9 -cpu cortex-a9
-nographic -no-reboot -kernel images/barebox-vexpress-ca9.img" yields a
working Barebox for me.

Regards,
Lucas


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2020-01-14 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 17:40 Wesley Chow
2020-01-14 20:06 ` Lucas Stach [this message]
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=5d1c6ffa63be590d5135dadf9200405cd5a28ba0.camel@lynxeye.de \
    --to=dev@lynxeye.de \
    --cc=barebox@lists.infradead.org \
    --cc=wes@cortico.ai \
    /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