On Sat, 20 Jul 2019, Jd Lyons wrote:
On Jul 20, 2019, at 11:30 AM, BALATON Zoltan balaton@eik.bme.hu wrote: On Sat, 20 Jul 2019, Jd Lyons wrote:
Using ATI ROM Xtender 1.2 with OS 9 and the ATY,Rage128v ‘NDRV’ i.e.
Where did you get Rage128v ROM and is it for Rage 128 instead of Rage128P i.e. Pro? If so it probably not supposed to work.
The ATI ROM Xtender is a bunch of disk based ‘NDRV’, for the Rage128 they match the “ name” property in the IOreg for our card. Changing the “ name” property you can test each one.
dev /pci/@f “ ATY,Rage128v” encode-string “ name” property boot
ATY,Rage128ns ATY,Rage128n ATY,Rage128o ATY,Rage128v
v1.2 contains these ns is a 32MB gram card, so is n, and o is a 16MB Vram card.
You can change how much vram is allocated with the vgamem_mb property (e.g. -device ati-vga,vgamem_mb=32 default is 16 and making it too big or unrealistic sizes probably breaks without warning) but it does not matter, this won't make it work better so probably best to leave it alone and test with a proper rom driver from a real card matching the model we're emulating rather than trying random ones because that just creates confusion because we don't know if it's not working becuase the driver sends wrong data for the card or because of emulation problems.
I'm still not convinced that these are correct. Doesn't Rage 128 Pro has Rage128P in it's name and then a lower case version letter such as p or s which is what I've seen in every device tree dump I've seen so far. So I think Rage128 without P might be a different GPU so drivers for that may not program the card correctly. Therefore you should only test with a driver for Rage128P. Then if it's not working it may be a problem with emulation (or missing setup from FCode ROM part).
Regards, BALATON Zoltan