From: Adrian Chadd <adrian@freebsd.org>
To: b43-dev@lists.infradead.org
Subject: Restricting BCM4354 to 802.11b only
Date: Fri, 6 Oct 2017 14:53:18 -0700 [thread overview]
Message-ID: <CAJ-Vmom2vjs9s1=xPnhR7gGTzTZ=JcNdQks5TBQZjmM1CPseRQ@mail.gmail.com> (raw)
In-Reply-To: <04e66bc2-8c34-f513-cd75-b8ea6f9f02c5@tealdrones.com>
On 6 October 2017 at 14:47, Dennis Millard <dennis@tealdrones.com> wrote:
> I'm developing on an nVidia TX1 SOM which has an integrated BCM4354 chipset.
> 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'm capable of making kernel driver modifications if necessary, but I don't
> have the required information to do this. I've seen references on google to
> the Broadcom WLAN client utility, or "wl", but it's not freely available
> anywhere.
>
> Does anyone have any advice on where to turn for information on how to do
> this? Thanks.
Hi,
Have you noticed any actual modulation switching latency? Ideally it's
just enabling a different PHY path and so the latency should be
effectively nil.
Also, BCM4354 is a fullmac SDIO 11ac chip, not a b43 chip. :-)
And the TL;DR is - yes, there'll be an ioctl command to send to the
chip to tell it which PHY mode to operate in, and I bet you can set it
to operate on 'b' only. I just don't know off-hand on the brcmfmac
driver what that is, and you should likely ask on linux-wireless where
the brcmfmac people watch out.
-adrian
prev parent reply other threads:[~2017-10-06 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 21:47 Restricting BCM4354 to 802.11b only Dennis Millard
2017-10-06 21:53 ` Adrian Chadd [this message]
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='CAJ-Vmom2vjs9s1=xPnhR7gGTzTZ=JcNdQks5TBQZjmM1CPseRQ@mail.gmail.com' \
--to=adrian@freebsd.org \
--cc=b43-dev@lists.infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).