On 02/17/2014 07:00 PM, Samuel Ortiz wrote: > Hi Arend, > > On Mon, Feb 17, 2014 at 06:37:33PM +0100, Arend van Spriel wrote: >> Hi Bernd, >> >> The hint to solve this is found on wireless.kernel.org [1] and the >> answer is as Samuel suspects. This file is very board specific so >> OEMs manufacturing/selling the board should provide it either upon >> request or through some distribution like a SDK. > There are several Win8 2-in-1 devices that do run the SDIO Full MAC > chipsets and obviously there is no SDK for those. Which means no distro > will ever be able to run out of the box on those. > I may be completely off the mark here, but isn't there a sensible > template for those guys ? Nothing optimised, but just something that > would at least make things work... Last time I got the question I extracted the nvram from the windows driver installer archive. However, it may end up in (U)EFI variable space. Guess that could be accessed from Linux as well. Anyway, it may be an area where we can and maybe should improve. I will discuss this with Franky and the rest of the team over here. > Also, the hint for pre 3.13 kernel is to copy the .bin into a .txt. Is > that still the case for post 3.13 ? I certainly hope you misread that. Before 3.13 the driver always look for brcmfmac-sdio.bin and brcmfmac-sdio.txt regardless the device being used. That has changed so the firmware file now includes the chip id and for some even the revision, eg. brcmfmac43241b4-sdio.bin and brcmfmac43241b4-sdio.txt. The nvram file has a totally different format as the bin file so copying will fail for sure. Regards, Arend -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
