From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin O'Connor Subject: Re: [SeaBIOS] KVM call agenda for 2013-05-28 Date: Fri, 31 May 2013 23:41:39 -0400 Message-ID: <20130601034139.GA8929@morn.localdomain> References: <20130523124132.GA18596@redhat.com> <20130528235309.GA31648@morn.localdomain> <20130531023426.GB18156@morn.localdomain> <20130523124132.GA18596@redhat.com> <20130528235309.GA31648@morn.localdomain> <20130531023426.GB18156@morn.localdomain> <20130531081334.16432.qmail@stuge.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: KVM devel mailing list , seabios@seabios.org, qemu-devel qemu-devel Return-path: Received: from mail-qc0-f182.google.com ([209.85.216.182]:37226 "EHLO mail-qc0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755270Ab3FADlm (ORCPT ); Fri, 31 May 2013 23:41:42 -0400 Received: by mail-qc0-f182.google.com with SMTP id n1so1225217qcw.13 for ; Fri, 31 May 2013 20:41:41 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20130531081334.16432.qmail@stuge.se> Sender: kvm-owner@vger.kernel.org List-ID: On Fri, May 31, 2013 at 10:13:34AM +0200, Peter Stuge wrote: > Kevin O'Connor wrote: > > one possible way forward would be to split the current SeaBIOS rom > > into two roms: "qvmloader" and "seabios". The "qvmloader" would do > > the qemu specific platform init (pci init, smm init, mtrr init, bios > > tables) and then load and run the regular seabios rom. > > qvmloader sounds a lot like coreboot. Agreed. I don't much like the qvmloader idea. I did want to open up discussion on the possibility, however. The only advantage it has over coreboot is that it could reasonably live in the qemu repo, and I do think that the hardware descriptions should like in the same code repo as the hardware implementation. -Kevin