From: James Lancaster <james@kirk.math.twsu.edu>
To: Qemu-devel@nongnu.org
Subject: [Qemu-devel] Problems with Qemu 0.7.2
Date: Fri, 21 Oct 2005 16:05:08 -0500 [thread overview]
Message-ID: <200510211605.08561.james@kirk.math.twsu.edu> (raw)
(With or without kqemu)
1) When switching from qemu, it doesn't like letting go of the mouse. If you
don't have it grabbed, and click on another window, it will grab the mouse
again, and the title bar will cycle through "Qemu" and "Qemu - Press ctrl-alt
to exit grab. If you use the keyboard to move the focus, it acts as it should
(in other words, no qemu grabbing).
2) "Video memory" is somehow being corrupted by changing resolution. See:
http://kirk.math.twsu.edu/family/james/pics/computer/qemu-visual-errors1.png
for the effect of switching from 800x600 to 640x480. (The other way it does
not result in corruption.) Also changing from 16-bit to 24-bit causes
corruption. (Similar to that seen in the screenshot. I can't detect a
definite pattern, other than text and some icons display correctly.)
3) The video doesn't appear to handle ARGB as can be seen in the screenshot:
http://kirk.math.twsu.edu/family/james/pics/computer/swiftshader-errors.png
If you zoom in on that one, to see individual pixels, one can notice a dark,
blue, green, red pattern. (Second screenshot dumped from the monitor:
http://kirk.math.twsu.edu/family/james/pics/computer/swiftshader-errors.ppm)
(Oh yeah, people on this list might want to look at Transgaming's software
directx8/9 renderer if they want 3d (swiftshader, formerly swshader, webpage:
http://www.transgaming.com/swiftshader.php), with kqemu, as now cpu is cheap,
graphics aren't. (Unfortunately, as one can see from the screenshots in 3,
there are problems))
James L
next reply other threads:[~2005-10-21 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 21:05 James Lancaster [this message]
2005-10-22 4:14 ` [Qemu-devel] Problems with Qemu 0.7.2 James Lancaster
2005-10-22 14:40 ` Jim C. Brown
2005-10-25 14:14 ` Ryan Rempel
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=200510211605.08561.james@kirk.math.twsu.edu \
--to=james@kirk.math.twsu.edu \
--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).