Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

carpediem234

macrumors newbie
Original poster
Apr 26, 2025
2
0
Hello all! This is long-winded, the primary aspects of the question are listed at the bottom.

I am deeply fascinated by open and secure computing. I have grown to deeply dislike x86 and ARM because of this, what with egregious licensing terms/fees and the dubious CSME/PSP/TrustZone coprocessors.

This lead me to RISC-V, the subsequent realization that we are still a long way off from RISC-V chips with performance suited to desktop use, (though I hold out hope that one day, hopefully within the next few decades, we will see a silicon fab producing powerful Hazard3 or 4, or 20 by that point-derived CPUs) and then POWER. (Also SPARC, MIPS, and other obscure open RISC ISAs, but I'd like at least some modern app support and a computer made this century to run them on.)

Now, I'm fully aware the POWER ISA wasn't handed off to the Linux Foundation until 2019, and that the design schematics for the 970MP will most definitely never see the light of day. BUT! What I have read of Apple utilizing Sun's Open Firmware spec and the belief that there isn't some shady coprocessor that I'm not allowed to see doing nefarious things in the background has piqued my interest regarding PowerPC Macs, in particular the last and most powerful of the line (If, of course, point 1 means what I hope it means and point 2 is correct.)

Truthfully, what I'm really looking to buy is something from Raptor Computing, but I wouldn't want to spend a stupendously inflated amount of money on one of their POWER9 systems when rumor has it they're working in conjunction with a silicon fab startup on POWER10 systems.

So, this is my overly-complex and needy rationale for wanting a Power Mac G5 Quad. Essentially, it will be an interim to familiarize myself with POWER and wait for the system I really want (fingers crossed Raptor's supply chain gets rebuilt and I don't have to pay $6k for their base, 4 Core/8GB RAM system that launched at $1k pre-lockdown!)

Whether or not I should buy one depends on the answers to these two questions:

1) When we say "Open Firmware" do we mean that the source code is publicly available or do we mean that Sun defined some things firmware needs to do and then Apple just made their own proprietary firmware that does those things?

2) Do the PowerPC 970MPs have some kind of coprocessor analogous to the above mentioned CSME, PSP, and TrustZone? If they do, is the code powering them available to audit in some way?

I've had no luck with finding answers to these questions, so I figured you all would be the most knowledgeable people to ask. Any insight greatly appreciated! :^)
 
Last edited:
Well ... I don't think the G5 Open Firmware is very "open". When I went looking, I couldn't even find a command line reference document for it. I posted here at MacRumors, asking if anyone had such a document, but no one did. I did get a list of known commands that a user has stitched together over time, but that was it. Open? I don't think so.
 
Last edited:
On the coprocessor question, each Power Mac G5 incorporates an SMU (System Management Unit), which appears to have an embedded processor in it. This from "Mr. Google":

"The SMU is a microcontroller chip on the logic board, responsible for managing power functions, including fan speed and thermal conditions [ ... ] The SMU interacts with the processor to manage power usage and thermal management."
 
Well ... I don't think the G5 Open Firmware is very "open". When I went looking, I couldn't even find a command line reference document for it. I posted here at MacRumors, asking if anyone had such a document, but no one did. I did get a list of known command that a user has stitched together over time, but that was it. Open? I don't think so.
Not Doc: https://ss64.com/mac/ .
 
1) When we say "Open Firmware" do we mean that the source code is publicly available or do we mean that Sun defined some things firmware needs to do and then Apple just made their own proprietary firmware that does those things?
Source code is not publicly available. Sun defined some things firmware needs to do and then Apple just made their own proprietary firmware that does those things.

There's an Open Firmware spec. There's various bus bindings for the spec (SCSI, PCI, block devices, graphics devices, etc). All are pdf documents, some with sample code.
https://openfirmware.info/IEEE_1275-1994
https://openfirmware.info/Bindings

Open Firmware on Power Macs has some assembly code and some precompiled fcode in the Open Firmware dictionary. Most of it is fcode images that are compiled into the Open Firmware dictionary using the precompiled part of Open Firmware dictionary. The fcode images can be converted to Forth to make it easier to read. Most of the words in later versions of Open Firmware have names. The names might not be very descriptive but it's better than earlier version of Open Firmware that did not name all the words.
https://forums.macrumors.com/thread...l-work-in-a-beige-power-macintosh-g3.2303689/

2) Do the PowerPC 970MPs have some kind of coprocessor analogous to the above mentioned CSME, PSP, and TrustZone? If they do, is the code powering them available to audit in some way?
I don't think so?
I suppose if there was such a thing, the code would be in the HWInit or Start part of ROM that happens before Open Firmware. Or it could be in the Open Firmware.
Or it could be in the Mac OS X kexts. Some of the kexts have source code.
https://opensource.apple.com
I suppose you should look in the IO Registry in Mac OS X to find what the kext might be. Use the IORegistry.app or the ioreg command. The platform expert kexts may have some Power Mac model specific code (for features that are not enumerated or outlined by the Open Firmware device tree).
 
Source code is not publicly available. Sun defined some things firmware needs to do and then Apple just made their own proprietary firmware that does those things.

There's an Open Firmware spec. There's various bus bindings for the spec (SCSI, PCI, block devices, graphics devices, etc). All are pdf documents, some with sample code.
https://openfirmware.info/IEEE_1275-1994
https://openfirmware.info/Bindings

Open Firmware on Power Macs has some assembly code and some precompiled fcode in the Open Firmware dictionary. Most of it is fcode images that are compiled into the Open Firmware dictionary using the precompiled part of Open Firmware dictionary. The fcode images can be converted to Forth to make it easier to read. Most of the words in later versions of Open Firmware have names. The names might not be very descriptive but it's better than earlier version of Open Firmware that did not name all the words.
https://forums.macrumors.com/thread...l-work-in-a-beige-power-macintosh-g3.2303689/


I don't think so?
I suppose if there was such a thing, the code would be in the HWInit or Start part of ROM that happens before Open Firmware. Or it could be in the Open Firmware.
Or it could be in the Mac OS X kexts. Some of the kexts have source code.
https://opensource.apple.com
I suppose you should look in the IO Registry in Mac OS X to find what the kext might be. Use the IORegistry.app or the ioreg command. The platform expert kexts may have some Power Mac model specific code (for features that are not enumerated or outlined by the Open Firmware device tree).
Extremely insightful, thank you very much!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.