From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BV6TI-0005mj-HI for qemu-devel@nongnu.org; Tue, 01 Jun 2004 06:26:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BV6TG-0005mX-5x for qemu-devel@nongnu.org; Tue, 01 Jun 2004 06:26:16 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BV6TG-0005mU-3c for qemu-devel@nongnu.org; Tue, 01 Jun 2004 06:26:14 -0400 Received: from [193.252.22.30] (helo=mwinf0105.wanadoo.fr) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BV6Sm-0001DB-H3 for qemu-devel@nongnu.org; Tue, 01 Jun 2004 06:25:44 -0400 Received: from mwinf0104.wanadoo.fr (mwinf0104 [172.22.132.26]) by mwinf0105.wanadoo.fr (SMTP Server) with ESMTP id 0963918B40A5 for ; Tue, 1 Jun 2004 12:24:55 +0200 (CEST) Received: from bellard.org (AMontpellier-103-1-4-67.w81-250.abo.wanadoo.fr [81.250.91.67]) by mwinf0104.wanadoo.fr (SMTP Server) with ESMTP id 3EC6F1BF7A6A for ; Tue, 1 Jun 2004 12:24:44 +0200 (CEST) Message-ID: <40BC5AB8.3060304@bellard.org> Date: Tue, 01 Jun 2004 12:30:16 +0200 From: Fabrice Bellard MIME-Version: 1.0 Subject: Re: Subject: Re: [Qemu-devel] VGA BIOS source code References: <200405312200.03734.bobb@absamail.co.za> <40BB92D1.6040508@fabianowski.de> <200405312114.08329.kyle@silverbeach.net> <40BC18B6.9040300@fabianowski.de> In-Reply-To: <40BC18B6.9040300@fabianowski.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Bartosz Fabianowski wrote: >> Is there a reasons for the a c b ordering? > > > No ;) > >> I think you are probably a little harsh on this code. It may be >> far from perfect, but it does (mostly) work. > > > Yes, it does work. Maybe I was a bit harsh in my wording after > wasting a day on it, sorry. Yes, and if you think about it longer, you will see the benefit of the Bochs VESA VBE layer. It is one of the simplest implementation you can think of. The VMware driver idea is just an extension of it to add some acceleration primitives, and of course it is much more complicated. Adding real hardware support (such as a Cirrus Logic VGA card) will also be more complicated than the Bochs VESA VBE layer. > Since my main interest is in running Windows inside QEMU, I could > also envision adding another driver later, similar to what is done in > VMWare. It would be a windows driver that acts as a dumb stub and > forwards every request to the dumb side. Since it would be designed > from the ground up only for QEMU, it could be limited in its > functionality to really only being a frame buffer and nothing else. > This would probably accelerate the emulation quite a bit. It is already done for NT (read the faq), at least for a linear frame buffer. Fabrice.