On 8 August 2018 at 21:14, Arend van Spriel
wrote:
> On 8/8/2018 7:58 PM, Randy Oostdyk wrote:
>>
>> Good day all,
>
>
> Hi Randy
>
>> I'm writing to report an issue with the linux kernel, and I'm hoping
>> this is the right place to report it. (short aside: I tried to ask in
>> the
On 8/8/2018 7:58 PM, Randy Oostdyk wrote:
Good day all,
Hi Randy
I'm writing to report an issue with the linux kernel, and I'm hoping
this is the right place to report it. (short aside: I tried to ask in
the #linux-wireless IRC channel, but wasn't permitted to speak!)
uhm. why?
I'm aware
On 08/08/2018 12:58 PM, Randy Oostdyk wrote:
Good day all,
I'm writing to report an issue with the linux kernel, and I'm hoping
this is the right place to report it. (short aside: I tried to ask in
the #linux-wireless IRC channel, but wasn't permitted to speak!)
I'm aware that this is a USB
Good day all,
I'm writing to report an issue with the linux kernel, and I'm hoping
this is the right place to report it. (short aside: I tried to ask in
the #linux-wireless IRC channel, but wasn't permitted to speak!)
I'm aware that this is a USB protocol issue, and so this may be the
wrong
> If driver does not know what kind of frame has been received from BSS,
> then it is possible to specify CFG80211_BSS_FTYPE_UNKNOWN
> in cfg80211_inform_bss[_width].
>
> In this case neither NL80211_BSS_BEACON_IES nor NL80211_BSS_PRESP_DATA
> will be reported to userspace.
The fix is for iw
