On Monday, April 16, 2018 04:41 PM, Kalle Valo wrote:
> Daniel Mack writes:
>
>> On Monday, April 16, 2018 04:13 PM, Kalle Valo wrote:
>>> Daniel Mack writes:
On Monday, April 16, 2018 04:03 PM, Kalle Valo wrote:
> Daniel Mack
Daniel Mack writes:
> On Monday, April 16, 2018 04:13 PM, Kalle Valo wrote:
>> Daniel Mack writes:
>>> On Monday, April 16, 2018 04:03 PM, Kalle Valo wrote:
Daniel Mack writes:
>
> them to the firmware message. The driver
On Monday, April 16, 2018 04:13 PM, Kalle Valo wrote:
> Daniel Mack writes:
>> On Monday, April 16, 2018 04:03 PM, Kalle Valo wrote:
>>> Daniel Mack writes:
them to the firmware message. The driver currently tells the core that
it is capable of
Daniel Mack writes:
> On Monday, April 16, 2018 04:03 PM, Kalle Valo wrote:
>> Daniel Mack writes:
>>
>>> When the ieee8022 core passes IE elements in the scan request, append
>>
>> You mean mac80211?
>>
>> And yeah, the ieee80211_ prefix is confusing.
On Monday, April 16, 2018 04:03 PM, Kalle Valo wrote:
> Daniel Mack writes:
>
>> When the ieee8022 core passes IE elements in the scan request, append
>
> You mean mac80211?
>
> And yeah, the ieee80211_ prefix is confusing. Many many years I
> started to change that to
Daniel Mack writes:
> When the ieee8022 core passes IE elements in the scan request, append
You mean mac80211?
And yeah, the ieee80211_ prefix is confusing. Many many years I
started to change that to mac80211_ but gave up :(
> them to the firmware message. The driver
When the ieee8022 core passes IE elements in the scan request, append
them to the firmware message. The driver currently tells the core that
it is capable of attaching up to WCN36XX_MAX_SCAN_IE_LEN octets, but
doesn't actually pass them to the the hardware.
Some defines were moved around to avoid