[SeaBIOS] [Qemu-stable] [Qemu-devel] problems with freeBSD
cardoe at gentoo.org
Thu Mar 7 07:12:41 CET 2013
On Wed, Mar 6, 2013 at 7:58 PM, Peter Stuge <peter at stuge.se> wrote:
> Laszlo Ersek wrote:
>> Going out on a limb, I suspect qemu commit 5f876756 instead.
>> I think the gcc version Anthony was using miscompiled SeaBIOS
> Yeah, it is very common. Lots of distributions patch their
> toolchains such that they don't compile firmware code correctly.
> Firmware isn't a common target, so I understand that it happens.
> For coreboot we recommend to build a vanilla toolchain using known
> good versions. We also have a script to do that. (The script is at
> util/crossgcc/buildgcc in the coreboot repo.)
Not sure if you or Kevin builds the coreboot images at
http://code.coreboot.org/p/seabios/downloads/, but would you guys
consider building point release as well (e.g. 184.108.40.206), if yes then my
The rest of the ML,
Would qemu consider using those blobs rather than different developers
using their distro toolchain to build up a random commit ID. I say
random only because often qemu releases ship with a non-release
In this past there's been other issues related to seabios + qemu, that
I've solved in Gentoo by simply using the coreboot seabios images
after some troubleshooting help from Peter. Similarly our Ubuntu
OpenStack machines at work had quirks resolved by dropping the
coreboot seabios images on them.
More information about the SeaBIOS