From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Fabio Estevam <festevam@gmail.com>,
Arend van Spriel <arend@broadcom.com>,
Hante Meuleman <meuleman@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
brcm80211-dev-list <brcm80211-dev-list@broadcom.com>
Subject: Re: brcm4330 fails to load on newer kernels
Date: Wed, 27 Jul 2016 22:51:53 +0200 [thread overview]
Message-ID: <57991EE9.30005@broadcom.com> (raw)
In-Reply-To: <CAOMZO5Cu_UO6L9wYy6eJUJwEE25BN-qeBRAMbFveFrJKHtF=aw@mail.gmail.com>
On 27-07-16 00:35, Fabio Estevam wrote:
> Hi,
>
> On a imx6sl-warp board with a brcm4330 I get the following results
> depending on the kernel version:
>
> - Kernel 4.4.15: place brcmfmac4330-sdio.bin and brcmfmac4330-sdio.txt
> in the rootfs and the kernel is able to read them correctly. wlan0 is
> present. All is fine.
>
> - Kernel 4.5.7: place brcmfmac4330-sdio.bin brcmfmac4330-sdio.txt in
> the rootfs and the kernel fails to load them:
>
> brcmfmac mmc1:0001:1: Direct firmware load for
> brcm/brcmfmac4330-sdio.bin failed with error -2
>
> Then I build brcmfmac4330-sdio.bin brcmfmac4330-sdio.txt into the
> kernel and then firmware is detected and wlan0 appears.
>
> - Kernel 4.7: I can place the firmware and nvram file into the rootfs
> or built-i and the following error is seen:
>
> brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
> brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
> brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
>
> So wlan0 never appears here.
>
> Does anyone have any suggestions about these different behaviours?
So for all kernel you have brcmfmac built-in the kernel or as a module?
Regards,
Arend
> Thanks,
>
> Fabio Estevam
>
next prev parent reply other threads:[~2016-07-27 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 22:35 brcm4330 fails to load on newer kernels Fabio Estevam
2016-07-27 20:51 ` Arend van Spriel [this message]
2016-07-27 20:57 ` Fabio Estevam
2016-07-28 18:37 ` Arend van Spriel
2016-07-29 1:05 ` Fabio Estevam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57991EE9.30005@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=festevam@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.