On 2016年07月06日 09:28, Masashi Honma wrote:
> Though netlink_broadcast() ...
Thanks for reply of David Miller, Eric Dumazet, David Teigrand.
On the basis of their comment, only rtnl_unicast() looks need to add gfp
flag
argument. So I will drop almost of patches except 0005.
I will send patch v2
From: Johannes Berg
Date: Wed, 6 Jul 2016 14:27:43 +0200
> People found two more bugs, so I have two more fixes. Both are related to
> memory - one's a leak, the other is a missing allocation failure check.
>
> These are both tagged for stable already, and shouldn't
On 2016年07月09日 01:08, David Teigland wrote:
On Thu, Jul 07, 2016 at 09:35:45AM +0900, Masashi Honma wrote:
At the fs/dlm/netlink.c#dlm_timeout_warn(),
prepare_data allocates buffer with GFP_NOFS
and send_data() sends the buffer.
But send_data() uses GFP_KERNEL or GFP_ATOMIC inside it.
Should
From: Dan Kephart
When an NL80211_DISCONNECT is sent to cfg80211, the driver's cfg80211
disconnect function sets the sme_state to SME_DISCONNECTED before receiving
a WMI_DISCONNECT_EVENT from the firmware. This caused cfg80211 to not know
that the connection is
This change alters the semantics of NL80211_CMD_NEW_INTERFACE events
by always sending this event whenever a new net_device object
associated with a wdev is registered. Prior to this change, this event
was only sent as a result of NL80211_CMD_NEW_INTERFACE command sent
from userspace. This
This change alters the semantics of NL80211_CMD_DEL_INTERFACE events
by always sending this event whenever a net_device object associated
with a wdev is destroyed. Prior to this change, this event was only
emitted as a result of NL80211_CMD_DEL_INTERFACE command sent from
userspace. This allows
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.
Signed-off-by: Denis Kenzior
The current mechanism to detect hot-plug / unplug of wireless devices is
somewhat arcane. One has to listen to NEW_WIPHY/DEL_WIPHY events over
nl80211 as well as RTM_NEWLINK / RTM_DELLINK events over rtnl, then
somehow find a correlation between these events. This involves userspace
sending
for me it crashes on wds sta on 3.18 kernels. need to solder a serial to
get more logs
Am 08.07.2016 um 18:31 schrieb Felix Fietkau:
On 2016-07-08 18:28, Toke Høiland-Jørgensen wrote:
Felix Fietkau writes:
On 2016-07-08 17:53, Toke Høiland-Jørgensen wrote:
Kalle Valo
Felix Fietkau writes:
> On 2016-07-08 18:28, Toke Høiland-Jørgensen wrote:
>> Felix Fietkau writes:
>>
>>> On 2016-07-08 17:53, Toke Høiland-Jørgensen wrote:
Kalle Valo writes:
> Toke Høiland-Jørgensen wrote:
>> This
On 2016-07-08 18:28, Toke Høiland-Jørgensen wrote:
> Felix Fietkau writes:
>
>> On 2016-07-08 17:53, Toke Høiland-Jørgensen wrote:
>>> Kalle Valo writes:
>>>
Toke Høiland-Jørgensen wrote:
> This switches ath9k over to using the mac80211
Felix Fietkau writes:
> On 2016-07-08 17:53, Toke Høiland-Jørgensen wrote:
>> Kalle Valo writes:
>>
>>> Toke Høiland-Jørgensen wrote:
This switches ath9k over to using the mac80211 intermediate software
queueing mechanism for data packets. It
On 2016-07-08 17:53, Toke Høiland-Jørgensen wrote:
> Kalle Valo writes:
>
>> Toke Høiland-Jørgensen wrote:
>>> This switches ath9k over to using the mac80211 intermediate software
>>> queueing mechanism for data packets. It removes the queueing inside the
>>> driver,
On Fri, Jul 8, 2016 at 6:29 PM, Manoharan, Rajkumar
wrote:
> I think security failures are due to peer unmap & map upon reassoc. Can you
> please try below change?
>
> diff --git a/drivers/net/wireless/ath/ath10k/mac.c
> b/drivers/net/wireless/ath/ath10k/mac.c
> index
On Fri, Jul 8, 2016 at 9:17 PM, Ben Greear wrote:
> On 07/08/2016 08:44 AM, Krishna Chaitanya wrote:
>>
>> On Fri, Jul 8, 2016 at 9:12 PM, Ben Greear
>> wrote:
>>>
>>> On 07/08/2016 08:39 AM, Krishna Chaitanya wrote:
>>>
Also can you please
Kalle Valo writes:
> Toke Høiland-Jørgensen wrote:
>> This switches ath9k over to using the mac80211 intermediate software
>> queueing mechanism for data packets. It removes the queueing inside the
>> driver, except for the retry queue, and instead pulls from mac80211
On 07/08/2016 08:44 AM, Krishna Chaitanya wrote:
On Fri, Jul 8, 2016 at 9:12 PM, Ben Greear wrote:
On 07/08/2016 08:39 AM, Krishna Chaitanya wrote:
Also can you please tell me how to make ath10k use minstrel rc, its needed
for comparative purposes? Is disable
On Fri, Jul 8, 2016 at 9:12 PM, Ben Greear wrote:
> On 07/08/2016 08:39 AM, Krishna Chaitanya wrote:
>
>> Also can you please tell me how to make ath10k use minstrel rc, its needed
>> for comparative purposes? Is disable HW_RATE_CONTROL enough or does
>> it need more
On 07/08/2016 08:39 AM, Krishna Chaitanya wrote:
Also can you please tell me how to make ath10k use minstrel rc, its needed
for comparative purposes? Is disable HW_RATE_CONTROL enough or does
it need more changes?
It cannot be done. You have to use whatever rate-ctrl is baked into the
On Fri, Jul 8, 2016 at 9:07 PM, Krishna Chaitanya
wrote:
> On Fri, Jul 8, 2016 at 8:57 PM, Krishna Chaitanya
> wrote:
>> On Fri, Jul 8, 2016 at 6:29 PM, Manoharan, Rajkumar
>> wrote:
>>> I think security failures are
On Fri, Jul 8, 2016 at 8:57 PM, Krishna Chaitanya
wrote:
> On Fri, Jul 8, 2016 at 6:29 PM, Manoharan, Rajkumar
> wrote:
>> I think security failures are due to peer unmap & map upon reassoc. Can you
>> please try below change?
>>
>> diff
Hi Johannes,
>> Are you okay with the general approach?
I see no issues with sending these events out. I'd like them to
actually be reliable (if present) though, not double as you'd implied -
but I didn't really understand in which cases you were expecting
issues, was it only P2P-Device?
On Fri, 2016-07-08 at 10:22 -0500, Denis Kenzior wrote:
>
> Apologies, I've only been looking at the kernel side for several
> days, so my understanding is still incomplete.
>
> I was looking at mac80211/iface.c: ieee80211_if_add() which seems to
> handle NL80211_IFTYPE_P2P_DEVICE specially by
Hi Johannes,
On 07/08/2016 05:32 AM, Johannes Berg wrote:
On Thu, 2016-07-07 at 02:08 -0500, Denis Kenzior wrote:
The current mechanism to detect hot-plug / unplug of wireless devices
is
somewhat arcane. One has to listen to NEW_WIPHY/DEL_WIPHY events
over
nl80211 as well as RTM_NEWLINK /
We don't have access to datasheets to document all the bits but we can
name these registers at least.
Signed-off-by: Rafał Miłecki
---
V2: Fix mistake in V1 that used BCMA_CCB_MII_MNG_CMD_DATA instead of
BCMA_CCB_MII_MNG_CTL in the second bcma_wait_reg call.
---
> From: Prasun Maiti [mailto:prasunmait...@gmail.com]
> Sent: Monday, June 27, 2016 3:43 PM
> To: Amitkumar Karwar
> Cc: Nishant Sarmukadam; Linux Wireless; Linux Next; Linux Kernel; Kalle
> Valo
> Subject: [PATCH v4] mwifiex: Reduce endian conversion for REG Host
> Commands
>
> For multiple REG
> From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless-
> ow...@vger.kernel.org] On Behalf Of Kalle Valo
> Sent: Friday, July 08, 2016 7:10 PM
> To: Amitkumar Karwar
> Cc: Prasun Maiti; Nishant Sarmukadam; Linux Wireless; Linux Next; Linux
> Kernel
> Subject: Re: [PATCH v4] mwifiex:
Rajkumar Manoharan wrote:
> Add NAPI support for rx and tx completion. NAPI poll is scheduled
> from interrupt handler. The design is as below
>
> - on interrupt
> - schedule napi and mask interrupts
> - on poll
>- process all pipes (no actual Tx/Rx)
>-
Toke Høiland-Jørgensen wrote:
> This switches ath9k over to using the mac80211 intermediate software
> queueing mechanism for data packets. It removes the queueing inside the
> driver, except for the retry queue, and instead pulls from mac80211 when
> a packet is needed. The retry queue is used to
Vasanthakumar Thiagarajan wrote:
> As hw cycle counters in QCA4019 wraparound independantly in QCA4019
> it is possible cycle counter and rx clear counter would wraparound
> at the same time. Current logic assumes only one of the counters
> would wraparound at anytime.
Bjorn Andersson wrote:
> Sometimes the firmware sends a HAL_DEL_BA_IND, the prima driver silently
> ignore this message so let's do the same to silence the error message.
>
> Cc: Nicolas Dechesne
> Signed-off-by: Bjorn Andersson
Benjamin Berg wrote:
> From: Benjamin Berg
>
> Beacons were not send out at (timestamp % beacon_time == 0) for interfaces
> other than the primary one. To send out beacons with the correct timestamp
> according to 10.1.3.2 of the 802.11
Martin Blumenstingl wrote:
> Some devices running OpenWrt need this and it makes sense to add this
> to ath9k_platform_data as the next patches will add a devicetree
> (boolean) property for it as well.
>
> Suggested-by: Vittorio Gambaletta
Bjorn Andersson wrote:
> From: Bjorn Andersson
>
> Merge the two allocation instead of separately allocating room for the
> indication payload.
>
> Signed-off-by: Bjorn Andersson
> Signed-off-by: Bjorn
Larry Finger wrote:
> All of the rtlwifi family of drivers have a similar routine that acquires
> the hardware info from efuse and initializes a number of variables in the
> driver's private area. A common routine is created for all drivers to use.
>
> Reported-by:
Amitkumar Karwar wrote:
> From: Shengzhen Li
>
> As interrupt is read in interrupt handler as well as interrupt processing
> thread, we observed a corner case issue for MSI in which interrupt gets
> processed twice.
>
> This patch moves interrupt reading
Brian Norris wrote:
> The PCIe driver didn't mask the host interrupts before trying to tear
> down. This causes lockups at reboot or rmmod when using MSI-X on 8997,
> since the MSI handler gets confused and locks up the system.
>
> Also tested on 8897, which does not
Amitkumar Karwar wrote:
> PCIe-USB8997 variant is being used in the product. Let's change default
> firmware from PCIe-UART to PCIe-USB. So by default PCIe-USB firmware would
> be downloaded if version register doesn't give any information.
>
> Signed-off-by: Amitkumar
Prasun Maiti wrote:
> The two members min_scan_time and max_scan_time of structure
> "mwifiex_ie_types_btcoex_scan_time" are of two bytes each. The values
> are assigned directtly from firmware without endian conversion handling.
> So, wrong datas will get saved in
Rafał Miłecki wrote:
> So far when receiving event about in-firmware-interface removal our
> event worker was notifying listener and afterwards it was removing Linux
> interface.
>
> First of all it was resulting in slightly unexpected order. The listener
> (del_virtual_intf callback) was
Amitkumar Karwar wrote:
> scan_block flag is used to block scan operation when 4 way handshake
> is in progress. Sometimes it doesn't get cleared due to incomplete
> association. An example is assoc request/response is done, but add key
> operation get canceled in some corner
Masanari Iida wrote:
> This patch fix spelling typos found in drivers/net/wireless/realtek.
>
> Signed-off-by: Masanari Iida
> Reviewed-by: Julian Calaby
Thanks, 1 patch applied to wireless-drivers-next.git:
8a1902374fa0
Jes Sorensen wrote:
> From: Jes Sorensen
>
> This needs to be handled locally in the parse_rx_desc() function in
> order to be able to handle aggregated packets in the future.
>
> Signed-off-by: Jes Sorensen
Thanks,
Amitkumar Karwar writes:
>> From: Prasun Maiti [mailto:prasunmait...@gmail.com]
>> Sent: Monday, June 27, 2016 3:43 PM
>> To: Amitkumar Karwar
>> Cc: Nishant Sarmukadam; Linux Wireless; Linux Next; Linux Kernel; Kalle
>> Valo
>> Subject: [PATCH v4] mwifiex: Reduce endian
I think security failures are due to peer unmap & map upon reassoc. Can you
please try below change?
diff --git a/drivers/net/wireless/ath/ath10k/mac.c
b/drivers/net/wireless/ath/ath10k/mac.c
index 5e1cc8f4c43c..f7f04bb46fc8 100644
--- a/drivers/net/wireless/ath/ath10k/mac.c
+++
On Fri, Jul 8, 2016 at 3:39 PM, Manoharan, Rajkumar
wrote:
>>> I am using ath10k driver with qca988x hw2.0 and trying to limit it to use
>>> VHT MCS0-7 (iw set bitrates vht-mcs-5 2:0-7).
>>>
>>> But the command it causing a FW crash, if it disable HW_HAS_RATE_CONTROL
Hi Kalle,
> From: Prasun Maiti [mailto:prasunmait...@gmail.com]
> Sent: Monday, June 27, 2016 3:43 PM
> To: Amitkumar Karwar
> Cc: Nishant Sarmukadam; Linux Wireless; Linux Next; Linux Kernel; Kalle
> Valo
> Subject: [PATCH v4] mwifiex: Reduce endian conversion for REG Host
> Commands
>
> For
Hi Michal / Kalle / Ben,
is this patch is good to go (or) should i re-work ?
I had replied to Michal's comment of introducing a new firmware
feature flag will not address the issue in older firmware / code.
Let me know if i had missed something very obvious.
On Tue, Jul 05, 2016 at 08:21:01AM
On Fri, 2016-07-08 at 16:02 +0530, Purushottam Kushwaha wrote:
> Driver may support different beacon interval on virtual interfaces.
> Allow setting different beacon interval per interface if driver has
> such support.
>
It seems this should be an nl80211 feature flag (ext features)
johannes
--
On Fri, 2016-07-08 at 15:58 +0530, Purushottam Kushwaha wrote:
>
> *
> + * @NL80211_ATTR_BEACON_TXRATE: User configurable beacon data rate
> (u32). This is
> + * used to set beacon tx rate.
>
It seems this should be nested from enum nl80211_tx_rate_attributes, to
perhaps allow HT/VHT beacons
Driver may support different beacon interval on virtual interfaces.
Allow setting different beacon interval per interface if driver has
such support.
Signed-off-by: Purushottam Kushwaha
---
include/net/cfg80211.h | 5 +
net/wireless/util.c| 3 +++
2 files
On Thu, 2016-07-07 at 02:08 -0500, Denis Kenzior wrote:
> The current mechanism to detect hot-plug / unplug of wireless devices
> is
> somewhat arcane. One has to listen to NEW_WIPHY/DEL_WIPHY events
> over
> nl80211 as well as RTM_NEWLINK / RTM_DELLINK events over rtnl, then
> somehow find a
This will allow user to configure beacon tx rate from userspace. This adds
new nl80211 attribute as NL80211_ATTR_BEACON_RATE.
Signed-off-by: Purushottam Kushwaha
---
include/net/cfg80211.h | 3 ++-
include/uapi/linux/nl80211.h | 5 +
net/wireless/nl80211.c
>> I am using ath10k driver with qca988x hw2.0 and trying to limit it to use
>> VHT MCS0-7 (iw set bitrates vht-mcs-5 2:0-7).
>>
>> But the command it causing a FW crash, if it disable HW_HAS_RATE_CONTROL
>> no crash is observed but it still uses MCS9.
>>
>> tree: wireless-drivers-next:
"Machani, Yaniv" wrote:
> Changed the configuration to support 64bit instead of 32bit
> this in order to offload the driver from handling a wraparound.
>
> Signed-off-by: Yaniv Machani
Thanks, 1 patch applied to wireless-drivers-next.git:
585dfe813fa5 wlcore:
Amitkumar Karwar wrote:
> We will derive sta_priv at the beginning of suspend handler.
> This will be useful for next patch in this series.
>
> Signed-off-by: Amitkumar Karwar
Thanks, 3 patches applied to wireless-drivers-next.git:
322397b268f7
"Reizer, Eyal" writes:
> Add support for using with both wl12xx and wl18xx.
>
> - all wilink family needs special init command for entering wspi mode.
> extra clock cycles should be sent after the spi init command while the
> cs pin is high.
> - Use inverted chip select for
Joe Perches wrote:
> This debugging macro can expand to a lot of code.
> Make it a function to reduce code size.
>
> (x86-64 defconfig w/ all rtlwifi drivers and allyesconfig)
> $ size drivers/net/wireless/realtek/rtlwifi/built-in.o*
>text data bss dec
Jes Sorensen wrote:
> From: Luis de Bethencourt
>
> reg_eac and reg_ecc are only used if candidate is bigger than 0, and in
> that case new values will be given to them. Removing the unused
> assignments.
>
> Signed-off-by: Luis de Bethencourt
We don't have access to datasheets to document all the bits but we can
name these registers at least.
Signed-off-by: Rafał Miłecki
---
drivers/bcma/driver_chipcommon_b.c | 10 ++
include/linux/bcma/bcma_driver_chipcommon.h | 3 +++
2 files changed, 9
> From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless-
> ow...@vger.kernel.org] On Behalf Of Nestor Machno
> Sent: Thursday, July 07, 2016 6:07 AM
> To: linux-wireless@vger.kernel.org
> Subject: Fwd: mwifiex+wpa_supplicant cannot set up WPA/WPA2 ADHOC
>
> Hi All,
> Amitkumar, can
writes:
> From: Tamizh chelvam
>
> This patch adds testmode support for 10.4 based chipsets
> and added code swap support for UTF binary.
>
> Signed-off-by: Tamizh chelvam
This patch introduced new checkpatch
Eduardo Abinader writes:
> just to comply with current ath9k_hw_nvram_read to return value, hence
> behaving reacting accordingly.
>
> Signed-off-by: Eduardo Abinader
> ---
> drivers/net/wireless/ath/ath9k/ar9003_eeprom.c | 6 --
Mohammed Shafi Shajakhan wrote:
> From: Mohammed Shafi Shajakhan
>
> Print an ath10k error message rather a call trace when HTT op version is
> not found from firmware META data (IE). This should be sufficient to figure
> out what went
ako...@qti.qualcomm.com wrote:
> From: Anilkumar Kolli
>
> rtc_state_cold_reset_mask is unused in ath10k_hw_regs.
> instead fixed delays are used.
>
> Signed-off-by: Anilkumar Kolli
Thanks, 2 patches applied to ath-next branch of ath.git:
Ben Greear wrote:
> From: Ben Greear
>
> Not sure this can happen, but seems like a reasonable sanity
> check.
>
> Signed-off-by: Ben Greear
Thanks, 2 patches applied to ath-next branch of ath.git:
c5ace87a886d
Eduardo Abinader wrote:
> just to comply to coding style.
>
> Signed-off-by: Eduardo Abinader
> Reviewed-by: Julian Calaby
Thanks, 1 patch applied to ath-next branch of ath.git:
9802977dcce5 ath10k: remove
Ashok Raj Nagarajan wrote:
> It is expected that all pktlog events for 10.4 firmware based solutions
> should come through CE8 where as in case of 10.2 firmware based solutions,
> it should come through one of the HTT events (HTT_T2H_MSG_TYPE_PKTLOG).
>
> But from
Chaehyun Lim wrote:
> is not used anymore, so just remove it.
>
> Signed-off-by: Chaehyun Lim
Thanks, 1 patch applied to ath-next branch of ath.git:
a3dadad73324 ath10k: remove unused
--
Sent by pwcli
Ben Greear wrote:
> From: Ben Greear
>
> Otherwise, the txrx-compl-task may access some bad memory?
>
> Signed-off-by: Ben Greear
Thanks, 2 patches applied to ath-next branch of ath.git:
de0170beaa88 ath10k: ensure
Mohammed Shafi Shajakhan wrote:
> From: Mohammed Shafi Shajakhan
>
> Enable support for 'drv_sta_statistics' callback.
> Export rx_duration support if available to cfg80211/nl80211
>
> This can also act as a placeholder for any new per STA
Mohammed Shafi Shajakhan wrote:
> From: Mohammed Shafi Shajakhan
>
> 10.4 'extended peer stats' will be not be appended with normal peer stats
> data and they shall be coming in separate chunks. Fix this by maintaining
> a separate linked
72 matches
Mail list logo