Emmanuel Grumbach wrote:
> I checked the diff between e91976c0 and 7596afd4 and it is very very small.
> Is your machine dual boot?
> A few users have reported a race between BT firmware load and Wifi
> firmware load. They also reported that booting in Windows, and then
> shutting down in Windows h
On Tue, Nov 06, 2018 at 11:49:12PM +0100, Lorenzo Bianconi wrote:
> Add mt76x02_config_mac_addr_list routine in order to set
> the mac address list supported by the driver. Initialize
> wiphy->addresses/n_addresses for mt76x0e driver
>
> Signed-off-by: Lorenzo Bianconi
> ---
> .../net/wireless/m
Hi Adham,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.20-rc1 next-20181106]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.c
> On Tue, Nov 06, 2018 at 11:49:12PM +0100, Lorenzo Bianconi wrote:
> > Add mt76x02_config_mac_addr_list routine in order to set
> > the mac address list supported by the driver. Initialize
> > wiphy->addresses/n_addresses for mt76x0e driver
> >
> > Signed-off-by: Lorenzo Bianconi
> > ---
> > ..
On Wed, Nov 07, 2018 at 05:05:01AM +, ajay.kat...@microchip.com wrote:
> 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 Sing
On Thu, 11 Oct 2018 at 22:21, Dan Haab wrote:
> The newest firmwares provide STA info using v7 of the struct. As v7
> isn't backward compatible, a union is needed.
>
> Even though brcmfmac does not use any of the new info it's important to
> provide the proper struct buffer. Without this change ne
Rafał Miłecki writes:
> On Thu, 11 Oct 2018 at 22:21, Dan Haab wrote:
>> The newest firmwares provide STA info using v7 of the struct. As v7
>> isn't backward compatible, a union is needed.
>>
>> Even though brcmfmac does not use any of the new info it's important to
>> provide the proper struct
On 11/7/2018 11:02 AM, Kalle Valo wrote:
Rafał Miłecki writes:
On Thu, 11 Oct 2018 at 22:21, Dan Haab wrote:
The newest firmwares provide STA info using v7 of the struct. As v7
isn't backward compatible, a union is needed.
Even though brcmfmac does not use any of the new info it's important
On 10/11/2018 10:19 PM, Dan Haab wrote:
The newest firmwares provide STA info using v7 of the struct. As v7
isn't backward compatible, a union is needed.
Even though brcmfmac does not use any of the new info it's important to
provide the proper struct buffer. Without this change new firmwares wi
From: Madhan Mohan R
Send p2p presence response from the p2p interface address instead
of the p2p device address. This is needed for p2p cert 6.1.9 to pass.
Signed-off-by: Madhan Mohan R
Signed-off-by: Chi-Hsien Lin
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c | 9 -
1 f
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 192.168.100.10
3. Bring down interface or
ifconfig wlan0 down or kill wpa_suppli
From: Ryohei Kondo
Miracast Certification clause 6.1.2 may fail if there is no WFD IE in
p2p assoc response. This change allows WFD IE to be added to p2p assoc
response.
Related WFA certification:
6.1.2 P-SnUT operating as a Group Owner accepts a WFD Session with a
Reference Source
Signed-off-b
This patch series addresses failures seen during p2p/miracast/apsta testing.
Chi-Hsien Lin (1):
brcmfmac: only generate random p2p address when needed
Madhan Mohan R (1):
brcmfmac: p2p cert 6.1.9-support GOUT handling p2p presence request
Ryohei Kondo (1):
brcmfmac: add vendor ie for assoc
P2p spec mentioned that the p2p device address should be the globally
administered address with locally administered bit set. Therefore,
follow this guideline by default.
When the primary interface is set to a locally administered address, the
locally administered bit cannot be set again. Generate
From: Wright Feng
APSTA can work on two band concurrently with using VSDB(Virtual
Simultaneous Dual-Band) or RSDB(Real Simultaneous Dual-Band) features.
In this case, we have to keep apsta is 1 in firmware side. However, if
we start wpa_supplicant on wlan0 and then start hostapd on wlan 1, the
ap
On 2018-10-30 21:02, Rob Herring wrote:
On Tue, Oct 30, 2018 at 3:41 AM wrote:
On 2018-10-16 00:54, Rob Herring wrote:
> On Thu, Oct 04, 2018 at 05:12:43PM +0530, Bhagavathi Perumal S wrote:
>> This adds new dt entry ext-fem-name, it is used by ath10k driver
>> to select correct timing paramet
Hello Tamizh,
> Co-Developed-by: Tamizh Chelvam
> Signed-off-by: Vasanthakumar Thiagarajan
> Signed-off-by: Tamizh chelvam
> ---
> include/net/cfg80211.h | 14 +++
> include/uapi/linux/nl80211.h | 69 +
> net/wireless/nl80211.c | 86
>
Rajkumar Manoharan writes:
> On 2018-11-02 03:30, Toke Høiland-Jørgensen wrote:
>> Rajkumar Manoharan writes:
>>
>>> On 2018-10-28 15:01, Rajkumar Manoharan wrote:
On 2018-10-28 08:48, Toke Høiland-Jørgensen wrote:
> Rajkumar Manoharan writes:
>
>>
>> 4ms 223 (40
This reverts commit cfb353c0dc058bc1619cc226d3cbbda1f360bdd3.
WCN3990 firmware does not yet implement this feature, and so it crashes
like this:
fatal error received: err_qdi.c:456:EX:wlan_process:1:WLAN RT:207a:PC=b001b4f0
This feature can be re-implemented with a proper service bitmap or oth
On 2018-11-07 10:56, Brian Norris wrote:
This reverts commit cfb353c0dc058bc1619cc226d3cbbda1f360bdd3.
WCN3990 firmware does not yet implement this feature, and so it crashes
like this:
fatal error received: err_qdi.c:456:EX:wlan_process:1:WLAN
RT:207a:PC=b001b4f0
This feature can be re-im
On 2018-11-07 06:53, Toke Høiland-Jørgensen wrote:
Rajkumar Manoharan writes:
Meanwhile we did some more experiments with both modes. The experiment
was done in open environment and fixed rate and UDP traffic ran for 60
seconds.
Seems like push mode not honoring the configured weight. Always
On 10/22/2018 10:55 AM, Tamizh chelvam wrote:
> /**
>* enum ieee80211_vif_flags - virtual interface flags
>*
> @@ -1565,6 +1594,8 @@ struct ieee80211_vif {
>
> bool txqs_stopped[IEEE80211_NUM_ACS];
>
> + struct ieee80211_tid_conf tid_conf;
> +
Why is there only one TID c
On Mon, Oct 8, 2018 at 2:03 AM Wen Gong wrote:
>
> In the noisy environment, if there are packets in the queue and can't
> send out, the suspend timing will be more than 5 seconds due to the wait,
> flush the queue to optimize the suspend timing, and let the upper layer to
> retry the packets afte
mac80211 may call us with vif == NULL, if the station is not currently
active (e.g., not associated). It is trivially easy to reproduce a crash
by suspending the system when not connected to an AP:
[ 65.533934] Unable to handle kernel NULL pointer dereference at virtual
address
On 10/22/2018 10:55 AM, Tamizh chelvam wrote:
>
> Add infrastructure for per TID aggregation/retry count configurations
> such as retry count and AMPDU aggregation control(disable/enable).
> In some scenario reducing the number of retry count for a specific data
> traffic can reduce the latency by
On 2018-11-08 03:00, Rajkumar Manoharan wrote:
On 2018-11-07 10:56, Brian Norris wrote:
This reverts commit cfb353c0dc058bc1619cc226d3cbbda1f360bdd3.
WCN3990 firmware does not yet implement this feature, and so it
crashes
like this:
fatal error received: err_qdi.c:456:EX:wlan_process:1:WLA
26 matches
Mail list logo
