- Joined
- Feb 18, 2019
- Messages
- 358
- Motherboard
- ASUS Z690 Maximus Extreme
- CPU
- i9-12900KF
- Graphics
- 6900XT
- Mac
- Mobile Phone
CaseySJ,
In this post here, you mentioned about real Macs maybe having Alpine Ridge at UPSB.
When running DCPIManager on a 2018 MacbookAir (where I saw 0x1578 at UPSB with IORegistryExplorer), I see that both an Alpine Ridge device ID (0x1578), and a Titan Ridge device is listed (0x15EA).
On our mobos, since we only have one TB device (Titan Ridge or Alpine Ridge), will we want to accurately ID UPSB as 0x15EA (or whatever our Titan Ridge's model's ID is), rather than 0x1578? Or, is the idea to force the Titan Ridge into pretending to be an Alpine Ridge device (0x1578) at UPSB, while being a Titan Ridge at USB0 (0x15EA)?
Maybe it depends on what Apple is really doing: does Apple use both an Alpine Ridge and a Titan Ridge controller, or is it only a cosmetic device name at UPSB with only one Titan Ridge controller being present?
(BTW, what app do you use to read the ROM files; or are you using tools in Windows?)
In this post here, you mentioned about real Macs maybe having Alpine Ridge at UPSB.
When running DCPIManager on a 2018 MacbookAir (where I saw 0x1578 at UPSB with IORegistryExplorer), I see that both an Alpine Ridge device ID (0x1578), and a Titan Ridge device is listed (0x15EA).
On our mobos, since we only have one TB device (Titan Ridge or Alpine Ridge), will we want to accurately ID UPSB as 0x15EA (or whatever our Titan Ridge's model's ID is), rather than 0x1578? Or, is the idea to force the Titan Ridge into pretending to be an Alpine Ridge device (0x1578) at UPSB, while being a Titan Ridge at USB0 (0x15EA)?
Maybe it depends on what Apple is really doing: does Apple use both an Alpine Ridge and a Titan Ridge controller, or is it only a cosmetic device name at UPSB with only one Titan Ridge controller being present?
(BTW, what app do you use to read the ROM files; or are you using tools in Windows?)
Attachments
Last edited: