blob: a890703426a12017da3288a992495aba2b71c209 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
|
device: 0.768
socket: 0.683
vnc: 0.674
PID: 0.659
network: 0.658
files: 0.624
performance: 0.565
graphic: 0.491
semantic: 0.452
boot: 0.426
KVM: 0.366
other: 0.350
permissions: 0.349
debug: 0.310
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
|