Re: [Qemu-devel] PMON2000 compilation and kernel question

[BALATON Zoltan]

On Thu, 7 Mar 2019, Andrew Randrianasulu wrote:
> distorted screen was when I tried 800x600 or 32 bpp ....

The screen resolution this binary tried to set was 640x480x16 but it used 
two screens, one at offset 0 which was not set up correctly due to flat 
panel registers not emulated and another for CRT at 0x5000000 which is 
outside VRAM. The window was switched to 640x480 but showed picture of the 
screen at 0 with wrong depth/stride so it showed at 4x size with dots 
instead of correct image. Maybe it could be fixed by emulating flat panel 
part of the chip but that's not used on the fulong2e so the pmon.bin 
should not set that up and should not put CRT outside of VRAM so I think 
config of this pmon was not correct for fulong2e.

> sha256sum /dev/shm/pmon-my/pmon/zloader.2edev/pmon.bin
> ecc82c621c33d140ac1ba01a70876f467e47a7cc9eb154a0647c227355d39e60  
> /dev/shm/pmon-my/pmon/zloader.2edev/pmon.bin

The one you've sent to me was:
$ sha256sum pmon.bin
4f2fdb964cb386a8ba5340b5b9999e7744c974b76b521ce940105c0c76c6387b  pmon.bin

> mac99 machine with your ati-vga device look like this (after upgrading X and 
> r128 driver)
> https://ibin.co/4ZKLzg90dFZA.png
> note again, this is with NoAccel (while strangely overlay still around via 
> xvinfo)

NoAccel just disables 2D but not overlay I think. Chip supports overlay 
but it's not emulated yet (plan to look at that after 2D) so any guest 
driver using it will probably not get picture for overlay (if it's not 
crashing due to unexpected data from device).

Regards,
BALATON Zoltan