From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40434) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVOXh-0002Hu-N4 for qemu-devel@nongnu.org; Wed, 02 Apr 2014 13:01:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WVOXb-0002g5-OC for qemu-devel@nongnu.org; Wed, 02 Apr 2014 13:01:37 -0400 Received: from mail-qc0-x230.google.com ([2607:f8b0:400d:c01::230]:64438) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVOXb-0002g1-Je for qemu-devel@nongnu.org; Wed, 02 Apr 2014 13:01:31 -0400 Received: by mail-qc0-f176.google.com with SMTP id m20so520876qcx.7 for ; Wed, 02 Apr 2014 10:01:31 -0700 (PDT) Date: Wed, 2 Apr 2014 13:01:28 -0400 From: "Gabriel L. Somlo" Message-ID: <20140402170126.GK9466@ERROL.INI.CMU.EDU> References: <20140326223610.GA28587@morn.localdomain> <20140331201807.GG9466@ERROL.INI.CMU.EDU> <533A7B60.7080408@redhat.com> <20140401143902.GA6462@morn.localdomain> <533ADF7D.6010804@redhat.com> <20140401184726.GH9466@ERROL.INI.CMU.EDU> <20140401202832.GA24065@morn.localdomain> <20140401212808.GI9466@ERROL.INI.CMU.EDU> <533B332C.7090701@redhat.com> <1396451225.31715.22.camel@nilsson.home.kraxel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1396451225.31715.22.camel@nilsson.home.kraxel.org> Subject: Re: [Qemu-devel] E820 (Re: [v4 PATCH 00/12] SMBIOS: build full tables in QEMU) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: agraf@suse.de, seabios@seabios.org, qemu-devel@nongnu.org, armbru@redhat.com, alex.williamson@redhat.com, Kevin O'Connor , imammedo@redhat.com, Laszlo Ersek On Wed, Apr 02, 2014 at 05:07:05PM +0200, Gerd Hoffmann wrote: > Hi, > > > If qemu gives OVMF a complete, concatenated dump of all tables, I'll > > have to split that up into individual tables, and install those one by one. > > I feel like I should have a look at how coreboot handles this for an > additional data point ... Sounds like maybe I also need to take a step back and try this stuff out (at least with Linux and Windows), for some first hand experience with how smbios tables are handled outside SeaBIOS... :) 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 :) Thanks much, --Gabriel PS. Coreboot says it supports q35 as well (http://www.coreboot.org/Supported_Motherboards) so if my guess that "coreboot + tianocore == ovmf" is true, then it must be tianocore that doesn't yet support q35 ?