On 11/07/16 23:59, a...@linux-foundation.org wrote:
>
> The patch titled
> Subject: MAINTAINERS: remove unreachable people that have left Atmel
> has been added to the -mm tree. Its filename is
> maintainers-remove-unreachable-people-that-have-left-atmel.patch
>
> This patch should soo
Hi Johannes,
thank for review and sorry for long delays in replies. A parallel thread
with Dave a discussion was initiated regarding HW platform samples
availability. Current driver implementation supports a newer QSR10G
platform, which availability is limited due to the platform still being
i
On Mon, Jul 11, 2016 at 12:01 AM, Arnd Bergmann wrote:
>> ath9k reads the data from the EEPROM into memory. With that property
>> disabled ath9k simply assumes that the endianness of the values in the
>> EEPROM are having the correct endianness for the host system (in other
>> words: no swap is be
After discovering there are 2 very different 14e4:4365 PCI devices we
made ID tables less generic. Back then we believed there are only 2 such
devices:
1) 14e4:4365 1028:0016 with SoftMAC BCM43142 chipset
2) 14e4:4365 14e4:4365 with FullMAC BCM4366 chipset
>From the recent report it appears there
From: Colin King
Date: Mon, 11 Jul 2016 16:54:20 +0100
> From: Colin Ian King
>
> idx can be returned as -ENOSPC, so we should check for this first
> before using it as an index into nn->vxlan_usecnt[] to avoid an
> out of bounds array offset read.
>
> Signed-off-by: Colin Ian King
Applied t
The iwl-debug.h header relies in implicit inclusion of linux/device.h and
we get a lot of warnings without that:
drivers/net/wireless/intel/iwlwifi/iwl-debug.h:44:23: error: 'struct device'
declared inside parameter list will not be visible outside of this definition
or declaration [-Werror]
vo
On 07/11/2016 02:27 PM, Grumbach, Emmanuel wrote:
> On Mon, 2016-07-11 at 14:19 -0400, Prarit Bhargava wrote:
>>
>> On 07/11/2016 02:00 PM, Emmanuel Grumbach wrote:
>>> On Mon, Jul 11, 2016 at 6:18 PM, Prarit Bhargava >>> wrote:
Didn't get any feedback or review comments on this patch.
On Sun, Jul 10, 2016 at 03:30:49PM +, Grumbach, Emmanuel wrote:
> Hi Kyle,
>
> Intel is releasing new firmware versions for all its mvm wireless
> devices.
> For devices 7260, 7265 and 3160, this is the last firmware updates. We
> may still have critical bug fixes, but those won't get any new
On Mon, 2016-07-11 at 14:19 -0400, Prarit Bhargava wrote:
>
> On 07/11/2016 02:00 PM, Emmanuel Grumbach wrote:
> > On Mon, Jul 11, 2016 at 6:18 PM, Prarit Bhargava > > wrote:
> > >
> > > Didn't get any feedback or review comments on this patch.
> > > Resending ...
> > >
> > > P.
> >
> > This
On 07/11/2016 02:00 PM, Emmanuel Grumbach wrote:
> On Mon, Jul 11, 2016 at 6:18 PM, Prarit Bhargava wrote:
>>
>> Didn't get any feedback or review comments on this patch. Resending ...
>>
>> P.
>
> This change is obviously completely broken. It simply disables the
> registration to thermal zon
On Mon, Jul 11, 2016 at 6:18 PM, Prarit Bhargava wrote:
>
> Didn't get any feedback or review comments on this patch. Resending ...
>
> P.
This change is obviously completely broken. It simply disables the
registration to thermal zone core.
>
> ---8<---
>
> The iwlwifi driver implements a therm
On 07/11/2016 12:07 PM, Coelho, Luciano wrote:
> On Mon, 2016-07-11 at 11:18 -0400, Prarit Bhargava wrote:
>> Didn't get any feedback or review comments on this patch. Resending
>> ...
>>
>> P.
>
> Sorry, this got flooded down my inbox.
NP, Luciano -- My worry was that it hadn't been seen or d
On Mon, 2016-07-11 at 11:18 -0400, Prarit Bhargava wrote:
> Didn't get any feedback or review comments on this patch. Resending
> ...
>
> P.
Sorry, this got flooded down my inbox.
> ---8<---
>
> The iwlwifi driver implements a thermal zone and hwmon device, but
> returns -EIO on temperature r
Hi Colin,
On Mon, Jul 11, 2016 at 04:46:57PM +0100, Colin King wrote:
> diff --git a/drivers/nfc/fdp/fdp.c b/drivers/nfc/fdp/fdp.c
> index e44a7a2..d93d314 100644
> --- a/drivers/nfc/fdp/fdp.c
> +++ b/drivers/nfc/fdp/fdp.c
> @@ -345,7 +345,7 @@ static void fdp_nci_release_firmware(struct nci_dev *
On Mon, 11 Jul 2016 16:54:20 +0100, Colin King wrote:
> From: Colin Ian King
>
> idx can be returned as -ENOSPC, so we should check for this first
> before using it as an index into nn->vxlan_usecnt[] to avoid an
> out of bounds array offset read.
>
> Signed-off-by: Colin Ian King
Acked-by: Ja
From: Colin Ian King
idx can be returned as -ENOSPC, so we should check for this first
before using it as an index into nn->vxlan_usecnt[] to avoid an
out of bounds array offset read.
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/netronome/nfp/nfp_net_common.c | 2 +-
1 file changed,
Ignore this, got some other fix included by mistake. Will resend.
On 11/07/16 16:46, Colin King wrote:
> From: Colin Ian King
>
> idx can be returned as -ENOSPC, so we should check for this first
> before using it as an index into nn->vxlan_usecnt[] to avoid an
> out of bounds array offset read.
From: Colin Ian King
idx can be returned as -ENOSPC, so we should check for this first
before using it as an index into nn->vxlan_usecnt[] to avoid an
out of bounds array offset read.
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/netronome/nfp/nfp_net_common.c | 2 +-
drivers/nfc/fdp/
Didn't get any feedback or review comments on this patch. Resending ...
P.
---8<---
The iwlwifi driver implements a thermal zone and hwmon device, but
returns -EIO on temperature reads if the firmware isn't loaded. This
results in the error
iwlwifi-virtual-0
Adapter: Virtual device
ERROR: Can
From: Ganapathi Bhat
It's been observed that firmware sends RADAR detected event without
specifying bss_num/bss_type. Also, the event body is empty.
Currently the event is being ignored by driver.
This patch checks on which interface 11H is active, accordingly fills
bss_num/bss_type and handles
From: Xinming Hu
This patch adds HT support for adhoc station. Firmware will upload
ibss sta connect event with beacon data, whenever new station joins
the adhoc network. Driver will check the HT IE and decide whether to
support HT aggreagation or not.
Signed-off-by: Xinming Hu
Signed-off-by: C
Disconnect message in mwifiex_reset_connect_state() would displays
necessary information. We unnecessarily have exactly same message in
cfg80211_disconnect(). As priv->cfg_bssid is cleared at this point of
time, it prints incorrect(all zero) MAC.
This message is removed here.
Signed-off-by: Amitk
From: Karthik D A
region code is an EEPROM setting received from firmware. Let's display
this in debugfs along with other information.
Signed-off-by: Karthik D A
Signed-off-by: Amitkumar Karwar
---
drivers/net/wireless/marvell/mwifiex/debugfs.c | 2 ++
1 file changed, 2 insertions(+)
diff --
From: Karthik D A
The driver sends and recives information to and from the firmware.
Correct endianness should be ensured as firmware follows little
endian format and host can be little/big endian.
Signed-off-by: Karthik D A
Signed-off-by: Amitkumar Karwar
---
drivers/net/wireless/marvell/mwi
It is observed that hostapd fails to setup with management frame
protection mode enabled when using mwifiex. This patch adds
cfg80211_set_default_mgmt_key handler to resolve the problem.
Signed-off-by: Amitkumar Karwar
---
drivers/net/wireless/marvell/mwifiex/cfg80211.c | 13 +
1 fil
From: Xinming Hu
Firmware may filter and drop packets under certain condition, for
example, ARP SA=DA packet. this event will be used to synchronize
the Rx Block Acknowledgment (BA) window bitmap and to fill any holes
in driver side.
Signed-off-by: Xinming Hu
Signed-off-by: Amitkumar Karwar
--
From: Ganapathi Bhat
This patch advertises RANDOM_MAC_ADDR feature to cfg80211. It allow the
application to issue scan with a MAC address and mask. Random MACs are
generated and used in probe requests sent for scanning until it is changed
by the application or device is restarted.
Signed-off-by:
Recent patch "mwifiex: fix NULL pointer" skips extended scan event
handling when suspend is in progress. It created a problem for scan
after interface disabled/enabled case.
This patch solves the problem by checking netif_running() status.
Fixes:16d25da94f3d654 ("mwifiex: fix NULL pointer derefer
This patch series includes couple of fixes and enhancements.
Amitkumar Karwar (3):
mwifiex: fix failed to reconnect after interface disabled/enabled
mwifiex: cfg80211 set_default_mgmt_key handler
mwifiex: remove misleading disconnect message
Ganapathi Bhat (2):
mwifiex: support random MAC
FW will provide a TX rate per link for each FW status,
and wlcore will be able to store the information for
the use of the mesh hwmp module.
This is used mainly in mesh.
Rates are reported when a mesh interface is up.
Signed-off-by: Maxim Altshul
---
Send both patches + fixes for reduntant null
Adding this opcode, allows the TI wireless driver,
to report throughput directly from FW to mac80211.
This is used mainly for mesh metric calculation.
Signed-off-by: Maxim Altshul
---
drivers/net/wireless/ti/wlcore/main.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/
Mesh HWMP module will be able to rely on the HW
RC algorithm if it exists, for path metric calculations.
This allows the metric calculation mechanism to calculate
a correct metric, based on PER and last TX rate both via
HW RC algorithm if it exists or via parameters collected
by the SW.
Signed-of
What are you trying to accomplish? I look forward to seeing any rate
control algorithm that can address the issues in minstrel!
( http://blog.cerowrt.org/post/minstrel/ )
It has generally been my hope to implement some form of better service
sharing between the VO, VI, and BE queues than what curr
On 2016-07-11 15:52, Toke Høiland-Jørgensen wrote:
> Felix Fietkau writes:
>
>> drv_wake_tx_queue will only call into the driver if there are frames
>> pending in the mac80211 queue. the driver needs to take care of its own
>> queued frames
>
> Thanks, makes sense. What's the proper etiquette he
Felix Fietkau writes:
> drv_wake_tx_queue will only call into the driver if there are frames
> pending in the mac80211 queue. the driver needs to take care of its own
> queued frames
Thanks, makes sense. What's the proper etiquette here? Do I roll these
up into a v4 (possibly with other changes
The logic was inverted here, set the bit if frames are pending.
Fixes: ba8c3d6f16a1 ("mac80211: add an intermediate software queue
implementation")
Signed-off-by: Felix Fietkau
---
net/mac80211/rx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/mac80211/rx.c b/net/mac8
mac80211 needs to know about driver queued frames
Signed-off-by: Felix Fietkau
---
drivers/net/wireless/ath/ath9k/xmit.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/wireless/ath/ath9k/xmit.c
b/drivers/net/wireless/ath/ath9k/xmit.c
index b3521c3..18c7443 100644
--- a/drive
drv_wake_tx_queue will only call into the driver if there are frames
pending in the mac80211 queue. the driver needs to take care of its own
queued frames
Signed-off-by: Felix Fietkau
---
drivers/net/wireless/ath/ath9k/xmit.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/net/wi
Hello everybody!
I'm a student working on a project about mac80211. I'm trying to modify
the behaviour of the AC's queues but I could really need some help about
this subject.
We are implementing a rate control algorithm. To do this we enqueue
packets on ieee80211_tx_frags() function, just
Hi Kalle,
I have one more patch intended for 4.8. I had forgotten to bump the FW
API version that our driver is now able to load. I hope there is still
time to get it included for 4.8.
Let me know if everything's fine (or not). :)
Luca.
The following changes since commit 6f482e37b75d4e56cdb9
Hi Kalle,
This is a fix for a warning that was spotted by Linus. We already have
this patch queued in -next, but it should have gone to -fixes. I hope
it is still possible to send it for 4.7. And it shouldn't be a problem
to have it in both, right? I guess git merge would take care of that.
Le
Remove a misleading debug message as well
Signed-off-by: Felix Fietkau
---
drivers/net/wireless/ath/ath9k/ar9003_calib.c | 54 +++
1 file changed, 22 insertions(+), 32 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/ar9003_calib.c
b/drivers/net/wireless/ath/ath
AR_PHY_65NM_CH0_THERM and AR_CH0_THERM were supposed to refer to the
same register, however they had different SREV checks.
Remove the duplicate and use the checks. Since there were other SREV
checks present in the only place that uses this, this will probaby not
affect runtime behavior.
Signed-o
Reduce indentation, use a variable to save a few pointer dereferences
Signed-off-by: Felix Fietkau
---
drivers/net/wireless/ath/ath9k/ar9003_calib.c | 53 +--
1 file changed, 26 insertions(+), 27 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/ar9003_calib.c
b/
Signed-off-by: Felix Fietkau
---
drivers/net/wireless/ath/ath9k/ar9003_calib.c | 25 ++---
drivers/net/wireless/ath/ath9k/hw.h | 1 +
2 files changed, 23 insertions(+), 3 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/ar9003_calib.c
b/drivers/net/wireles
On 11-7-2016 9:39, Marcel Holtmann wrote:
> Hi Julian,
>
>> This function emits NL80211_CMD_NEW_INTERFACE or
>> NL80211_CMD_DEL_INTERFACE events. This is meant to be used by the core
>> to notify userspace applications such as wpa_supplicant when a netdev
>> related to a wireless
The register layout of AR_PHY_SPECTRAL_SCAN has changed, only AR9280
uses the old layout
Signed-off-by: Felix Fietkau
---
drivers/net/wireless/ath/ath9k/ar9002_phy.c | 32 +
drivers/net/wireless/ath/ath9k/ar9002_phy.h | 5 -
2 files changed, 27 insertions(+), 10
Stephen Rothwell writes:
> Today's linux-next merge of the wireless-drivers-next tree got a
> conflict in:
>
> drivers/net/wireless/intel/iwlwifi/mvm/scan.c
>
> between commit:
>
> 7947d3e075cd ("mac80211: Add support for beacon report radio measurement")
>
> from the net-next tree and commit
Hi Julian,
> This function emits NL80211_CMD_NEW_INTERFACE or
> NL80211_CMD_DEL_INTERFACE events. This is meant to be used by the core
> to notify userspace applications such as wpa_supplicant when a netdev
> related to a wireless device has been added or removed.
>
> Sig
49 matches
Mail list logo