On 2018-04-12 01:00, Sven Eckelmann wrote:
On Mittwoch, 11. April 2018 21:04:46 CEST Pradeep Kumar Chitrapu wrote:
Issues wmi command to firmware when multicast rate change is received
with the new BSS_CHANGED_MCAST_RATE flag.
[...]
+ if (changed & BSS_CHANGED_MCAST_RATE &&
+
On 2018-04-16 20:30, Kalle Valo wrote:
Rob Herring writes:
On Tue, Apr 10, 2018 at 10:19:46PM +0530, Govind Singh wrote:
Add device tree binding documentation details for wcn3990
wifi block present in Qualcomm SDM845/APQ8098 SoC into
"qcom,ath10k.txt".
Signed-off-by:
Hi,
On Mon, Apr 16, 2018 at 02:32:47PM +0300, Kalle Valo wrote:
> cjhu...@codeaurora.org writes:
> > On 2018-04-14 05:13, Arend van Spriel wrote:
> >> On 4/13/2018 1:28 PM, Kalle Valo wrote:
> >>> cjhu...@codeaurora.org writes:
> >>>
> >> + if (test_bit(WMI_SERVICE_SPOOF_MAC_SUPPORT,
Despite this issue is not harmful since it is not actually used in
mt76 driver, fix DMA txinfo bitmask definition
Fixes: 7bc04215a66b ('mt76: add driver code for MT76x2e')
Signed-off-by: Lorenzo Bianconi
---
drivers/net/wireless/mediatek/mt76/mt76x2_dma.h | 7
On Tue, Apr 10, 2018 at 12:14 PM, Stanislaw Gruszka wrote:
> Hi
>
> On Mon, Apr 09, 2018 at 08:45:20PM +0200, Hans Ulli Kroll wrote:
>> here are my changes for working 5Ghz band and more USB ID's form my side
>
> I applied the changes and pushed to github repo.
>
> Thanks
>
On 16 April 2018 at 16:16, Daniel Mack wrote:
> Here's another series of 5 patches for wcn36xx that address some issues
> with scanning. The first one is the most important one.
>
Nicely done. Thanks !
>
> Daniel
>
> Daniel Mack (5):
> wcn36xx: abort scan request when
Hello
Greeetings to you please did you get my previous email regarding my
investment proposal last week friday ?
MS.Zeliha ömer faruk
zeliha.omer.fa...@gmail.com
On 4/14/2018 12:56 PM, Stanislaw Gruszka wrote:
On Fri, Apr 13, 2018 at 11:06:13AM -0700, Jakub Kicinski wrote:
>On Fri, 13 Apr 2018 16:44:38 +0200, Stanislaw Gruszka wrote:
> >When finishing scanning we switch to operational channel sill with
> >SCANNING flag. This mean that we never perform
On Mon, 16 Apr 2018 13:56:18 +0200, Stanislaw Gruszka wrote:
> When finishing scanning we switch to operational channel sill with
> SCANNING flag. This mean that we never perform calibration works after
> scanning. To fix the problem queue calibration works on
> .sw_scan_complete() routine.
>
>
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
Rob Herring writes:
> On Tue, Apr 10, 2018 at 10:19:46PM +0530, Govind Singh wrote:
>> Add device tree binding documentation details for wcn3990
>> wifi block present in Qualcomm SDM845/APQ8098 SoC into
>> "qcom,ath10k.txt".
>>
>> Signed-off-by: Govind Singh
Average ack rssi will be given to userspace via NL80211 interface
if firmware is capable. Userspace tool ‘iw’ can process this
information and give the output as one of the fields in
‘iw dev wlanX station dump’.
Example output :
localhost ~ #iw dev wlan-5000mhz station dump Station
Average ack rssi value is weighted average of ack rssi for
no of msdu's has been sent.
This feature is enabled by the host driver if firmware is capable.
After receiving event from host, firmware allocates the necessary
memory to store the ack_rssi for data packets during the init time.
After
The driver will process the RSSI if available and send it to mac80211.
mac80211 will compute the weighted average of ack RSSI for stations.
Signed-off-by: Balaji Pothunoori
---
net/mac80211/sta_info.c | 10 ++
net/mac80211/sta_info.h | 2 ++
This patchset introduces the average ack rssi for data frames.
Balaji Pothunoori (3):
ath10k: average ack rssi support for data frames.
mac80211: average ack rssi support for data frames
cfg80211: average ack rssi support for data frames
v2:
Addressed ath10k-check warnings
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
On Mon, Apr 16, 2018 at 1:54 PM, Kalle Valo wrote:
> Josh Boyer writes:
>
>> On Tue, Mar 27, 2018 at 12:41 PM, ojab // wrote:
>>> [please CC me since I'm not subscribed to the lists and terribly sorry
>>> for HTML mails]
>>>
>>> Oh hai!
On Mon, Apr 9, 2018 at 6:21 AM, Maya Erez wrote:
> This is the latest firmware from wil6210 5.2 firmware branch.
>
> Signed-off-by: Maya Erez
> ---
> WHENCE | 2 +-
> wil6210.brd | Bin 3588 -> 3588 bytes
> wil6210.fw | Bin 350748 -> 400364
Wen Gong wrote:
> When trying to set wow wakeup patterns it fails with this command:
>
> iw phyxx wowlan enable patterns offset xx+ IP address xx.xx.xx.xx
>
> The reason is that the wow pattern from upper layer is in 802.3 format
> for this case, it need to convert it to
On Mon, Apr 9, 2018 at 4:36 AM, Siva Rebbagondla wrote:
> From: Amitkumar Karwar
>
> These images will be loaded by rsi driver based on operating mode.
> Firmware version is 1.6.1
>
> rs9113_ap_bt_dual_mode.rps - AP and BT functionality
>
Josh Boyer writes:
> On Tue, Mar 27, 2018 at 12:41 PM, ojab // wrote:
>> [please CC me since I'm not subscribed to the lists and terribly sorry
>> for HTML mails]
>>
>> Oh hai!
>>
>> I have Compex WLE1216V2-20 (based on QCA9984 chip) that isn't
>> supported by
On Tue, Mar 27, 2018 at 12:41 PM, ojab // wrote:
> [please CC me since I'm not subscribed to the lists and terribly sorry
> for HTML mails]
>
> Oh hai!
>
> I have Compex WLE1216V2-20 (based on QCA9984 chip) that isn't
> supported by linux-firmware (git master), card init fails with
On Fri, Apr 6, 2018 at 2:34 AM, Luca Coelho wrote:
> Hi,
>
> I have updated all the firmwares we currently support.
>
> Please pull or let me know if there are any issues.
>
> Cheers,
> Luca.
>
>
> The following changes since commit 8c1e439c967a50f0698d61aafdba3841aff10db0:
>
>
Carl Huang wrote:
> The ath10k reports the random_mac_addr capability to upper layer
> based on the service bit firmware reported. Driver sets the
> spoofed flag in scan_ctrl_flag to firmware if upper layer has
> enabled this feature in scan request.
>
> Test with
Carl Huang wrote:
> Add WMI_SERVICE_AVAILABLE_EVENT to extend WMI_SERVICE_READY_EVENT,
> the 128bit service map in WMI_SERVICE_READY_EVENT is not enough
> for firmware to notice new WLAN service to host driver. Hereby,
> for thoese new WLAN service, firmware will notice
pill...@codeaurora.org writes:
> From: Govind Singh
>
> SRRI/DRRI are not mapped in the HW Shadow block and can lead
> to un-clocked access if common subsystem in the target is
> powered down due to idle mode.
>
> To mitigate this problem SRRI/DRRI can be read from
> DDR
Rakesh Pillai wrote:
> By default ath10k driver enables the support for HW_CHECKSUM
> (NETIF_F_HW_CSUM). Since the TCP/UDP checksum calculation is not enabled
> in the wcn3990 firmware the checksum is incorrect in the TCP/UDP packets
> and all patckets are dropped. But
When the network interface goes down while a scan request is still
pending that can't be stopped due to firmware hickups, wcn->scan_req
remains set, even though the hardware is deinitialized. This results
in -EBUSY for all scan requests after the interface was brought up
again.
Fix this by
For firmwares that don't have the SCAN_OFFLOAD feature bit set, do
not call into wcn36xx_smd_stop_hw_scan(). Instead, stop the asynchronous
work and call into ieee80211_scan_completed() immediately.
Signed-off-by: Daniel Mack
---
drivers/net/wireless/ath/wcn36xx/main.c | 14
Pass the bss_type of the currently configured BSS in the message for the
scan request. Therefore, that setting needs to be kept in struct
wcn36xx_vif.
This seems to be only interesting when scanning for a specific SSID
and doesn't matter for regular wildcard scans.
Signed-off-by: Daniel Mack
When the firmware sends a WCN36XX_HAL_SCAN_IND_DEQUEUED indication,
the request is apparently no longer valid. Attempts to stop the hardware
scan request subsequently will lead to the following error message, and
the hardware is no longer able to communicate with any AP:
[ 57.917186] wcn36xx:
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
Here's another series of 5 patches for wcn36xx that address some issues
with scanning. The first one is the most important one.
Daniel
Daniel Mack (5):
wcn36xx: abort scan request when 'dequeued' indicator is sent
wcn36xx: cancel pending scan request when interface goes down
wcn36xx:
On Dienstag, 20. Juni 2017 09:13:40 CEST miaoq...@codeaurora.org wrote:
> From: Miaoqing Pan
>
> The hard coded register 0x9864 and 0x9924 are invalid
> for ar9300 chips.
[...]
> - REG_SET_BIT(ah, 0x9864, 0x7f000);
> - REG_SET_BIT(ah, 0x9924, 0x7f00fe);
Sorry
When finishing scanning we switch to operational channel sill with
SCANNING flag. This mean that we never perform calibration works after
scanning. To fix the problem queue calibration works on
.sw_scan_complete() routine.
Signed-off-by: Stanislaw Gruszka
---
avr_rssi is not calculated correctly as we do not divide result
by 256 (mt76 sum avg_rssi1 and avg_rssi2 and divide by 512).
However dividing by 256 will make avg_rssi almost the same as
last rssi value - not really an average. So use EWMA to calculate
avg_rssi. I've chosen weight_rcp=4 to
cjhu...@codeaurora.org writes:
> On 2018-04-14 05:13, Arend van Spriel wrote:
>> On 4/13/2018 1:28 PM, Kalle Valo wrote:
>>> cjhu...@codeaurora.org writes:
>>>
>> +if (test_bit(WMI_SERVICE_SPOOF_MAC_SUPPORT, ar->wmi.svc_map)) {
>> +ret =
Hi,
for an university project i needed to use the debugging mechanisms provided by
the ath9k driver.
However it seems that some options of the debug mask described on
https://wireless.wiki.kernel.org/en/users/drivers/ath9k/debug are currently not
implemented, e.g. tracing the ATH_DBG_WMI
On 2018-04-14 01:54, Peter Oh wrote:
On 04/13/2018 06:48 AM, Kalle Valo wrote:
Sven Eckelmann writes:
But of course, I cannot say much about how the rate control from QCA
works and
in which form these information are already available.
If you want to know the
43 matches
Mail list logo