On 11/08/2018 7:53, Arend van Spriel wrote:
> On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
>> From: Madhan Mohan R
>>
>> Along with F2 watermark (existing) configuration, F1 MesBusyCtrl
>> should be enabled & configured to avoid overflow errors.
>
> Reviewed-by: Arend van Spriel
>>
From: Ajay Singh
We would like to update the maintainer email id's for wilc1000 driver.
Signed-off-by: Aditya Shankar
Signed-off-by: Ganesh Krishna
Signed-off-by: Adham Abozaeid
Signed-off-by: Ajay Singh
Acked-by: Ganesh Krishna
---
Changes in
Hi,
Gentle Remainder..!!!.
Any update required for this patch?. If not, When can i expect this
patch to be available in wireless-next?.
Thank you,
Siva Rebbagondla
On Thu, Oct 18, 2018 at 5:21 PM Siva Rebbagondla wrote:
>
> On Thu, Oct 18, 2018 at 2:06 PM Johannes Berg
> wrote:
> >
> > From:
On Thu, Nov 08, 2018 at 09:50:25PM +, adham.aboza...@microchip.com wrote:
> From: Adham Abozaeid
>
> From: Adham Abozaeid
Twice? Something went wrong on your side, for all of these patches :(
Please fix up and resend.
thanks,
greg k-h
From: Adham Abozaeid
From: Adham Abozaeid
Validate cfg parameters after being called by cfg80211 in set_wiphy_params
before scheduling the work executed in handle_cfg_param
Signed-off-by: Adham Abozaeid
---
drivers/staging/wilc1000/host_interface.c | 61 ++-
From: Adham Abozaeid
From: Adham Abozaeid
host_if_drv.cfg_values is a write only member, and can be removed
Signed-off-by: Adham Abozaeid
---
drivers/staging/wilc1000/host_interface.c | 13 -
drivers/staging/wilc1000/host_interface.h | 1 -
2 files changed, 14 deletions(-)
From: Adham Abozaeid
From: Adham Abozaeid
After removing cfg_values member, cfg_values_lock that was used to protect
it can also be removed.
Signed-off-by: Adham Abozaeid
---
drivers/staging/wilc1000/host_interface.c | 9 -
drivers/staging/wilc1000/host_interface.h | 2 --
2 files
From: Adham Abozaeid
Validate input parameters to set_wiphy_param before scheduling
handle_cfg_param() to validate them.
This way proper errors can be returned to caller.
Also cleaned up unused code in handle_cfg_param.
Changes since v1:
- Correction spelling in subject of patch#2
- Added From:
Johannes Berg wrote on 08/11/2018:
> On Thu, 2018-11-08 at 21:26 +0100, Johannes Berg wrote:
>> Hi,
>>
>>> The attached patch adds support for CPPFLAGS to iw's Makefile.
>>
>> Please send the patch as plain text (not attachment), and with signed-
>> off-by per the CONTRIBUTING file.
>
> Actually,
On Thu, 2018-11-08 at 21:26 +0100, Johannes Berg wrote:
> Hi,
>
> > The attached patch adds support for CPPFLAGS to iw's Makefile.
>
> Please send the patch as plain text (not attachment), and with signed-
> off-by per the CONTRIBUTING file.
Actually, it looks like patchwork knows how to read
Dear linux-wireless,
The attached patch adds support for CPPFLAGS to iw's Makefile.
I am not subscribed to the list, please Cc: me in replies.
Paride
From f672e0f8690b7f38d29d83b29f2374787694c31e Mon Sep 17 00:00:00 2001
From: Paride Legovini
Date: Thu, 8 Nov 2018 21:19:20 +0100
Subject:
Hi,
> The attached patch adds support for CPPFLAGS to iw's Makefile.
Please send the patch as plain text (not attachment), and with signed-
off-by per the CONTRIBUTING file.
Thanks,
johannes
On Wed, Nov 7, 2018 at 7:48 PM Chi-Hsien Lin wrote:
>
> From: Wright Feng
>
> The firmware does not respond ARP request and causes ping failure with
> following steps:
>
> 1. Bring up interface
>ifconfig wlan0 up or start wpa_supplicant
> 2. Set the IP address
>ifconfig wlan0
On 11/8/18 4:22 AM, Greg KH wrote:
> On Tue, Nov 06, 2018 at 12:01:18AM +, adham.aboza...@microchip.com wrote:
>> From: Adham Abozaeid
>>
>> Validate cfg parameters after being called by cfg80211 in set_wiphy_params
>> before scheduling the work executed in handle_cfg_param
>>
>>
On 2018-11-08 16:54, Stanislaw Gruszka wrote:
> On Thu, Nov 08, 2018 at 04:01:54PM +0100, Lorenzo Bianconi wrote:
>> > Restore behaviour on mt76x0 before commit 1bb04bb4b838 ("mt76: move
>> > mt76x02_init_device in mt76x02-lib module"). This will allow to use
>> > wcid 1 for AP when we work in
On 2018-11-08 16:52, Stanislaw Gruszka wrote:
> On Thu, Nov 08, 2018 at 03:58:29PM +0100, Lorenzo Bianconi wrote:
>> > For STA mode configure legacy basic rates according to info
>> > mac80211 provides to us, as well as follback registers, which
>> > are setup in vendor driver under
On Thu, Nov 08, 2018 at 04:01:54PM +0100, Lorenzo Bianconi wrote:
> > Restore behaviour on mt76x0 before commit 1bb04bb4b838 ("mt76: move
> > mt76x02_init_device in mt76x02-lib module"). This will allow to use
> > wcid 1 for AP when we work in station mode. It's not clear if this
> > is needed,
On Thu, Nov 08, 2018 at 03:58:29PM +0100, Lorenzo Bianconi wrote:
> > For STA mode configure legacy basic rates according to info
> > mac80211 provides to us, as well as follback registers, which
> > are setup in vendor driver under CONFIG_STA_SUPPORT .
> > For LB_FBK_CFG1 register use values from
From: Rafał Miłecki
Driver can report IEEE80211_VHT_CAP_SUPP_CHAN_WIDTH_160MHZ so it's
important to provide valid & complete info about supported bands for
each channel. By default no support for 160 MHz should be assumed unless
firmware reports it for a given channel later.
This fixes info
> Restore behaviour on mt76x0 before commit 1bb04bb4b838 ("mt76: move
> mt76x02_init_device in mt76x02-lib module"). This will allow to use
> wcid 1 for AP when we work in station mode. It's not clear if this
> is needed, but this is how vendor driver assign wcid's in STA mode.
> This should be
> For STA mode configure legacy basic rates according to info
> mac80211 provides to us, as well as follback registers, which
> are setup in vendor driver under CONFIG_STA_SUPPORT .
> For LB_FBK_CFG1 register use values from vendor driver, which
> are different for mt76x0 and mt76x2 .
>
>
Restore behaviour on mt76x0 before commit 1bb04bb4b838 ("mt76: move
mt76x02_init_device in mt76x02-lib module"). This will allow to use
wcid 1 for AP when we work in station mode. It's not clear if this
is needed, but this is how vendor driver assign wcid's in STA mode.
This should be harmless
Use information about protection that mac80211 provide to us.
Used protection should be part of ht capabilites that either
remote AP provde to us in STA mode or is set in hostapd.conf
in ht_capab option.
Signed-off-by: Stanislaw Gruszka
---
drivers/net/wireless/mediatek/mt76/mt76x02_mac.c | 58
Use set_rts_threshold calback to enable/disable threshold only for
legacy traffic. RTS/CTS threshold for HT TXOP make make no sense
to me since used protection (RTS/CTS , CTS-to-self or none)
should be determined by HT capabilities and applied to any HT
frames.
Signed-off-by: Stanislaw Gruszka
For STA mode configure legacy basic rates according to info
mac80211 provides to us, as well as follback registers, which
are setup in vendor driver under CONFIG_STA_SUPPORT .
For LB_FBK_CFG1 register use values from vendor driver, which
are different for mt76x0 and mt76x2 .
Signed-off-by:
I can still observe random performance drops on my setup.
Those drops are very rare after applying those:
mt76x02: assure we update gain after scan
mt76x02: run calibration after scanning
mt76x0: do not overwrite other MT_BBP(AGC, 8) fields
but sill happened in Felix tree up to:
79864387b0a0
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
From: Double Lo
Transaction between AOS and SDIOD is not protected, and if cmd 52
received in AOS and in the middle of response state changed from AOS to
SDIOD, response is corrupted and it causes to SDIO Host controller to
hang.
See comment in
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
From: Madhan Mohan R
By disabling command decode, sdiod_aos module supports
the detection of sdio command line toggle only and
generates a wakeup request to PMU and to sdiod core.
It does not decode any sdio command and generates no
response to any
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
From: Wright Feng
Transaction between AOS and SDIOD is not protected, and if cmd 52
received in AOS and in the middle of response state changed from AOS to
SDIOD, response is corrupted and it causes to SDIO Host controller to
hang.
I think it would
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
Use sr_eng_en bit to check 4373 sr support.
Reviewed-by: Arend van Spriel
Signed-off-by: Chi-Hsien Lin
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
From: Naveen Gupta
The number of words that the read FIFO has to contain except
the end of frame before sends data back to the host.
Max watermark = (512B - 2* (BurstLength))/4 =
(512 - 128)/4 = 384/4 = 0x60
so if burst length (i.e. BurstLength = 64)
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
GCI core is needed for ULP operation. Allow GCI core enumuration with
below changes:
- Allow GCI to be added to core list even when it doesn't have a wrapper.
- Allow 8K address space size.
- Don't overwrite the address value when an additional size
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
From: Praveen Babu C
Add saverestore register settings for 43012.
I would collapse this commit with PATCH 04/11.
Reviewed-by: Arend van Spriel
Signed-off-by: Praveen Babu C
Signed-off-by: Chi-Hsien Lin
---
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
CYW43012 is a 1x1 802.11a/b/g/n Dual-Band HT20, 256-QAM/Turbo QAM. It
is an Ultra Low Power WLAN+BT combo chip.
comments below
Reviewed-by: Arend van Spriel
Signed-off-by: Chi-Hsien Lin
---
.../wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c |
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
From: Winnie Chang
Add the raw 4354 PCIe device ID.
What is the motivation for adding this. I can do an educated guess, but
I would like to see it in the commit message. Why only for 4354?
Regards,
Arend
Signed-off-by: Winnie Chang
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
From: Madhan Mohan R
Along with F2 watermark (existing) configuration, F1 MesBusyCtrl
should be enabled & configured to avoid overflow errors.
Reviewed-by: Arend van Spriel
Signed-off-by: Madhan Mohan R
Signed-off-by: Chi-Hsien Lin
---
On 11/6/2018 4:50 AM, Chi-Hsien Lin wrote:
From: Wright Feng
We got SDIO_CRC_ERROR with 4373 on SDR104 when doing bi-directional
throughput test. Enable watermark to 256 to guarantee the operation
stability.
Maybe it would be better to clarify the unit of the watermark. Here you
use bytes,
On Tue, Nov 06, 2018 at 12:01:18AM +, adham.aboza...@microchip.com wrote:
> From: Adham Abozaeid
>
> Validate cfg parameters after being called by cfg80211 in set_wiphy_params
> before scheduling the work executed in handle_cfg_param
>
> Signed-off-by: Adham Abozaeid
> ---
>
38 matches
Mail list logo
