From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752405AbbD0DpT (ORCPT ); Sun, 26 Apr 2015 23:45:19 -0400 Received: from mail-bn1bon0141.outbound.protection.outlook.com ([157.56.111.141]:42640 "EHLO na01-bn1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752338AbbD0DpQ (ORCPT ); Sun, 26 Apr 2015 23:45:16 -0400 Authentication-Results: spf=fail (sender IP is 192.88.158.2) smtp.mailfrom=freescale.com; google.com; dkim=none (message not signed) header.d=none; Date: Mon, 27 Apr 2015 11:33:52 +0800 From: Dong Aisheng To: Arend van Spriel CC: John Tobias , John Stultz , "" , "" , Fabio Estevam , Aisheng Dong , Shawn Guo , Ritter Yeh , Ecco Park , "Dmitry Shmidt" Subject: Re: Broadcom 43340 module on iMX6DL Message-ID: <20150427033351.GC26374@shlinux1.ap.freescale.net> References: <55394141.1080601@broadcom.com> <5539FCD5.4050708@broadcom.com> <553A8803.5010700@broadcom.com> <553A9368.9030700@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <553A9368.9030700@broadcom.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:192.88.158.2;CTRY:US;IPV:NLI;EFV:NLI;BMV:1;SFV:NSPM;SFS:(10019020)(6009001)(339900001)(51704005)(377454003)(189002)(479174004)(199003)(33656002)(47776003)(76176999)(62966003)(19580395003)(105606002)(50466002)(85426001)(104016003)(46102003)(50986999)(87936001)(19580405001)(54356999)(97756001)(110136001)(83506001)(6806004)(77156002)(15975445007)(92566002)(23726002)(93886004)(2950100001)(4001350100001)(106466001)(77096005)(46406003)(5001920100001)(32563001)(42262002);DIR:OUT;SFP:1102;SCL:1;SRVR:BN3PR03MB1415;H:az84smr01.freescale.net;FPR:;SPF:Fail;MLV:sfv;MX:1;A:1;LANG:en; X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN3PR03MB1415; X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(601004)(5002010)(5005006)(3002001);SRVR:BN3PR03MB1415;BCL:0;PCL:0;RULEID:;SRVR:BN3PR03MB1415; X-Forefront-PRVS: 0559FB9674 X-OriginatorOrg: freescale.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Apr 2015 03:45:12.5771 (UTC) X-MS-Exchange-CrossTenant-Id: 710a03f5-10f6-4d38-9ff4-a80b81da590d X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=710a03f5-10f6-4d38-9ff4-a80b81da590d;Ip=[192.88.158.2];Helo=[az84smr01.freescale.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR03MB1415 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 24, 2015 at 09:03:04PM +0200, Arend van Spriel wrote: > On 04/24/15 20:24, John Tobias wrote: > >Hi Arend, > > > >Apologize for the confusion. I am asking the repo for the device > >driver for 43340. Looking at the link you sent, it's more userspace > >support and didn't see the device driver there... > > crap. you are right. it is userspace and firmware. You need a kernel > repo. There are some on the site I referred to, but you may need to > contact Freescale whether they provide it publicly like on github or > so. > One simple question: Does the brcmfmac driver in upstream kernel also work? I mean this one: drivers/net/wireless/brcm80211 Regards Dong Aisheng > Regards, > Arend > > >Regards, > > > >John > > > > > >On Fri, Apr 24, 2015 at 11:14 AM, Arend van Spriel wrote: > >>On 04/24/15 19:49, John Tobias wrote: > >>> > >>>Hi Arend, > >>> > >>>I am not pretty sure if the brcm43340 driver for android is the latest > >>>one. May I know repo?. > >> > >> > >>Not sure what you are asking. I gave the url. Did you try using the > >>brcmfmac4334-sdio.bin firmware file. I would like to know if that one works > >>for your device. > >> > >>Regards, > >>Arend > >> > >> > >>>Regards, > >>> > >>>John > >>> > >>>On Fri, Apr 24, 2015 at 1:20 AM, Arend van Spriel > >>>wrote: > >>>> > >>>>On 04/24/15 03:04, John Tobias wrote: > >>>>> > >>>>> > >>>>>Btw, where I could get a copy of the latest driver?. > >>>> > >>>> > >>>> > >>>>The open-source bcmdhd is in AOSP [1]. I would stick to the android > >>>>release > >>>>branch you are running on your device. > >>>> > >>>>Regards, > >>>>Arend > >>>> > >>>>[1] https://android.googlesource.com/platform/hardware/broadcom/wlan/ > >>>> > >>>> > >>>>>Regards, > >>>>> > >>>>>John > >>>>> > >>>>>On Thu, Apr 23, 2015 at 5:59 PM, John Tobias > >>>>>wrote: > >>>>>> > >>>>>> > >>>>>>Hi John, > >>>>>> > >>>>>>Is it possible to have a copy of the firmware for 43340?. > >>>>>> > >>>>>>Regards, > >>>>>> > >>>>>>John > >>>>>> > >>>>>>On Thu, Apr 23, 2015 at 5:57 PM, John Stultz > >>>>>>wrote: > >>>>>>> > >>>>>>> > >>>>>>>On Thu, Apr 23, 2015 at 12:00 PM, Arend van Spriel > >>>>>>>wrote: > >>>>>>>> > >>>>>>>> > >>>>>>>>By the name of the file I suspected you did. Personally, I verified > >>>>>>>>the > >>>>>>>>firmware works on 43341. John Stultz tested both 43340 and 43341 with > >>>>>>>>this > >>>>>>>>firmware. > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>Minor correction here, I only tested on 43341 hardware. The confusion > >>>>>>>might be that the firmware I originally had access to claimed it was > >>>>>>>43340. > >>>>>>> > >>>>>>>thanks > >>>>>>>-john > >>>> > >>>> > >>>> > >> > From mboxrd@z Thu Jan 1 00:00:00 1970 From: b29396@freescale.com (Dong Aisheng) Date: Mon, 27 Apr 2015 11:33:52 +0800 Subject: Broadcom 43340 module on iMX6DL In-Reply-To: <553A9368.9030700@broadcom.com> References: <55394141.1080601@broadcom.com> <5539FCD5.4050708@broadcom.com> <553A8803.5010700@broadcom.com> <553A9368.9030700@broadcom.com> Message-ID: <20150427033351.GC26374@shlinux1.ap.freescale.net> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Apr 24, 2015 at 09:03:04PM +0200, Arend van Spriel wrote: > On 04/24/15 20:24, John Tobias wrote: > >Hi Arend, > > > >Apologize for the confusion. I am asking the repo for the device > >driver for 43340. Looking at the link you sent, it's more userspace > >support and didn't see the device driver there... > > crap. you are right. it is userspace and firmware. You need a kernel > repo. There are some on the site I referred to, but you may need to > contact Freescale whether they provide it publicly like on github or > so. > One simple question: Does the brcmfmac driver in upstream kernel also work? I mean this one: drivers/net/wireless/brcm80211 Regards Dong Aisheng > Regards, > Arend > > >Regards, > > > >John > > > > > >On Fri, Apr 24, 2015 at 11:14 AM, Arend van Spriel wrote: > >>On 04/24/15 19:49, John Tobias wrote: > >>> > >>>Hi Arend, > >>> > >>>I am not pretty sure if the brcm43340 driver for android is the latest > >>>one. May I know repo?. > >> > >> > >>Not sure what you are asking. I gave the url. Did you try using the > >>brcmfmac4334-sdio.bin firmware file. I would like to know if that one works > >>for your device. > >> > >>Regards, > >>Arend > >> > >> > >>>Regards, > >>> > >>>John > >>> > >>>On Fri, Apr 24, 2015 at 1:20 AM, Arend van Spriel > >>>wrote: > >>>> > >>>>On 04/24/15 03:04, John Tobias wrote: > >>>>> > >>>>> > >>>>>Btw, where I could get a copy of the latest driver?. > >>>> > >>>> > >>>> > >>>>The open-source bcmdhd is in AOSP [1]. I would stick to the android > >>>>release > >>>>branch you are running on your device. > >>>> > >>>>Regards, > >>>>Arend > >>>> > >>>>[1] https://android.googlesource.com/platform/hardware/broadcom/wlan/ > >>>> > >>>> > >>>>>Regards, > >>>>> > >>>>>John > >>>>> > >>>>>On Thu, Apr 23, 2015 at 5:59 PM, John Tobias > >>>>>wrote: > >>>>>> > >>>>>> > >>>>>>Hi John, > >>>>>> > >>>>>>Is it possible to have a copy of the firmware for 43340?. > >>>>>> > >>>>>>Regards, > >>>>>> > >>>>>>John > >>>>>> > >>>>>>On Thu, Apr 23, 2015 at 5:57 PM, John Stultz > >>>>>>wrote: > >>>>>>> > >>>>>>> > >>>>>>>On Thu, Apr 23, 2015 at 12:00 PM, Arend van Spriel > >>>>>>>wrote: > >>>>>>>> > >>>>>>>> > >>>>>>>>By the name of the file I suspected you did. Personally, I verified > >>>>>>>>the > >>>>>>>>firmware works on 43341. John Stultz tested both 43340 and 43341 with > >>>>>>>>this > >>>>>>>>firmware. > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>Minor correction here, I only tested on 43341 hardware. The confusion > >>>>>>>might be that the firmware I originally had access to claimed it was > >>>>>>>43340. > >>>>>>> > >>>>>>>thanks > >>>>>>>-john > >>>> > >>>> > >>>> > >> >