From: Alex Beregszaszi <alex@fsn.hu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qvm86, kqemu and video speed
Date: Tue, 12 Apr 2005 18:38:43 +0200 [thread overview]
Message-ID: <20050412183843.1a3ad827@caprice.artificis.hu> (raw)
In-Reply-To: <425A84B0.60200@praguespringpeople.org>
Hi,
> I understand qvm86 and kqemu provide some virtualisation of the host
> machine, including allowing the guest some direct memory access. Is it
> conceivable for these modules to be extended to allow the guest
> machine to directly write to host video memory, or else to a host
> memory buffer that is copied into the Qemu window?
I'm working on such a Direct Host Graphics custom "videocard". I'm
reusing the common vga code, while adding an mmio and framebuffer range
for the direct stuff. Also it has a custom pci vendor/device id. It is
working quiet nicely, however, plenty of guest os drivers are needed
(preferably for different Windows versions - for Linux I have mine).
--
Alex Beregszaszi e-mail: alex@fsn.hu
Free Software Network cell: +36 70 3144424
next prev parent reply other threads:[~2005-04-12 16:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 14:07 [Qemu-devel] qvm86, kqemu and video speed Struan Bartlett
2005-04-11 15:01 ` James Mastros
2005-04-11 15:17 ` Paul Brook
2005-04-11 15:35 ` Struan Bartlett
2005-04-11 21:51 ` Struan Bartlett
2005-04-15 8:54 ` Struan Bartlett
2005-04-12 3:13 ` Darryl Dixon
2005-04-11 21:53 ` Struan Bartlett
2005-04-12 16:38 ` Alex Beregszaszi [this message]
2005-04-12 19:30 ` Fabrice Bellard
2005-04-13 3:57 ` use.reply-to.address
2005-04-13 8:06 ` Struan Bartlett
2005-04-13 18:12 ` Hetz Ben Hamo
2005-04-13 19:24 ` Leonardo E. Reiter
2005-04-13 20:09 ` Leonardo E. Reiter
2005-04-14 9:42 ` Thomas Steffen
2005-04-18 7:32 ` Oliver Gerlich
2005-04-19 6:15 ` emuls
2005-04-13 21:12 ` Jim C. Brown
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=20050412183843.1a3ad827@caprice.artificis.hu \
--to=alex@fsn.hu \
--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).