** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914535
Title:
PL110 8-bit mode is not emulated correctly
Status in QEMU:
Invalid
Bug description
I think unless you can either (a) show that QEMU is behaving differently
from the real hardware or (b) point at what bit of the hardware
documentation QEMU's implementation is not following, then this doesn't
really sound like it's a bug in QEMU.
--
You received this bug notification because you
Well... I don't have any ARM Versatile Express board. Also,
documentation and manuals are not saying much about it
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914535
Title:
PL110 8-bit mode is n
On Mon, 22 Feb 2021 at 12:18, Vadim Averin <1914...@bugs.launchpad.net> wrote:
>
> So how can I manage it to display grayscale?
Programme the palette with exclusively shades of grey ?
The question here really is: is QEMU behaving differently
from the real vexpress-a15 hardware here? If it is, the
So how can I manage it to display grayscale?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914535
Title:
PL110 8-bit mode is not emulated correctly
Status in QEMU:
New
Bug description:
When
Anyway, on first investigation I'm not sure what QEMU's pl11x model is doing
wrong. The 8-bit mode is a palette-based setup, where the guest must program in
the RGB values it wants to use into the palatte registers as RGB555 data:
https://developer.arm.com/documentation/ddi0293/c/programmer-s-m
So, were you able to reproduce it?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914535
Title:
PL110 8-bit mode is not emulated correctly
Status in QEMU:
New
Bug description:
When the emulat
Lucky I looked at your screenshot, as half the repro instructions are only
given in that!
When the guest gets to a shell prompt, one needs to type:
# fbset -depth 8
# fbset
# dd if=/dev/urandom of=/dev/fb0
--
You received this bug notification because you are a member of qemu-
devel-ml, which i
Archive with all the demo files (kernel, disk image, dtb file, screenshot of
the bug):
https://avevad.ddns.net/storage/qbug.tar
QEMU commandline:
qemu-system-arm -serial stdio -M vexpress-a15 -dtb vexpress-v2p-ca15_a7.dtb
-smp 4 -m 256M -kernel zImage_new -append "console=ttyAMA0
root=/dev/mmc
Do you have a test case (QEMU command line and all necessary image
files) that demonstrates this, please ?
** Tags added: arm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914535
Title:
PL110 8-
10 matches
Mail list logo