From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mu9zn-0001g8-5r for qemu-devel@nongnu.org; Sat, 03 Oct 2009 15:10:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mu9zi-0001cY-Gb for qemu-devel@nongnu.org; Sat, 03 Oct 2009 15:10:18 -0400 Received: from [199.232.76.173] (port=38365 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mu9zi-0001cT-C0 for qemu-devel@nongnu.org; Sat, 03 Oct 2009 15:10:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:65147) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mu9zh-0007yM-Pt for qemu-devel@nongnu.org; Sat, 03 Oct 2009 15:10:14 -0400 Date: Sat, 3 Oct 2009 21:09:54 +0200 From: Gleb Natapov Subject: Re: [coreboot] [Qemu-devel] Release plan for 0.12.0 Message-ID: <20091003190954.GH17326@redhat.com> References: <4AC60037.6000001@codemonkey.ws> <2a50f7880910020958g3fe5eadehe5e5094c05b218d9@mail.gmail.com> <4AC64A5C.6010003@gmx.net> <4AC64C32.4020509@codemonkey.ws> <4AC67326.6080603@gmx.net> <20091003150803.GF17326@redhat.com> <20091003173252.1061.qmail@stuge.se> <13426df10910031040y5029dc31m8c6ca4a4bac098a6@mail.gmail.com> <20091003181631.GG17326@redhat.com> <20091003183030.10662.qmail@stuge.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091003183030.10662.qmail@stuge.se> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ron minnich , Anthony Liguori , Coreboot , qemu-devel@nongnu.org, Carl-Daniel Hailfinger , Anthony Liguori , Jordan Justen On Sat, Oct 03, 2009 at 08:30:30PM +0200, Peter Stuge wrote: > Gleb Natapov wrote: > > Exactly. I am glad to hear that coreboot has support for QEMU, > > but seabios does the job already, so why add more layers? > > If SeaBIOS does not need any code at all for QEMU machine init I > agree there's no point in considering coreboot. > The code is there already. > If QEMU machine specific init is in fact needed in that SeaBIOS, then > the answer isn't as obvious.. > May be it is possible to drop seabios init code and use coreboot, but I prefer to dial with one codebase for all BIOS needs. By moving to seabios we try to improve situation not make it worse. -- Gleb.