From: "Jamie Burns" <jamie.burns@dynamicexpression.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU Video Driver for Win NT-based systems
Date: Wed, 12 May 2004 19:52:14 +0100 [thread overview]
Message-ID: <001401c43852$3e9ae9b0$5500a8c0@shaggy> (raw)
In-Reply-To: 20040512174908.01420955.iosglpgc@teleline.es
Will windows GDI calls use DirectDraw if implemented? Or is there still a
need to accelerate GDI seperately?
----- Original Message -----
From: "Natalia Portillo" <iosglpgc@teleline.es>
To: <qemu-devel@nongnu.org>
Sent: Wednesday, May 12, 2004 5:49 PM
Subject: Re: [Qemu-devel] QEMU Video Driver for Win NT-based systems
> This is the same as making a DirectDraw (2D part of DirectX) driver.
>
> A full DirectX package of drivers will be great: DirectDraw (for 2D),
Direct3D (converting calls to OpenGL in host), DirectSound/DirectSound3D and
DirectMusic (for the sound card), and DirectInput (keyboards, mice,
joysticks)...
>
> On Wed, 12 May 2004 12:30:08 +0100
> "Jamie Burns" <jamie.burns@dynamicexpression.co.uk> wrote:
>
> > Wouldn't a 2D accelerator be a good idea first? ;o)
> >
> > If Windows asks for a "line" to be drawn, or a "blit-op" then could that
be
> > passed through to the QEMU emulated video hardware, which in turn could
> > simply get SDL or whatever to do the required operation. Then 2D
graphics
> > would speed up immensly.
> >
> > Are there any documents giving an overview of how the QEUM architecture
> > works in this respect? I would work on a driver in my spare time but
really
> > do not know where to start.
> >
> > J.
> >
> > ----- Original Message -----
> > From: "Grzegorz Kulewski" <kangur@polcom.net>
> > To: <qemu-devel@nongnu.org>
> > Sent: Wednesday, May 12, 2004 11:20 AM
> > Subject: Re: [Qemu-devel] QEMU Video Driver for Win NT-based systems
> >
> >
> > > On Wed, 12 May 2004, Filip Navara wrote:
> > > > Jean-Michel POURE wrote:
> > > > >>if anyone is interested I have created open source QEMU/Bochs
video
> > > > >>driver for Windows NT/2K/XP/2003.
> > > > >>Binaries - www.volny.cz/xnavara/qemuvid_bin.zip
> > > > >>Sources - www.volny.cz/xnavara/qemuvid_src.zip
> > > > >
> > > > >Are these VBE drivers?
> > > > >
> > > > Not in the sense of VBE 3.0 specification. I have such driver too,
but
> > > > it propably works only on ReactOS because of using undocumented API.
> > > >
> > > > >Can you describe the drivers and its capabilities in more details?
> > > >
> > > > The driver uses the Bochs/QEMU VBE I/O port, the same method as used
by
> > > > BXVGA. My implementation is a bit simplier, but still with the same
> > > > features. It also uses the Linear FrameBuffer feature of the
Bochs/QEMU
> > > > interface that wasn't available at the time when BXVGA was written.
> > >
> > > Are there any driver that works with win9x? Can you port your (or
write
> > > it from scratch)?
> > >
> > > Will your driver work in Bochs?
> > >
> > > Is it possible to create driver that emulates DirectX and OpenGL by
> > > sending the OpenGL commands to the host OpenGL libs. DirectX commands
> > > should probably be converted before into OpenGL.
> > >
> > >
> > > Thanks for your work,
> > >
> > > Grzegorz Kulewski
> > >
> > >
> > >
> > > _______________________________________________
> > > Qemu-devel mailing list
> > > Qemu-devel@nongnu.org
> > > http://mail.nongnu.org/mailman/listinfo/qemu-devel
> >
> >
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://mail.nongnu.org/mailman/listinfo/qemu-devel
>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-05-12 18:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 20:47 [Qemu-devel] QEMU Video Driver for Win NT-based systems Filip Navara
2004-05-12 8:01 ` Jean-Michel POURE
2004-05-12 10:05 ` Filip Navara
2004-05-12 10:20 ` Grzegorz Kulewski
2004-05-12 11:30 ` Jamie Burns
2004-05-12 16:49 ` Natalia Portillo
2004-05-12 17:51 ` Grzegorz Kulewski
2004-05-12 19:05 ` Fabrice Bellard
2004-05-12 20:10 ` Grzegorz Kulewski
2004-05-13 3:52 ` Natalia Portillo
2004-05-13 8:23 ` David Holm <dholm@gentoo.org>
2004-05-12 21:16 ` vaise
2004-05-12 18:52 ` Jamie Burns [this message]
2004-05-12 20:29 ` Natalia Portillo
2004-05-12 21:31 ` Filip Navara
2004-05-12 21:52 ` Grzegorz Kulewski
2004-05-12 22:57 ` Jamie Burns
2004-05-12 23:04 ` Filip Navara
2004-05-13 3:56 ` Natalia Portillo
2004-05-13 7:53 ` Filip Navara
2004-05-13 9:56 ` Jamie Burns
2004-05-14 15:21 ` Natalia Portillo
2004-05-14 16:58 ` Filip Navara
2004-05-12 13:51 ` Filip Navara
2004-05-12 14:06 ` Grzegorz Kulewski
2004-05-12 15:40 ` Martin Garton
2004-05-12 18:12 ` Natalia Portillo
2004-05-12 18:38 ` Fabrice Bellard
2004-05-12 21:19 ` vaise
2004-05-12 19:52 ` Lionel Ulmer
2004-05-20 15:43 ` [Qemu-devel] Again Ishwar Rattan
2004-05-20 19:42 ` Pavel Janík
2004-05-21 1:18 ` Ishwar Rattan
2004-05-21 13:02 ` Ishwar Rattan
2004-05-21 15:39 ` [Qemu-devel] Minix-2.0.4 boot?? Ishwar Rattan
2004-05-23 17:16 ` Jim C. Brown
2004-05-21 19:54 ` [Qemu-devel] Again Pavel Janík
2004-05-21 21:40 ` Ishwar Rattan
2004-05-23 11:49 ` Pavel Janík
2004-05-20 20:52 ` vaise
2004-05-20 21:09 ` Ishwar Rattan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001401c43852$3e9ae9b0$5500a8c0@shaggy' \
--to=jamie.burns@dynamicexpression.co.uk \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).