diff options
author | Gerd Hoffmann <kraxel@redhat.com> | 2013-09-05 21:57:19 +0200 |
---|---|---|
committer | Gerd Hoffmann <kraxel@redhat.com> | 2013-09-10 11:14:08 +0200 |
commit | c58c7b959b93b864a27fd6b3646ee1465ab8832b (patch) | |
tree | 7e09d3987bd52d53adf403bce7b4449238f47ad5 /hw/sh4 | |
parent | 18b203850a859f1d4688baa8a0ddb8e7af55962f (diff) | |
download | qemu-c58c7b959b93b864a27fd6b3646ee1465ab8832b.zip qemu-c58c7b959b93b864a27fd6b3646ee1465ab8832b.tar.gz qemu-c58c7b959b93b864a27fd6b3646ee1465ab8832b.tar.bz2 |
qxl: fix local renderer
The local spice renderer assumes the primary surface is located at the
start of the "ram" bar. This used to be a requirement in qxl hardware
revision 1. In revision 2+ this is relaxed. Nevertheless guest drivers
continued to use the traditional location, for historical and backward
compatibility reasons. The qxl kms driver doesn't though as it depends
on qxl revision 4+ anyway.
Result is that local rendering is hosed for recent linux guests, you'll
get pixel garbage with non-spice ui (gtk, sdl, vnc) and when doing
screendumps. Fix that by doing a proper mapping of the guest-specified
memory location.
https://bugzilla.redhat.com/show_bug.cgi?id=948717
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'hw/sh4')
0 files changed, 0 insertions, 0 deletions