From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?J=F6rg?= Krause Date: Fri, 29 Jul 2016 18:23:13 +0200 Subject: [Buildroot] [PATCH] warpboard: linux.fragment: Do not use CONFIG_BRCMFMAC as built-in In-Reply-To: <1469799930-20206-1-git-send-email-fabio.estevam@nxp.com> References: <1469799930-20206-1-git-send-email-fabio.estevam@nxp.com> Message-ID: <1469809393.3805.12.camel@embedded.rocks> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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 > --- > ?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