Once the kernel takes over from iBoot, there’s a lot of hardware to get running before the SSV can be properly validation, and kernel extensions loaded.
M1 Pro
Sometimes known as iBoot1 and iBoot2, they start work with the LocalPolicy for the intended boot volume, validating its vital components.
Understanding each of the four stages in the Secure Booting of an M1 Mac. These are summarised in diagram available here.
macOS manages the loading and frequency of M1 cores according to the QoS set, and rules which differ between the original M1 and the M1 Pro.
How the two Efficiency cores in the M1 Pro and Max chips can match the performance of all four E cores in the original M1.
A better Disk Utility, understanding Spotlight, Time Machine to APFS, an introduction to ARM assembly language, Shortcuts, and wiping it all.
There’s a fundamental difference in the way that Intel and M1 Macs store and load their ‘firmware’, which enables the M1 Mac to load and run difference versions of iBoot.
This article has now been extensively corrected and modified.
How can the two E cores in an M1 Pro/Max apparently match the performance of the four in the original M1? Answers, please.
Some apps and other code doesn’t appear to run faster on M1 chips, and some even runs more slowly. Could this be a result of it not using the best acceleration for vectors and matrices?
