[fedora-arm] Re: Bluetooth on Pinebook Pro

Hello Peter,

you're right: what a mess with this part.

 See below at you're remarks.

Am 09.08.24 um 16:21 schrieb Peter Robinson:

Hi Andreas,    

first: don't know if Bluetooth has worked before. If updated today the laptop and noticed Bluetooth isn't working.  

  Nope, the bliuetooth for the brcmfmac parts is complicated.    

dmesg | grep -i bluetooth missed 'brcm/BCM4345C5.hcd    After searching Internet I've found https://copr.fedorainfracloud.org/coprs/jwillikers/pinebook-pro and installed ap6256-firmware-2020.02-10.fc39.aarch64.rpm  

  Well per the rules for copr that shouldn't be there, but that aside....    There's two different WiFi parts, both using brcmfmac, in the Pinebook  Pro so it will depend on which one you have.    One of those parts is a Cypress part, now part of Infineon, and the  WiFi for that part will work OOTB. The WiFi for the synaptics part  won't work OOTB. That should tell you what variant of the HW you have.  You then need to go and find the right version of the BT firmware for  the one you have because neither of those firmware are upstream.    The most useful bit of debug is actually from the wifi module:    # dmesg | grep FWID  [   20.285673] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4356/2  wl0: Apr  9 2021 00:40:07 version 7.35.349.104 (775a9ab CY) FWID  01-64b609e0

What I have:

[   37.944145] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version 7.45.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84

BTW: for the WIFI-Part I've installed https://fedora.roving-it.com/brcm-pinebookpro-0.0-1.noarch.rpm from your nullrOute BLOG.

    The two letter right before the FWID tells you who makes the module.  The above is from the Rock960 which has a Cypress part.    Basically Broadcom made the original HW, they then sold it to  Cypress... but kept rights to it.... then Broadcom sold it to  Synaptics.... but kept the rights to it. So there's 3 vendors making  similar but not the same HW, in all cases the BT firmware can only be  described as a mess!  

Any hint where I can the correct firmware ?

  Peter