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@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
