Re: Bug#797779: brcmfmac4330-sdio.txt from OpenElec fixes the issue
Hi Stefan,
I copied the debian-arm list, because this should be an issue which is present
on almost any ARM based SoC and there might exist solutions for other SoCs
already.
On Wednesday 02 September 2015 19:37:13 Stefan Lippers-Hollmann wrote:
> Hi
>
> On 2015-09-02, Rainer Dorsch wrote:
> > Hi,
> >
> > I copied brcmfmac4330-sdio.txt from OpenElec
> >
> > https://github.com/OpenELEC/wlan-firmware/blob/master/firmware/brcm/brcmfm
> > ac4330-sdio.txt
> >
> > to /lib/firmware/brcm
> >
> > which fixes the issue
>
> [...]
>
> brcmfmac4330-sdio.txt is OEM, respectively even device specific[1],
> nothing that would be generic enough (for all bcm4330 devices) to be
> shipped by Debian's firmware packages.
>
> On x86 systems this blob is typically provided in a UEFI variable (but not
> found automatically by the kernel, so you need to copy it from the UEFI
> variable to /lib/firmware). On embedded devices it needs to be provided by
> the manufacturer (not Broadcom, but the OEM vendor) of your wlan card
> (respectively the devboard).
>
> Regards
> Stefan Lippers-Hollmann
>
> [1] These blobs contain calibration data, regulatory domain settings
> and similar information, which is highly specific to your exact
> device. Using data from a different device would make it run out
> of its specifications (getting you in trouble with FCC, ETSI,
> etc.) and could even physically damage your device.
Are you saying that I opened the bugreport against the wrong package or that
this is not a bug at all?
Doesn't on an ARM system the device tree file contain embedded device specific
information, which is shipped with the kernel itself? And would this txt file
not fit perfectly in this category of information?
How is this issue addressed for other ARM SoCs?
Thanks
Rainer
--
Rainer Dorsch
http://bokomoko.de/
Reply to: