Re: Missing dimm-info properties in openbios ?

[Andrew Randrianasulu]

On Wed, Mar 19, 2025 at 5:35 PM Andrew Randrianasulu
<randrianasulu@gmail.com> wrote:
>
>
>
> ср, 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
>
>

reapplied two patches on top of-current quemu, but sadly it dos not work?


netbsd10$ ~/src/qemu/build/qemu-system-ppc -bios
~/src/MacROMan/TestImages/4MB\ ROMs/1997-11\ -\ 79D68D63\ -\ Power\
Mac\ G3\ desktop.ROM    -d unimp -device
ati-vga,addr=0x12,romfile=/home/guest//src/qemu/build/ati_oem_rage128pro_136_agp_full.rom
-serial stdio -m 256 -M g3beige
portA_write unimplemented
CUDA: unimplemented GET_SET_IIC write 0x45 3
CUDA: unimplemented GET_SET_IIC write 0x45 3
CUDA: unimplemented GET_SET_IIC write 0x45 3
CUDA: unimplemented GET_SET_IIC write 0x45 3
netbsd10$
netbsd10$
netbsd10$
netbsd10$ ~/src/qemu/build/qemu-system-ppc -bios
~/src/MacROMan/TestImages/4MB\ ROMs/1997-11\ -\ 79D68D63\ -\ Power\
Mac\ G3\ desktop.ROM    -d unimp -device
ati-vga,addr=0x12,romfile=/home/guest//src/qemu/build/ati_oem_rage128pro_136_agp_full.rom
-serial stdio -m 256 -M g3beige
portA_write unimplemented
CUDA: unimplemented GET_SET_IIC write 0x45 3
CUDA: unimplemented GET_SET_IIC write 0x45 3
CUDA: unimplemented GET_SET_IIC write 0x45 3
CUDA: unimplemented GET_SET_IIC write 0x45 3
CUDA: unimplemented GET_SET_IIC write 0x45 3
CUDA: unimplemented GET_SET_IIC write 0x45 3
CUDA: unimplemented GET_SET_IIC write 0x45 3
CUDA: unimplemented GET_SET_IIC write 0x45 3
CUDA: unimplemented GET_SET_IIC write 0x45 3
netbsd10$


Note, amount of CUDA messages differ between two runs!







>
>> There are several versions, the two we've tried
>> were Rage128pd and Rage128ps and these should work. Be aware that ATI
>> Rage, Rage Pro, Rage 128 and Rage 128 Pro are all different cards...
>>
>> > Also a bit of rebase on my end needed ...
>> >
>> >
>> >>> Reason to ask: NetBSD/macppc only can be booted with 256mb ram or less in
>> >>> Qemu.
>> >>
>> >> Does it use SPD for that?
>> >
>> >
>> > not directly, as comment indicates.  Linux/macos/ISX happy with way it
>> > currently set up, but NetBSD not.
>>
>> How does NetBSD find the memory size then?
>
>
> Good question .. i looked for word "memory" and ended up in this file, but it 
> might be really just for user information ... :( {spdmem }
>
>
>
>
>> It should be in it's source
>> somewhere than that should explain what the issue is with other than 256M.
>>
>> > I wonder if there some qemu generic machinery for providing more exact dimm
>> > sizes? I think qemu-system-x86_64  provide something via acpi ....
>>
>> I think the generic way for hardware info on PowerMac is the device-tree
>> and looks like Apple puts the dimm-info properties for this. I don't know
>> it there's a standard way for it but probably not, that's why Apple come
>> up with this dimm-info. But why would an OS care about that if it has the
>> memory size? This info is mostly useful for the firmware to set up the
>> memory controller. At the OS level all you can do with it is display it to
>> the user maybe as hardware info.
>>
>> Regards,
>> BALATON Zoltan

0002-From-BALATON-Zoltan-balaton-eik.bme.hu.patch
Description: Text Data

0001-From-BALATON-Zoltan-balaton-eik.bme.hu.patch
Description: Text Data