qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] E820 (Re: [v4 PATCH 00/12] SMBIOS: build full tables in


From: Gabriel L. Somlo
Subject: Re: [Qemu-devel] E820 (Re: [v4 PATCH 00/12] SMBIOS: build full tables in QEMU)
Date: Wed, 2 Apr 2014 21:57:33 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Apr 02, 2014 at 01:01:28PM -0400, Gabriel L. Somlo wrote:
> Speaking of, I *thought* I had a vague idea of how all this stuff fits
> together, but it turns out I don't... There's
> 
>       - OVMF
>         http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=OVMF
> 
>       - TianoCore
>         http://www.coreboot.org/TianoCore
> 
>       - coreboot
>         http://www.coreboot.org/Download_coreboot
> 
> Apparently, TianoCore is a "coreboot payload", which in my mind is
> somewhat analogous to bootloader "stages" chaining off each other,
> but then what's OVMF (the only thing I actually tried, which only
> works on piix) ? Is it a packaged bundle of coreboot+tianocore ?
> or something else entirely ?
> 
> What if I want to send a patch against this whole "thing" to
> facilitate integration with the new smbios table generator in qemu ?
> 
> Which git repos do I need to have around, and how to stitch them
> together to obtain "the thing you use as an argument to -bios in lieu
> of SeaBIOS", when it comes time to test ? :)
> 
> I'm guessing this is a FAQ, so if there's one place that explains it
> all, please point me at it. Otherwise I'd be happy to write it up once
> I get my head wrapped around it :)

Nevermind, it seems it's all under git://git.code.sf.net/p/tianocore/edk2 :)

Although the nomenclature is still a bit fuzzy to me, the "thing to build"
within edk2 appears to be OvmfPkg (ACTIVE_PLATFORM = OvmfPkg/OvmfPkgX64.dsc,
with TOOL_CHAIN_TAG = GCC48, in Conf/target.txt, at least on F20).

I now have the latest and greatest "upstream" OVMF.fd, and I can use it
(piix only) to boot Fedora 20 live x86_64. Guess I'm on my way :)

I get "missing smbios entry point" when I do a dmidecode, BTW. QEMU is
sending type 1, 3, 4, etc. blobs in fw_cfg, not sure yet what I need
to do to get OVMF to add the entry point... Maybe I should try without
my smbios-patched qemu ?

Thanks,
--Gabriel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]