From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "open list:BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVER"
<brcm80211-dev-list.pdl@broadcom.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: brcmfmac4356-pci device not seeing 2.4Ghz channel 12 and 13
Date: Thu, 6 Jul 2017 21:43:56 +0200 [thread overview]
Message-ID: <1b37a554-a69d-53ed-1c66-ab1edceb9af4@broadcom.com> (raw)
In-Reply-To: <775f1300-ce1f-0e0b-747b-bf9b34d32362@redhat.com>
On 06-07-17 21:23, Hans de Goede wrote:
> Hi,
>
> On 28-06-17 14:35, Arend Van Spriel wrote:
>> Op 28 jun. 2017 12:07 schreef "Hans de Goede" <hdegoede@redhat.com
>> <mailto:hdegoede@redhat.com>>:
>> >
>> > Hi,
>> >
>> > I noticed today that my GPD Win (x86 clamshell mini laptop)
>> > which uses a brcmfmac4356-pci wifi does not see an APs which
>> > is using channel 13.
>> >
>> > I've tried updating brcmfmac4356-pci.txt changing "ccode=US"
>> > to "ccode=EU" and then rebooted, but that does not help.
>>
>> Some variables may be stored on the device. However, EU may not be
>> valid. Could you try NL instead?
>
> Yes changing it to NL fixes this. This is still a bit problematic
> though. Because what are we going to put in the nvram file we want
> to put in linux-firmware ?
Agree. I am surprised (not pleasantly) that these devices are not
properly programmed and thus need nvram for the country code.
>> > I believe that the Linux wifi stack is supposed to automatically
>> > figure out the country settings based on AP provided info ?
>>
>> That depends. The device runs its own wifi stack which should have
>> 802.11d support for what you describe.
>>
>> > But that does not seem to be working here ? Any hints on howto
>> > debug this further would be appreciated.
>>
>> You could try doing "country" iovar get somewhere in
>> brcmf_bus_started() to check country setting in firmware.
>
> Let me know if you still want me to do this given that ccode=NL fixes this.
Well. Could you try it with ccode commented out in nvram file.
Regards,
Arend
next prev parent reply other threads:[~2017-07-06 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 10:07 brcmfmac4356-pci device not seeing 2.4Ghz channel 12 and 13 Hans de Goede
[not found] ` <CAF7Mx6pPmsZektpdEVphqUzBtbGGiMh7cedexTDsGOC8myF=9w@mail.gmail.com>
[not found] ` <CAF7Mx6rUwR9TLDZuQ0pDkj0xG_j+d31w7LKBuv9q9A2V0gN7mw@mail.gmail.com>
[not found] ` <CAF7Mx6oVrjxYApXbO2dV8JGY7QrYy+uF6-QH=M67RW_wBM7GGA@mail.gmail.com>
2017-07-06 19:23 ` Hans de Goede
2017-07-06 19:43 ` Arend van Spriel [this message]
2017-08-30 13:39 ` Hans de Goede
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=1b37a554-a69d-53ed-1c66-ab1edceb9af4@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=hdegoede@redhat.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;
as well as URLs for NNTP newsgroup(s).