Hi Sara,
[auto build test WARNING on mac80211-next/master]
[also build test WARNING on v4.5-rc5 next-20160223]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Emmanuel-Grumbach/mac80211-allow
On Wed, Feb 17, 2016 at 4:34 PM, Ross Green wrote:
> Appreciate your efforts!
>
> Just trying to make sure it does not get lost.
> Introduced in rc1, not fixed by ... rc4.
>
> Anyway, I will continue to test, lots of other things still to chase
> even in rc4!
>
> Regards,
>
>
Hi Sara,
[auto build test WARNING on mac80211-next/master]
[also build test WARNING on v4.5-rc5 next-20160223]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Emmanuel-Grumbach/mac80211-allow
On Tue 2016-02-23 21:55:14, Johannes Berg wrote:
> On Tue, 2016-02-23 at 21:45 +0100, Pavel Machek wrote:
>
> > So... you add LED trigger to display the state of the airplane
> > mode. Ok, why not.
>
> Yes. However, consider that "the airplane mode" isn't a well-defined
> concept; some systems
On Tue, Feb 23, 2016 at 03:10:27PM +0100, Johannes Berg wrote:
> What you really "want" is to use VHT modulations, mostly for the
> dubious purpose of marketing benchmarks to reach 256-QAM modulations.
>
> I think the de-facto standard for this would be to use IEs similar to
> VHT ones,
From: Johannes Berg
This was requested by Android, and the appropriate cfg80211 API
had been added by Dmitry. Support it in mac80211, allowing drivers
to provide the timestamp.
Signed-off-by: Johannes Berg
---
include/net/mac80211.h | 3 +++
On Tue, 2016-02-23 at 21:45 +0100, Pavel Machek wrote:
> So... you add LED trigger to display the state of the airplane
> mode. Ok, why not.
Yes. However, consider that "the airplane mode" isn't a well-defined
concept; some systems may want to light up that LED even when wifi is
still enabled,
On Tue, 2016-02-23 at 21:46 +0100, Arend Van Spriel wrote:
>
> > Maybe we should be less specific here regarding the NLA_FLAG and
> > say
> > that it will contain attributes for each, indicating which
> > behaviours
> > are supported, and say there's behaviour-dependent data inside each
> > of
>
On 23-2-2016 15:20, Johannes Berg wrote:
> On Wed, 2016-02-17 at 11:47 +0100, Arend van Spriel wrote:
>>
>> + * @NL80211_ATTR_BSS_SELECT: nested attribute for driver supporting the
>> + * BSS selection feature. When used with %NL80211_CMD_GET_WIPHY it contains
>> + * NLA_FLAG type according
On Mon 2016-02-22 11:36:35, João Paulo Rechi Vita wrote:
> There is still quite a bit of code using this interface, so we can't
> just remove it. Hopefully it will be possible in the future, but since
> its scheduled removal date is past 2 years already, we are better having
> the documentation
On Tue, 2016-02-23 at 16:06 +0100, Arnd Bergmann wrote:
>
> Does rfkill always have a separate device in the Linux driver model?
Yes, the rfkill core code registers and adds one in the rfkill class.
> johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the
From: Sara Sharon
When HW crypto is used, there's no need for the CCMP/GCMP MIC to
be available to mac80211, and the hardware might have removed it
already after checking. The MIC is also useless to have when the
frame is already decrypted, so allow indicating that it's
On Tue, 2016-02-23 at 13:43 -0500, Avery Pennarun wrote:
> We're putting my version of the patch into our devices in order to be
> able to try different values and see how it changes the percentage of
> devices with nonzero 'pending' field in agg_status. I'm hoping using
> zero here will result
From: poh
Check and set Rx MAC timestamp when firmware indicates it.
Firmware adds it in Rx beacon frame only at this moment.
Driver and mac80211 may utilize it to detect such clockdrift
or beacon collision and use the result for beacon collision
avoidance.
Signed-off-by:
On 2016-02-23 14:05, Johannes Berg wrote:
>> Yes. If A-MSDU in A-MPDU is not supported, dealing with starting and
>> stopping of A-MPDU sessions leaves all kinds of nasty corner cases
>> (since the txq is not flushed between sessions). In that case it's
>> better to just leave it disabled from
Hi poh,
[auto build test WARNING on wireless-drivers-next/master]
[also build test WARNING on v4.5-rc5 next-20160223]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Oh/ath10k-set-MAC
On Tue, Feb 23, 2016 at 5:14 AM, Johannes Berg
wrote:
> On Tue, 2016-02-16 at 16:28 -0500, Avery Pennarun wrote:
>> Since around the beginning of time, ath9k aggregates have timed out
>> after
>> 5000 TU (around 5000ms) of inactivity, but nobody seems to be quite
>>
This allows small static builds, especially when using musl libc.
Signed-off-by: Dima Krasner
---
Makefile | 8
iw.c | 10 --
iw.h | 2 +-
3 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/Makefile b/Makefile
index e61825e..4077020
From: poh
Check and set Rx MAC timestamp when firmware indicates it.
Firmware adds it in Rx beacon frame only at this moment.
Driver and mac80211 may utilize it to detect such clockdrift
or beacon collision and use the result for beacon collision
avoidance.
Signed-off-by:
Hello.
I think there might be a bug in the following code of minstrel_ht when
deciding if RTS/CTS should be enabled:
/* enable RTS/CTS if needed:
* - if station is in dynamic SMPS (and streams > 1)
* - for fallback rates, to increase chances of getting through
*/
if (offset
On Tue, 2016-02-23 at 15:53 +0100, Felix Fietkau wrote:
> > Perhaps we could live with this being done only for the fast-xmit
> > case?
> I don't think we should pass padded vs non-padded frames depending on
> whether fast-xmit was used. The non-fast-xmit codepath could simply
> do the memmove at
Add USB ID 0411:01fd for Buffalo WLI-UC-G450 wireless adapter,
RT chipset 3593
Signed-off-by: Anthony Wong
Cc: sta...@vger.kernel.org
---
drivers/net/wireless/ralink/rt2x00/rt2800usb.c | 1 +
1 file changed, 1 insertion(+)
diff --git
On Tuesday 23 February 2016 14:42:55 Marc Dietrich wrote:
> Am Dienstag, 23. Februar 2016, 14:17:17 CET schrieb Arnd Bergmann:
> > On Tuesday 23 February 2016 11:38:52 Marc Dietrich wrote:
> > > Am Dienstag, 23. Februar 2016, 11:31:40 CET schrieb Arnd Bergmann:
> > Ah, so the problem of attaching
On 02/23/2016 06:22 AM, Johannes Berg wrote:
On Tue, 2016-02-23 at 06:18 -0800, Ben Greear wrote:
[root@ben-ota2 lanforge]# iw phy wiphy0 info
Wiphy wiphy0
Band 1:
[...]
VHT Capabilities (0x338001b2):
Max MPDU length: 11454
On 2016-02-23 15:29, Johannes Berg wrote:
> On Fri, 2016-02-19 at 11:01 +0100, Janusz Dziedzic wrote:
>> HW/driver should set NEED_ALIGNED4_SKBS flag in case
>> require aligned skbs to four-byte boundaries.
>> This affect only TX direction.
>>
>> Padding is added after ieee80211_hdr, before
Hi Dave,
Here's a (first, even? I didn't have much until before the conference...)
pull request for net-next.
There's nothing out of the ordinary, I think, except that I have an ARM
Tegra patch in here. It's part of an rfkill series and needed to be merged
with those patches, it also has the
Add VHT radiotap parsing support to ieee80211_parse_tx_radiotap().
That capability has been tested using a d-link dir-860l rev b1 running
OpenWrt trunk and mt76 driver
Signed-off-by: Lorenzo Bianconi
---
v2:
- fix mac80211-injection documentation
---
On Fri, 2016-02-19 at 11:01 +0100, Janusz Dziedzic wrote:
> HW/driver should set NEED_ALIGNED4_SKBS flag in case
> require aligned skbs to four-byte boundaries.
> This affect only TX direction.
>
> Padding is added after ieee80211_hdr, before IV/LLC.
I'm still not super happy with how invasive
On Tue, 2016-02-23 at 06:18 -0800, Ben Greear wrote:
> [root@ben-ota2 lanforge]# iw phy wiphy0 info
> Wiphy wiphy0
>
> Band 1:
[...]
> VHT Capabilities (0x338001b2):
> Max MPDU length: 11454
> Supported Channel Width: neither 160
On Wed, 2016-02-17 at 11:47 +0100, Arend van Spriel wrote:
>
> + * @NL80211_ATTR_BSS_SELECT: nested attribute for driver supporting the
> + * BSS selection feature. When used with %NL80211_CMD_GET_WIPHY it contains
> + * NLA_FLAG type according nl80211_bss_select_attr to indicate what
> + *
On Mon, 2016-02-22 at 14:42 -0800, gree...@candelatech.com wrote:
> From: Ben Greear
>
> ath10k supports VHT on 2.4Ghz band.
It can't. At least not formally, as this sentence is written, since VHT
per the spec requires operating on the 5 GHz band, and it also requires
On 02/22/2016 10:49 PM, ako...@qti.qualcomm.com wrote:
From: Anilkumar Kolli
To enable per peer stats feature we are reducing the number of peers.
Firmware has introduced tx stats feature. We have memory limitation in
firmware to add these additional bytes.
Maybe
On 02/23/2016 02:47 AM, Arik Nemtsov wrote:
On Tue, Feb 23, 2016 at 12:42 AM, wrote:
From: Ben Greear
ath10k supports VHT on 2.4Ghz band.
If supplicant and hostapd and radio think
VHT should be allowed, then kernel should let them
try.
Am Dienstag, 23. Februar 2016, 14:17:17 CET schrieb Arnd Bergmann:
> On Tuesday 23 February 2016 11:38:52 Marc Dietrich wrote:
> > Am Dienstag, 23. Februar 2016, 11:31:40 CET schrieb Arnd Bergmann:
> > > On Tuesday 23 February 2016 11:15:31 Arnd Bergmann wrote:
> > > > On Thursday 18 February 2016
>>> Removing supported chainmask fields as it can be always derived
>>> from num_rf_chains.
>>>
>>> Signed-off-by: Rajkumar Manoharan
>>
> Hello,
>
> This one break monitor mode for qca988x and 10.x firmware:
> After Revert "ath10k: remove supported chain mask" - works
From: Xinming Hu
This patch sdio multi port aggregation statistics which can be
used for debugging. This debug data is collected in
/sys/kernel/debug/mwifiex/mlan0/debug.
Signed-off-by: Xinming Hu
Signed-off-by: Cathy Luo
Signed-off-by:
From: Xinming Hu
multiport address flag(0x1000) should not be set during sdio cmd53,
if we have only one packet to read/write.
Signed-off-by: Cathy Luo
Signed-off-by: Xinming Hu
Signed-off-by: Amitkumar Karwar
---
From: Xinming Hu
It is observed that driver may send the data packet to tdls peer
before tdls peer receives tdls setup confirm frame.
Similar race condition exists during tdls teardown procedure also.
This patch adds 10 milliseconds delay to resolve the race.
Signed-off-by:
This patch corrects the error case in association path by returning
-1. Earlier "media_connected" used to remain on in this error case
causing failure for further association attempts.
Signed-off-by: Amitkumar Karwar
Fixes: b887664d882ee4 ('mwifiex: channel switch handling
On Tuesday 23 February 2016 11:38:52 Marc Dietrich wrote:
> Am Dienstag, 23. Februar 2016, 11:31:40 CET schrieb Arnd Bergmann:
> > On Tuesday 23 February 2016 11:15:31 Arnd Bergmann wrote:
> > > On Thursday 18 February 2016 21:04:49 Johannes Berg wrote:
> > > > On Tue, 2016-01-26 at 09:42 +0100,
On Tue, 2016-02-23 at 12:11 +0100, Lorenzo Bianconi wrote:
> Add VHT radiotap parsing support to ieee80211_parse_tx_radiotap().
> That capability has been tested using a d-link dir-860l rev b1
> running OpenWrt trunk and mt76 driver
>
> + VHT rate for the transmission (only for devices without
On Tue, 2016-02-23 at 13:12 +0100, Felix Fietkau wrote:
>
> It's initialized to 0 by default, in which case it does not limit the
> A-MSDU size. The driver does not need to set it, but it really
> should.
Right, but this is problematic as Emmanuel had pointed out, when
scaling down you run into
On 29 October 2015 at 12:01, Kalle Valo wrote:
> Rajkumar Manoharan writes:
>
>> Removing supported chainmask fields as it can be always derived
>> from num_rf_chains.
>>
>> Signed-off-by: Rajkumar Manoharan
>
Hello,
On Thu, 2016-02-18 at 19:39 +0100, Felix Fietkau wrote:
> Requires software tx queueing support. frag_list support (for zero-
> copy)
> is optional.
>
Come to think of it, a commit message that explains what it does and
how it works would be nice :)
johannes
--
To unsubscribe from this list:
This reverts commit 6c2ab2398b88 ("staging: wilc1000: remove spaces around
'->'").
It had applied from a incorrectly commit a1b56a4c5054
("staging: wilc1000: wilc_wfi_cfgoperations.c: removes unnecessary log
messages").
Signed-off-by: Leo Kim
---
This patch removes unnecessary retry 3 times and related variable.
Actually the retry 3 times sentence, don't retry at all.
Repeats conditions are that until read a chip-id and written a register.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/wilc_wlan.c | 7 +++
1
On 2016-02-23 12:25, Johannes Berg wrote:
> On Thu, 2016-02-18 at 19:39 +0100, Felix Fietkau wrote:
>> Requires software tx queueing support. frag_list support (for zero-
>> copy) is optional.
>
> "optional" ;-)
>
>> @@ -1751,6 +1754,7 @@ struct ieee80211_sta {
>> bool mfp;
>> u8
On Thu, 2016-02-18 at 19:39 +0100, Felix Fietkau wrote:
> Requires software tx queueing support. frag_list support (for zero-
> copy) is optional.
"optional" ;-)
> @@ -1751,6 +1754,7 @@ struct ieee80211_sta {
> bool mfp;
> u8 max_amsdu_subframes;
> u16 max_amsdu_len;
> +
Add VHT radiotap parsing support to ieee80211_parse_tx_radiotap().
That capability has been tested using a d-link dir-860l rev b1 running
OpenWrt trunk and mt76 driver
Signed-off-by: Lorenzo Bianconi
---
Documentation/networking/mac80211-injection.txt | 10
On Fri, 2016-02-19 at 17:39 +0100, Cédric Debarge - ACKSYS wrote:
> > What are you working on that you need this?
>
> We are working on critical industrial networks where a specific
> (generally high) bandwidth is required.
> Supressing low MCSs (that are not able to handle the desired
>
On Thu, 2016-02-18 at 13:54 -0800, Ben Greear wrote:
> > Yeah, it does, at least if you assume that the capabilities can
> > actually change. We assume they don't though, hostapd/wpa_s for
> > example will never re-query them after startup.
>
> Restarting supplicant, even if it came to that,
On Tue, 2016-02-23 at 11:49 +0100, Lorenzo Bianconi wrote:
> > On Tue, 2016-02-23 at 11:29 +0100, Lorenzo Bianconi wrote:
> > > I used the previous commit scheme (mac80211: Parse legacy and HT
> > > rate
> > > in injected frames).
> >
> > Oh, I merged something similar there? My mistake.
> >
>
On Tue, Feb 23, 2016 at 12:42 AM, wrote:
>
> From: Ben Greear
>
> ath10k supports VHT on 2.4Ghz band.
> If supplicant and hostapd and radio think
> VHT should be allowed, then kernel should let them
> try.
Removing the 80Mhz check entirely is
On Tue, 2016-02-23 at 11:29 +0100, Lorenzo Bianconi wrote:
> I used the previous commit scheme (mac80211: Parse legacy and HT rate
> in injected frames).
Oh, I merged something similar there? My mistake.
> I will rewrite the documentation. Should I send v3 or a different
> patch?
>
Please
Am Dienstag, 23. Februar 2016, 11:31:40 CET schrieb Arnd Bergmann:
> On Tuesday 23 February 2016 11:15:31 Arnd Bergmann wrote:
> > On Thursday 18 February 2016 21:04:49 Johannes Berg wrote:
> > > On Tue, 2016-01-26 at 09:42 +0100, Johannes Berg wrote:
> > Just for my curiosity: what is the
On Tuesday 23 February 2016 11:15:31 Arnd Bergmann wrote:
> On Thursday 18 February 2016 21:04:49 Johannes Berg wrote:
> > On Tue, 2016-01-26 at 09:42 +0100, Johannes Berg wrote:
> Just for my curiosity: what is the difference between a rfkill-gpio
> device and a gpio-keys device with a
On Fri, 2016-02-19 at 19:03 +0100, Thierry Reding wrote:
> On Thu, Feb 18, 2016 at 09:04:49PM +0100, Johannes Berg wrote:
> > On Tue, 2016-01-26 at 09:42 +0100, Johannes Berg wrote:
> > > On Mon, 2016-01-25 at 13:18 +0100, Thierry Reding wrote:
> > > >
> > > > Johannes, I assume that you'll want
I used the previous commit scheme (mac80211: Parse legacy and HT rate
in injected frames).
I will rewrite the documentation. Should I send v3 or a different patch?
Regards,
Lorenzo
On Tue, Feb 23, 2016 at 11:10 AM, Johannes Berg
wrote:
> On Fri, 2016-02-19 at 11:43
On Fri, 2016-02-19 at 11:43 +0100, Lorenzo Bianconi wrote:
> Add IEEE80211_RADIOTAP_VHT entry to rtap_namespace_sizes array in
> order to
> define alignment and size of VHT info in tx radiotap
>
Applied this though.
johannes
--
To unsubscribe from this list: send the line "unsubscribe
On Thursday 18 February 2016 21:04:49 Johannes Berg wrote:
> On Tue, 2016-01-26 at 09:42 +0100, Johannes Berg wrote:
> > On Mon, 2016-01-25 at 13:18 +0100, Thierry Reding wrote:
> > >
> > > Johannes, I assume that you'll want to take this through your tree
> > > because of the dependency? In
On Wed, 2016-02-17 at 20:30 +0200, Emmanuel Grumbach wrote:
> From: Beni Lev
>
> Today, the supplicant will add the RRM capabilities
> Information Element in the association request only if
> Quiet period is supported (NL80211_FEATURE_QUIET).
>
Applied.
johannes
--
To
On Tue, 2016-02-16 at 16:28 -0500, Avery Pennarun wrote:
> Since around the beginning of time, ath9k aggregates have timed out
> after
> 5000 TU (around 5000ms) of inactivity, but nobody seems to be quite
> sure
> why, and this magic number seems to have migrated around from one
> place to
>
On Fri, 2016-02-19 at 11:43 +0100, Lorenzo Bianconi wrote:
> Add VHT radiotap parsing support to ieee80211_parse_tx_radiotap().
> That capability has been tested using a d-link dir-860l rev b1
> running
> OpenWrt trunk and mt76 driver
>
> Signed-off-by: Lorenzo Bianconi
Both applied.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, 2016-02-19 at 12:18 +0100, Lorenzo Bianconi wrote:
> Fix wiphy supported_band access in tx radiotap parsing introduced
> in commit 5ec3aed9ba4c ("mac80211: Parse legacy and HT rate in
> injected frames"). In particular, info->band is always set to 0
> (IEEE80211_BAND_2GHZ) since it has not
-20160223] [if your patch is applied to the wrong git tree,
please drop us a note to help improving the system]
url:
https://github.com/0day-ci/linux/commits/akolli-qti-qualcomm-com/ath10k-Reduce-number-of-peers-to-support-peer-stats-feature/20160223-145312
base:
https://git.kernel.org/pub/scm
On Mon, 2016-02-08 at 14:25 +0100, Felix Fietkau wrote:
> reuse_skb is set to true if the code decides to use the last segment.
> Fixes a memory leak
>
Applied.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to
On Mon, 2016-02-08 at 14:34 +0100, Felix Fietkau wrote:
> This massively reduces data copying and thus improves rx performance
>
Applied.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo
>
> Hi Janusz,
>
> >
> > Hello,
> >
> > I have intel7260 connected via external PCIe + DELL latitude e6430.
> >
> > [ 5199.805417] iwlwifi :04:00.0: enabling device (0100 -> 0102) [
> > 5199.809222] iwlwifi :04:00.0: loaded firmware version
> > 17.275772.0 op_mode iwlmvm
> > [
Hi Dave,
Unfortunately I neglected to send you a pull request last week,
so it's here now. We gave a number of fairly important fixes
(two found by KASAN, the wext thing that for some reason people
have started seeing issues with) so it'd be good if these can
still go into 4.5.
Let me know if
On Mon, 2016-02-15 at 14:35 +0100, Arend van Spriel wrote:
> When user-space has started a critical protocol session and a
> disconnect
> event occurs, the rdev::crit_prot_nlportid remains set. This caused a
> subsequent NL80211_CMD_CRIT_PROTO_START to fail (-EBUSY). Fix this by
> clearing the
On Thu, 2016-02-11 at 01:00 +0100, Ola Olsson wrote:
> The connection keys are zeroed out in all other cases except this
> one. Let's fix the last one as well.
>
Applied.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to
On Thu, 2016-02-18 at 19:49 +0100, Felix Fietkau wrote:
> The value 5000 was put here with the addition of the timeout field to
> ieee80211_start_tx_ba_session. It was originally added in mac80211 to
> save resources for drivers like iwlwifi, which only supports a
> limited
> number of concurrent
Hi Janusz,
>
> Hello,
>
> I have intel7260 connected via external PCIe + DELL latitude e6430.
>
> [ 5199.805417] iwlwifi :04:00.0: enabling device (0100 -> 0102) [
> 5199.809222] iwlwifi :04:00.0: loaded firmware version
> 17.275772.0 op_mode iwlmvm
> [ 5199.819548] iwlwifi
Hello,
I have intel7260 connected via external PCIe + DELL latitude e6430.
[ 5199.805417] iwlwifi :04:00.0: enabling device (0100 -> 0102)
[ 5199.809222] iwlwifi :04:00.0: loaded firmware version
17.275772.0 op_mode iwlmvm
[ 5199.819548] iwlwifi :04:00.0: Detected Intel(R) Dual Band
75 matches
Mail list logo