summary refs log tree commit diff stats
path: root/results/classifier/105/device/1572959
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/105/device/1572959')
-rw-r--r--results/classifier/105/device/157295926
1 files changed, 26 insertions, 0 deletions
diff --git a/results/classifier/105/device/1572959 b/results/classifier/105/device/1572959
new file mode 100644
index 00000000..77c2007f
--- /dev/null
+++ b/results/classifier/105/device/1572959
@@ -0,0 +1,26 @@
+device: 0.768
+socket: 0.683
+vnc: 0.674
+network: 0.658
+instruction: 0.526
+graphic: 0.491
+semantic: 0.452
+boot: 0.426
+mistranslation: 0.391
+KVM: 0.366
+other: 0.350
+assembly: 0.216
+
+bcm2835_property: inconsistent values when both setting and querying the framebuffer 
+
+As the framebuffer settings are copied into the result message before it is reconfigured, inconsistent behavior can happen when, for instance, you set with a single message the width, height, and depth, and ask at the same time to allocate the buffer and get the pitch and the size.
+
+In this case, the reported pitch and size would be incorrect as they were computed with the initial values of width, height and depth, not the ones the client requested.
+
+Attached is a patch also sent to the qemu-devel mailing list.
+
+
+
+The patch had been merged here:
+https://git.qemu.org/?p=qemu.git;a=commitdiff;h=27a5dc7be6a55b60039e3920
+