All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] warpboard: linux.fragment: Do not use CONFIG_BRCMFMAC as built-in
Date: Fri, 29 Jul 2016 18:23:13 +0200	[thread overview]
Message-ID: <1469809393.3805.12.camel@embedded.rocks> (raw)
In-Reply-To: <1469799930-20206-1-git-send-email-fabio.estevam@nxp.com>

Hi Fabio,

On Fr, 2016-07-29 at 10:45 -0300, Fabio Estevam wrote:
> Selecting the driver CONFIG_BRCMFMAC as built-in causes some probe
> issues
> as we cannot guarantee that the brcmfmac driver will be probed after
> the
> rootfs has been mounted. The brcmfmac driver retrieves the firmware
> and
> nvram file from the rootfs, so the rootfs should be mounted first.
> 
> To avoid such issues let the CONFIG_BRCMFMAC be built as module,
> which is
> the original option in imx_v6_v7_defconfig.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
> ---
> ?board/freescale/warpboard/linux.fragment | 1 -
> ?1 file changed, 1 deletion(-)
> 
> diff --git a/board/freescale/warpboard/linux.fragment
> b/board/freescale/warpboard/linux.fragment
> index 736b9cd..892d0cb 100644
> --- a/board/freescale/warpboard/linux.fragment
> +++ b/board/freescale/warpboard/linux.fragment
> @@ -1,2 +1 @@
> ?CONFIG_CFG80211_WEXT=y
> -CONFIG_BRCMFMAC=y

Shouldn't this be "CONFIG_BRCMFMAC=m"?

J?rg

  reply	other threads:[~2016-07-29 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 13:45 [Buildroot] [PATCH] warpboard: linux.fragment: Do not use CONFIG_BRCMFMAC as built-in Fabio Estevam
2016-07-29 16:23 ` Jörg Krause [this message]
2016-07-29 16:29   ` Fabio Estevam
2016-07-29 16:34     ` Jörg Krause
2016-07-30 10:17 ` Thomas Petazzoni

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=1469809393.3805.12.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --cc=buildroot@busybox.net \
    /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.