[Feature request] Add info about attached firmware or codec

[dreamwhite]

In some kexts, such as AirportItlwm and IntelBluetoothFirmware, there's an IOReg property that tells the loaded firmware.

It would be convenient to have the same feature on:

• AppleALC (under HDEF device, with a property named IOCodec for example)
• BrcmPatchRAM (under the BRCMXXXXX Hub device, with a property named fw_name or Firmware)

I know that there's no practical difference, but at least when providing an IOReg makes it very easy to obtain more info about the codec/loaded firmware very quickly

P.S. Happy Millenium bug

[vit9696]

That might be useful indeed.

• For AppleALC it already shows the codec vendor id though, and for this reason it is fairly easy to figure it out.
• For BT it may be handy. CC @lvs1974, would you consider it?

[dreamwhite]

For AppleALC it already shows the codec vendor id though, and for this reason it is fairly easy to figure it out.

Well, I don't know if I'm missing something or not but when I open HDEF properties in IORegistryExplorer I see:

• vendor-id: <86 80 00 00>
• device-id: <71 9d 00 00>

My audio codec is ALC3254 aka ALC295. Where should I look?

[mikebeaton]

For AppleALC it already shows the codec vendor id though, and for this reason it is fairly easy to figure it out.

Well, I don't know if I'm missing something or not but when I open HDEF properties in IORegistryExplorer I see:

• vendor-id: <86 80 00 00>
• device-id: <71 9d 00 00>

My audio codec is ALC3254 aka ALC295. Where should I look?

Actually here and here - AudioDxe code includes the translation from known ids to strings, but I believe AppleALC does not.

[dreamwhite]

Thank you so much for your reply. Well yes, basically it translate the PCI IDs in a human readable format but that's not what I was looking for 😅

I mean, I still haven't found yet a way of identifying my audio codec name (ALC295) via IORegistryExplorer. Am I missing something?

[mikebeaton]

The translations are still available in AudioDxe code, here and here.

The codec id 0x0255 ties back to the CodecID in the AppleALC Info.plist, in my case here (allowing for dec/hex conversion), in your case it would be 0x0295 from here.

[dreamwhite]

Okay thank you so much! I figured it out before reading your comment but again thank you! What about BT instead?

[mikebeaton]

Okay thank you so much! I figured it out before reading your comment but again thank you!

Oh. Good... :-/

What about BT instead?

Go back to @vit9696's original comment!

[Andrey1970AppleLife]

[dreamwhite]

Wait, what's your WiFi/BT card model? Is it natively compatible with macOS or you're using BrcmPatchRAM?

[Andrey1970AppleLife]

BCM943225HMB macOS 12 with BlueToolFixup.kext

[dreamwhite]

BCM943225HMB macOS 12 with BlueToolFixup.kext

Oh okay so without any type of BrcmFirmwareData, right?

[Andrey1970AppleLife]

Yes, without.

[dreamwhite]

Yes, without.

Oh okay, what I was asking actually is getting the firmware name when using BrcmFirmwareData 😅

[dreamwhite]

Yes, without.

Oh okay, what I was asking actually is getting the firmware name when using BrcmFirmwareData 😅

Hi, any update on this? Don't wanna rush on you but rather know if it'll get implemented or not

[vit9696]

Well, could add, but I personally see no reason. Reopened in case anybody picks it up.