[Qemu-devel] [Bug 1777672] Re: QEMU aarch64 virtual/physical frame buffer

2018-08-10 Thread David Hoelzer
The virtual size must be at least the size of the physical display. One approach toward double-buffering is to make the virtual height twice the physical height. To "flip" the displays you simply change the start of the visible view port. See these: https://lb.raspberrypi.org/forums/viewtopic.p

[Qemu-devel] [Bug 1777672] Re: QEMU aarch64 virtual/physical frame buffer

2018-07-26 Thread David Hoelzer
Whoops.. Forgot to include the QEMU command line: qemu-system-aarch64 -M raspi3 --kernel kernel8.img -serial stdio -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1777672 Title: QEMU aarch64 virtual

[Qemu-devel] [Bug 1777672] Re: QEMU aarch64 virtual/physical frame buffer

2018-07-26 Thread David Hoelzer
Certainly! Attached. If you start the attached on a piece of hardware, it will start and display fine.. If you start it in QEMU, it will start but display a double-height screen rather than limiting the physical screen to the specified dimensions. (The virtual display is double-height in prep

[Qemu-devel] [Bug 1777672] [NEW] QEMU aarch64 virtual/physical frame buffer

2018-06-19 Thread David Hoelzer
Public bug reported: I fully recognize that the error here could be mine, but the code is pretty simple and straightforward; When emulating a Raspberry PI 3 using aarch64 and allocating a virtual framebuffer larger than the physical frambuffer (for double-buffering purposes), the QEMU window shows