On 07/04/2012 03:34 AM, Wei Ni wrote: > New options enabled: > * WIRELESS: (dependency) > * CFG80211: (dependency) > * WLAN: (dependency) > * BRCMFMAC: wlan driver, enable as module. > diff --git a/arch/arm/configs/tegra_defconfig b/arch/arm/configs/tegra_defconfig > +CONFIG_BRCMFMAC=m Why does this need to be a module? Everything else in tegra_defconfig is built-in, and it'd be nice to be consistent here. Built-in makes net-booting new kernels from U-Boot much easier, since there aren't any modules to copy. When I built a kernel with this series, I observed the following: CONFIG_BRCMFMAC=m * Neither Cardhu nor Ventana auto-load the module. When the module is manually modprobe'd, I still see no wireless device being created. CONFIG_BRCMFMAC=y * Cardhu: No wireless device created. I do see some kernel spew such as "mmc1: queuing unknown CIS tuple 0x80" which I believe is the SDIO device being probed, but I don't see any Linux device being created. * Ventana: There's a 60s hang during boot, I believe related to the BRCM driver, since the hang doesn't occur without the series. In summary, this series doesn't work at all for me. Can you please explain what you tested and how? Are there any differences between the various Cardhu and Ventana board revisions and/or the 2 different wireless cards possible on Cardhu that'd explain this? Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
