From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34)
	id 1BO2mw-0005lY-Bn
	for qemu-devel@nongnu.org; Wed, 12 May 2004 19:05:22 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34)
	id 1BO2mP-0005Px-At
	for qemu-devel@nongnu.org; Wed, 12 May 2004 19:05:20 -0400
Received: from [194.228.2.92] (helo=smtp-out4.iol.cz)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1BO2mO-0005PY-Pa
	for qemu-devel@nongnu.org; Wed, 12 May 2004 19:04:49 -0400
Received: from [194.228.180.133] (a133-180.dialup.iol.cz [194.228.180.133])
	by smtp-out4.iol.cz (Internet on Line ESMTP server) with ESMTP id
	433EE31790
	for <qemu-devel@nongnu.org>; Thu, 13 May 2004 01:04:48 +0200 (CEST)
Message-ID: <40A2AD90.5000306@volny.cz>
Date: Thu, 13 May 2004 01:04:48 +0200
From: Filip Navara <xnavara@volny.cz>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] QEMU Video Driver for Win NT-based systems
References: <40A13BFD.3010709@volny.cz>
	<200405121001.56247.jm@poure.com>	<40A1F6D6.9090609@volny.cz>	<Pine.LNX.4.58.0405121212190.8750@alpha.polcom.net>	<000601c43814$7c5a2380$5500a8c0@shaggy>	<20040512174908.01420955.iosglpgc@teleline.es>	<001401c43852$3e9ae9b0$5500a8c0@shaggy>	<20040512212914.685d9f1b.iosglpgc@teleline.es>	<40A297CD.1020500@volny.cz>
	<Pine.LNX.4.58.0405122348160.19264@alpha.polcom.net>
In-Reply-To: <Pine.LNX.4.58.0405122348160.19264@alpha.polcom.net>
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: <http://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Grzegorz Kulewski wrote:

>On Wed, 12 May 2004, Filip Navara wrote:
>  
>
>>Natalia Portillo wrote:
>>    
>>
>>>DirectDraw is the accelerator for GDI.
>>>      
>>>
>>This is not correct. At the driver level GDI calls and DirectDraw calls 
>>are completly separate interfaces implemented different way.
>>    
>>
>
>You are unfortunatelly right. GDI was introduced a lot ealier than 
>DirectX (I think before win95).
>
Right, it was there since Windows 1.0.

> But GDI can be not accelerated by graphic 
>card but by qemu (using sdl or something like that) because today apps are 
>using GDI mainly for user interface and not for advanced drawing I think. 
>Right?
>  
>
Right, GDI is used mainly for UI drawing. It can be accelerated a bit. 
These GDI things can be *theoretically* optimized on the driver/HW level:
Alpha Blending, Gradient Fills, BitBlts/StretchBlts/TransparentBlts, 
Paths/Lines and HW Cursor. This is kind of what VMware does, their 
drivers pass some of the requests throught I/O ports (partially 
documented) to the emulator which executes the most common operations in 
the non-emulated host environment.

- Filip