Hello, On 19 December 2013 11:12, Chen-Yu Tsai <wens@xxxxxxxx> wrote: > Hi, > > On Thu, Dec 19, 2013 at 12:39 AM, Chen-Yu Tsai <wens@xxxxxxxx> wrote: >> Hi, >> >> On Thu, Dec 19, 2013 at 12:16 AM, Arend van Spriel <arend@xxxxxxxxxxxx> wrote: >>> On 12/18/2013 02:12 PM, Hans de Goede wrote: >>>> Hi, >>>> >>>> On 12/18/2013 11:31 AM, Arend van Spriel wrote: >>>>> On 12/05/2013 10:46 PM, Julian Calaby wrote: >>>>>> Firstly, are there any plans to support the BCM43362 chipset with the >>>>>> brcmfmac driver in the near future? >>>>> >>>>> Hi Julian, >>>>> >>>>> I am working on a patch to support this chip. It is looking promising. >>>>> Just have to go after a firmware image to be sure. >>>> >>>> Cool. Do you have a cubietruck? With my latest wip tree: >>>> https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-next >>> >>> No cubietruck here. I googled the term last week because it came up and >>> found embeddedcomputer.nl selling it. >>> >>>> We've mmc/sdio controller support on top of 3.13-rc4, it would be >>>> nice if we could also get the wifi and bluetooth to work here. > > I got the chip to respond to probing. It is BCM43362 for sure. > > root@cubietruck:/sys/bus/mmc/devices/mmc1:0001/mmc1:0001:1# cat device > 0xa962 > root@cubietruck:/sys/bus/mmc/devices/mmc1:0001/mmc1:0001:1# cat vendor > 0x02d0 > > Vendor ID is Broadcom. Device ID is 43362. > But I get two devices, mmc1:0001:1 and mmc1:0001:2. I don't know > if this is normal or not. > > Bluetooth still isn't responding. > Well, bluetooth is supposed to be attached to an UART, not SDIO. That's what the datasheets of the chip I found looked like. Not sure how firmware is supposed to fit in in this case but this would not be the first serial BT chip requiring firmware, would it? Thanks Michal -- 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
