Linux wireless drivers development
 help / color / mirror / Atom feed
From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
	"Michael Eskowitz" <MichaelE@inventeksys.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: building brcmfmac driver for iMX6 Ultralite platform
Date: Tue, 12 Jul 2016 23:32:46 +0200	[thread overview]
Message-ID: <72354044-4f67-bfbd-ed0f-12183dc8fc53@broadcom.com> (raw)
In-Reply-To: <CACna6rzU91CRGmgPtAgEhdqwpSGSs0i-C3qL7OiB8soHk8vq8Q@mail.gmail.com>



On 12-7-2016 23:10, Rafał Miłecki wrote:
> On 12 July 2016 at 21:17, Michael Eskowitz <MichaelE@inventeksys.com> wrote:
>> Arend,
> 
> What about my reply? ;)
> 
> 
>> That is news to me.  I was under the impression that bcmdhd was Broadcom's
>> proprietary (closed source) Linux driver and brcmfmac was the open source
>> Linux driver.
> 
> Don't top post. It's hard to say what you're replying to. bcmdhd is
> also open source (not sure what license), just not mainline.
> 
> 
>> Either way, I am now running
>>
>>         insmod  brcmutil.ko
>>         insmod  brcmfmac.ko
>>
>> I receive no errors and no kernel messages.
>>
>> When I insert the 43341 module into the SDIO slot nothing happens.  I'm
>> guessing that the version of the brcmfmac driver that I built does not
>> support that chip.
> 
> Is is detected by the system? If so, what ID does it use?
> 
> 
>> When I insert the 43362 module into the SDIO slot I receive the following
>> errors
>>
>>         mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
>>         mmc0: new high speed SDIO card at address 0001
>>         brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Jun  7 2012
>> 18:27:16 version 5.90.225 FWID 01-d8fe14bd
>>         brcmfmac: brcmf_fil_cmd_data: Failed err=-23
>>         brcmfmac: brcmf_fil_cmd_data: Failed err=-23
>>         brcmfmac: brcmf_fil_cmd_data: Failed err=-23
>>         brcmfmac: brcmf_fil_cmd_data: Failed err=-23
>>         brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
>>         brcmfmac: brcmf_add_if: ignore IF event
>>         brcmfmac: brcmf_fil_cmd_data: Failed err=-23
>>         brcmfmac: brcmf_construct_reginfo: channel 1: f=2412 bw=0
>> sb=-1998840228
>>         brcmfmac: brcmf_construct_reginfo: channel 2: f=2417 bw=0
>> sb=-1998840228
>>
>> and suddenly ifconfig shows the interface wlan0.  The interface looks to be
>> valid as it is displaying a MAC from our address range.
>>
>> Although the interface wlan0 is present I am not able to use wl commands to
>> scan for networks.  wl reports "wl driver adapter not found" for all command
>> arguments.  If I run the command
>>
>>         iwlist  wlan0  scan
>>
>> I'm told that the interface does not support scanning.  If I run wpa_cli and
>> then the commands scan and scanresults I don't see any networks.
> 
> "wl" user space tool uses wlioctl, proprietary protocol, brcmfmac
> doesn't support it.

Well, not quite these days. The wl tool can be built to use nl80211
vendor commands to transport wl commands to firmware. However, my bet is
you have the "classic" wl tool using ioctl() api, which we removed from
brcmfmac years ago.

> iwlist uses wext protocol, legacy one.

iwlist is indeed using wext protocol, but cfg80211 should provide
compatibility layer so cfg80211-based drivers like brcmfmac can work
with it. However, there seem to be issues and not everything runs
smoothly. Apparently no one cares enough about wext.

> Please use nl80211 based tools, e.g. "iw".

So indeed use "iw":

$ sudo ifconfig wlan0 up
$ sudo iw wlan0 scan

Regards,
Arend

  reply	other threads:[~2016-07-12 21:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 19:24 building brcmfmac driver for iMX6 Ultralite platform Michael Eskowitz
2016-07-01  7:49 ` Arend Van Spriel
2016-07-12 19:17   ` Michael Eskowitz
2016-07-12 21:10     ` Rafał Miłecki
2016-07-12 21:32       ` Arend Van Spriel [this message]
2016-07-13 14:51       ` Michael Eskowitz
2016-07-01  9:07 ` Rafał Miłecki
2016-07-01  9:14   ` Arend Van Spriel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=72354044-4f67-bfbd-ed0f-12183dc8fc53@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=MichaelE@inventeksys.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox