Public bug reported:
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.
** Affects: qemu
Importance: Undecided
Status: New
** Patch added: "Fix mbox_property"
https://bugs.launchpad.net/bugs/1572959/+attachment/4641358/+files/mbox_property.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1572959
Title:
bcm2835_property: inconsistent values when both setting and querying
the framebuffer
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1572959/+subscriptions
