qemu-ppc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Missing dimm-info properties in openbios ?


From: Andrew Randrianasulu
Subject: Re: Missing dimm-info properties in openbios ?
Date: Thu, 20 Mar 2025 20:16:12 +0300



чт, 20 мар. 2025 г., 19:53 BALATON Zoltan <balaton@eik.bme.hu>:
On Thu, 20 Mar 2025, Andrew Randrianasulu wrote:
> On Thu, Mar 20, 2025 at 2:23 PM Andrew Randrianasulu
> <randrianasulu@gmail.com> wrote:
>> ср, 19 мар. 2025 г., 17:35 Andrew Randrianasulu <randrianasulu@gmail.com>:
>>> ср, 19 мар. 2025 г., 16:40 BALATON Zoltan <balaton@eik.bme.hu>:
>>>>
>>>> On Wed, 19 Mar 2025, Andrew Randrianasulu wrote:
>>>>> ср, 19 мар. 2025 г., 16:04 BALATON Zoltan <balaton@eik.bme.hu>:
>>>>>> On Wed, 19 Mar 2025, Andrew Randrianasulu wrote:
>>>>>>> I was reading NetBSD's
>>>>>>>
>>>>>>> sys/arch/macppc/macppc/memory.c
>>>>>>>
>>>>>>> and there is comment:
>>>>>>>
>>>>>>> *<---->The EEPROMs for Serial Presence Detect don't show up in the
>>>>>>> * <--->OpenFirmware tree, but their contents are available through the
>>>>>>>
>>>>>>> * <--->"dimm-info" property of the "/memory" node.  To make the
>>>>>>> * <--->information available, we fake up an I2C bus with EEPROMs
>>>>>>> * <--->containing the appropriate slices of the "dimm-info" property.
>>>>>>>
>>>>>>> But I can't find "dimm-info" in openbios source tree ?
>>>>>>>
>>>>>>> Is it simply not implemented?
>>>>>>
>>>>>> I think OpenBIOS knows nothing about SPD and Mac i2c so it won't look at
>>>>>> them. It gets memory size from fw_cfg which it adds to /memory node and
>>>>>> that's it. Does NetBSD work on g3beige?
>>>>>
>>>>>
>>>>> yes, this is where I noticed that keyboard on cuda/adb acts strange not
>>>>> only in macos ..... but may be not all hosts affected that badly.
>>>>>
>>>>>
>>>>> You can try that with the Apple
>>>>>> ROM then and see if that works.
>>>>>>
>>>>>
>>>>>
>>>>> yeah, I just need to find this rage128 option ROM ;) (dingusppc seems to
>>>>> get it from main rom or somewhere else ...?).
>>>>
>>>> I think DingusPPC emulates the older ATI GPU that beige G3 had and the
>>>> machine ROM contains driver for that so no ROM is needed. The G4 had
>>>> Rage128Pro so that may have ROM for it but Rage128Pro on G3 probably needs
>>>> a Mac ROM for the newer card. These are easy to find if you look for "ati
>>>> mac roms" for example.
>>>
>>>
>>> like this?
>>>
>>> https://lists.ucc.gu.uwa.edu.au/pipermail/cdg5/2020-July/000270.html
>>>
>>>
>>>
>>>> There are several versions, the two we've tried
>>>> were Rage128pd and Rage128ps
>>
>>
>> Ah, found site with grand total of four rage128 Mac firmwares!
>>
>> https://web.archive.org/web/20240625145211/http://themacelite.wikidot.com/wikidownloads2
>>
>> will try all them ;) two AGP, two PCI ...
>
> So far only one worked with graphics:
>
> netbsd10$ ~/src/qemu/build/qemu-system-ppc -bios
> ~/K38_sdcard1/Documents/1997-11\ -\ 78F57389\ -\ Power\ Mac\ G3\
> \(v3\).ROM     -d unimp,guest_errors -device
> ati-vga,addr=0x12,romfile=/home/guest/ati-fcode-roms/ati_oem_rage128pro_110_agp_full.rom
>   -m 256 -M g3beige  -drive if=mtd,format=raw,file=nvram.img -cdrom
> ~/obj/releasedir/images/NetBSD-10.99.12-macppc.iso -icount shift=1

That's good enough for me and I'm not sure older ROM versions are supposed
to work. Consider that according to
https://en.wikipedia.org/wiki/Power_Macintosh_G3 the Gossamer G3 that
g3beige emulates was produced between 1997 November and 1998 December and
had an ATI Rage II+, Rage Pro or Rage Pro Turbo on board. While
https://en.wikipedia.org/wiki/ATI_Rage#List says the Rage 128 Pro is from
1999 August and it was not available on Macs before the later G4
PowerMac3,1 in late 1999 so I think it's likely that it needs the latest
firmware version (even if that's still older than the card but I'm not
sure if 1997-11 date is correct for v3 ROM but it could well be the ATI
card's ROM was developed for that in 1999 and not tested for compatibility
with older versions at that point). Maybe there's some changelog of Mac
firmware updates somewhere that could confirm this but I think it's
sensible to say: use the latest version or face the consequences of
trying untested combinations.

well, I am re-reading 40 forum pages of 

https://forums.macrumors.com/threads/question-how-powerful-of-a-graphics-card-will-work-in-a-beige-power-macintosh-g3.2303689/page-23


some interesting fcode drawing programs were posted there, so a lot of time will be well spend on playing with new toy. 

I might try netboot or tftp something too, because it seems on this rom version I can't dev into ata devices ...

Thanks for all your work put into this. I still think that putting few remarks about rom/option rom /command line tested may be on Zoltan's QMiga developer page will be of some use for future us.

I looked at scsi controller in dingusppc and it was 10kb for MESH + 30 kb or so for actual controller. Booted 9.0/9.1 ok, but for me even few new lines is groundbreaking so I do not think we will see scsi support for this g3 machine in qemu anytime soon ;) :(

Controller itself seems to be documented 
1994_AM79C940.pdf, arh, no this is MACE ethernet, all 10mbit of it.

scsi is ..

NCR53C94/Am53CF94

and there is bunch new and old docs on mach64 on bitsavers I downloaded

GCS-C03300_3D_RAGE_LT_PRO_Technical_Reference_Manual_Rev_1.01_1997.pdf
PRG-215R3-00-10_RAGE_PRO_and_Derivatives_Programmers_Guide_Rev_1.0_200003(1).pdf
PRG-215R3-00-10_RAGE_PRO_and_Derivatives_Programmers_Guide_Rev_1.0_200003.pdf
RRG-G02700_mach64_Register_Reference_Guide_ATI-264VT_and_3D_RAGE_1996.pdf
RRG-G03300_Rev2.01x_3D_RAGE_LT_PRO_Register_Reference_Guide_199804.pdf
RRG-G04500-C_RAGE_128_PRO_Register_Reference_Guide_Rev_1.01_200001.pdf
RRG-S00700-05_mach64_Register_Reference_Guide_1999410.pdf


but .... myself is not up to such tasks, sadly. Despite all those years tinkering with Slackware and mesa.

Ah, btw - rpcs3 does have nv40-ish (RSX) emulation , hardware accelerated, but I am afraid it connected somewhat differently from pc/macs so not directly usable .... but at least one can read logs!


Regards,
BALATON Zoltan

reply via email to

[Prev in Thread] Current Thread [Next in Thread]