Hi Guillaume,

indeed that worked and I filed a bug to suggest the fix.
https://bugzilla.opensuse.org/show_bug.cgi?id=1169771

Now, what do you suggest to get to the next step, that is having a
fully functional Bluetooth stack?
I have managed to get Bluetooth working on my cubox-i, but that
requires a .hcd file not provided by the bcm43xx-firmware package, the
program brcm_patchram_plus and possibly an udev rule and a systemd
service.
Should I make a stand alone package and try to have it accepted, or
should I ask the maintainer to integrate everything into the
bcm43xx-firmware package?

Thanks for guidance.

Kind regards,

Alessio

Il giorno ven 17 apr 2020 alle ore 09:13 Guillaume Gardet
<guillaume.gar...@arm.com> ha scritto:
>
> Hi Alessio,
>
> > -----Original Message-----
> > From: Alessio Adamo <alessio.ad...@gmail.com>
> > Sent: 16 April 2020 21:40
> > To: OS-arm <opensuse-arm@opensuse.org>
> > Subject: [opensuse-arm] Possible bug in install-brcmfmac.sh [pkg bcm43xx-
> > firmware]
> >
> > Hi everybody,
> >
> > I was trying to achieve Bluetooth activation on my cubox-i, and while 
> > tinkering I
> > realized a putative bug in the script 'install-brcmfmac.sh' used by the 
> > package
> > 'bcm43xx-firmware'.
> > The script parses the file '/sys/firmware/devicetree/base/compatible'
> > looking for 'solidrun,cubox-i', however it is not successful, because in my 
> > personal
> > case it actually retrieves 'solidrun,cubox-i/q'.
> > Because of this, the symbolic link
> > '/lib/firmware/brcm/brcmfmac4330-sdio.txt' is not created and brcmfmac fails
> > with the following error messages:
> >
> > [   21.774391] brcmfmac: brcmf_fw_alloc_request: using
> > brcm/brcmfmac4330-sdio for chip BCM4330/4
> > [   21.833131] brcmfmac mmc0:0001:1: Direct firmware load for
> > brcm/brcmfmac4330-sdio.solidrun,cubox-i/q.txt failed with error -2
> > [   21.833205] brcmfmac mmc0:0001:1: Direct firmware load for
> > brcm/brcmfmac4330-sdio.txt failed with error -2
> >
> > The content of '/sys/firmware/devicetree/base/compatible' is:
> > solidrun,cubox-i/q^@fsl,imx6q^@
> >
> > Probably because it is a Cubox-i Pro Quad Core.
> > Should the pattern for case statement be changed into
> >
> > solidrun,cubox-i|solidrun,cubox-i/q)
> >
> > ?
>
> Could you give it a try and also report this problem on 
> https://bugzilla.opensuse.org please?
>
> Thanks,
> Guillaume
>
> >
> > Ciao
> > Alessio
> > --
> > To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
> > To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
>
> IMPORTANT NOTICE: The contents of this email and any attachments are 
> confidential and may also be privileged. If you are not the intended 
> recipient, please notify the sender immediately and do not disclose the 
> contents to any other person, use it for any purpose, or store or copy the 
> information in any medium. Thank you.
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Reply via email to