Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dennis Millard <dennis@tealdrones.com>
To: linux-wireless@vger.kernel.org
Subject: Restricting BCM4354 to 802.11b only
Date: Fri, 6 Oct 2017 16:18:57 -0600	[thread overview]
Message-ID: <820714b7-e1de-33eb-2437-d2539608e50c@tealdrones.com> (raw)

I'm developing on an nVidia TX1 SOM which has an integrated BCM4354 
chipset which is a fullmac DSIO 11ac chip. The SOM is running Ubuntu 
16.04 Linux (64-bit ARM)

I have an application where I need long range with low bandwidth 
requirements.  It seems that 802.11b has the best receive sensitivity, 
and I need to reduce latency caused by modulation switching (i.e. 802.11 
b, g, n etc).  I'm looking for a way to configure the BCM43 chipset to 
lock in to 802.11b mode only, so I want to disable 802.11g and 802.11n 
modes.

I've seen references on google to the Broadcom WLAN client utility, or 
"wl", but it's not freely available anywhere.

I'm capable of making kernel driver modifications if necessary, but I 
don't have the required information to do this.  Cypress has bought the 
Broadcom line, and some support person from Cypress suggested the following:

"For your query, we have different IOV and IOCTL calls for doing so. 
There is a IOV_NMODE (set to 0 disable 802.11n mode) and ioctl WLC_GMODE 
(set to 0 to disable 802.11g mode) . You need to make these calls during 
the system initialization phase to use 802.11b only mode."

I don't see any references to the WLC_GMODE ioctl in the brcfmac driver 
source, so I haven't been able to make that ioctl call in my code.


Does anyone have any advice on how to do this?  Thanks.

    -Dennis

                 reply	other threads:[~2017-10-06 22:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=820714b7-e1de-33eb-2437-d2539608e50c@tealdrones.com \
    --to=dennis@tealdrones.com \
    --cc=linux-wireless@vger.kernel.org \
    /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