[SeaBIOS] [Qemu-devel] [Qemu-stable] problems with freeBSD
mjt at tls.msk.ru
Thu Mar 7 08:17:31 CET 2013
07.03.2013 10:12, Doug Goldstein wrote:
> On Wed, Mar 6, 2013 at 7:58 PM, Peter Stuge <peter at stuge.se> wrote:
>> 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. 22.214.171.124), if yes then my
> next question...
> 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.
Just a note, or an "alternative opinion", so to say. In Debian, we have
a social contract which, among other things, ensures that the binaries
you, as a user, get, comes with source which you can modify on the
system you installed. This requires, for example, that all binaries
shipped are actually built from the corresponding source, and that
no blobs from whatever other sources are used, ever.
We don't even ship any upstream blobs in the debian qemu _source_
package: we repack upstream qemu.tar.gz by removing these blobs.
So from this PoV, it'd be better if upstream didn't ship any blobs
at all, -- we wont need to repack the upstream .tar.gz ;)
FWIW, prpbably we were lucky so far: we had almost no issues with
(mis)compiling of various ROM codes (bochsbios, seabios, vgabios,
pxe roms, various sparc/ppc firmware etc) using toolchains provided
More information about the SeaBIOS