I added the EDID too Openbios properties, but that didn’t do the trick:-(
Just really killing time while you and others work out what we need to run the FCode to the end.
On Jul 21, 2019, at 8:53 AM, BALATON Zoltan balaton@eik.bme.hu wrote:
On Sun, 21 Jul 2019, Jd Lyons wrote:
A thought on why our ATY ‘NDRV’s are going to abort:
I think the properties missing from the FCode ROM is really the EDID data from our virtual display device.
Because that's the most prominent or why? It could be any other ATY,* attribute as well or just because the card is not set up the way as the FCode would have done.
So it maybe worth propagating the EDID data on the device tree to see if this is the property the FCode ROM sets up for the ‘NDRV’ that we are missing.
You can try that if you want but maybe easier to try other attributes first as they are simpler to add. You can get the edid blob bytes with:
qemu-edid | od -t x1
You only need the first 128 bytes because that's what drivers look at. Then you would need to add this to device-tree somehow, probably the same way as FCode adds NDRV.
I'd rather fix OpenBIOS to work but if you want to experiment with random options you could try, maybe you can identify what's needed that way.
Regards, BALATON Zoltan