From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37864) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UjNK0-0008EY-8k for qemu-devel@nongnu.org; Mon, 03 Jun 2013 01:28:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UjNJz-0006Ww-G4 for qemu-devel@nongnu.org; Mon, 03 Jun 2013 01:28:44 -0400 Received: from mx1.redhat.com ([209.132.183.28]:19204) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UjNJz-0006Wl-85 for qemu-devel@nongnu.org; Mon, 03 Jun 2013 01:28:43 -0400 Message-ID: <51AC2965.2080005@redhat.com> Date: Mon, 03 Jun 2013 07:28:05 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <20130523124132.GA18596@redhat.com> <20130528235309.GA31648@morn.localdomain> <51A5C117.6000609@redhat.com> <871u8p92v8.fsf@codemonkey.ws> <1369905828.20691.50.camel@shinybook.infradead.org> <51A73459.2020407@redhat.com> <1369916358.5141.32.camel@i7.infradead.org> <51A78152.10000@redhat.com> <51A86E3F.5030803@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [SeaBIOS] KVM call agenda for 2013-05-28 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jordan Justen Cc: KVM devel mailing list , Juan Quintela , Laszlo Ersek , seabios@seabios.org, qemu-devel qemu-devel , Kevin O'Connor , "Michael S. Tsirkin" , Anthony Liguori , "Jordan Justen (Intel address)" , David Woodhouse On 06/01/13 01:01, Jordan Justen wrote: > On Fri, May 31, 2013 at 2:32 AM, Gerd Hoffmann wrote: >> Hi, >> >>> I guess -bios would load coreboot. Coreboot would siphon the data >>> necessary for ACPI table building through the current (same) fw_cfg >>> bottleneck, build the tables, >> >> Yes. > > So, this is really about making coreboot+seabios the default QEMU > firmware, and making seabios depend on being a coreboot payload? I still think it's better to simply have qemu generate the acpi tables, but if that isn't going to be accepted we should seriously consider & evaluate switching to coreboot. >>> load the boot firmware (SeaBIOS or OVMF or >>> something else -- not sure how to configure that), > > It wouldn't be loading OVMF. It would be loading CorebootPkg. Yep. Some OVMF bits would be needed though (virtio drivers, qemu boot priority support, ...). cheers, Gerd