Re: [PATCH] {nl, cfg, mac}80211: Implement hidden mesh ID

2014-09-08 Thread Yeoh Chun-Yeow
On Mon, Sep 8, 2014 at 9:15 PM, Johannes Berg wrote: > On Mon, 2014-09-08 at 08:24 -0400, Bob Copeland wrote: >> On Mon, Sep 08, 2014 at 02:01:22PM +0800, Chun-Yeow Yeoh via Devel wrote: >> > The hidden mesh ID is use to enhance the security of >> > open mesh and possible secured mesh later on by

Re: pull request: wireless-next 2014-09-08

2014-09-08 Thread David Miller
From: "John W. Linville" Date: Mon, 8 Sep 2014 15:16:31 -0400 > Please pull this batch of updates intended for the 3.18 stream... Pulled into net-next, thanks a lot John. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kerne

Re: [PATCH 2/2] cfg80211: fix processing world regdomain when non modular

2014-09-08 Thread Luis R. Rodriguez
On Mon, Sep 08, 2014 at 11:59:39AM +0200, Helmut Schaa wrote: > Hi, > > On Fri, Sep 5, 2014 at 11:43 PM, Luis R. Rodriguez wrote: > > Yeah this seems to be a corner case of the fact that we deal with > > locking for the last request only through RCU and we only annotate > > that the request was p

[PATCH 2/2] bcma: add support for chipcommon B core

2014-09-08 Thread Hauke Mehrtens
This core is used on BCM4708 to configure the PCIe and USB3 PHYs and it contains the addresses to the Device Management unit. This will be used by the PCIe driver first. Signed-off-by: Hauke Mehrtens --- drivers/bcma/Makefile | 1 + drivers/bcma/bcma_private.h

[PATCH 1/2] bcma: store more alternative addresses

2014-09-08 Thread Hauke Mehrtens
Each core could have more than one alternative address. There are cores with 8 alternative addresses for different functions. The PHY control in the Chip common B core is done through the 2. alternative address and not the first one. Signed-off-by: Hauke Mehrtens CC: linux-...@vger.kernel.org ---

pull request: wireless-next 2014-09-08

2014-09-08 Thread John W. Linville
Dave, Please pull this batch of updates intended for the 3.18 stream... For the mac80211 bits, Johannes says: "Not that much content this time. Some RCU cleanups, crypto performance improvements, and various patches all over, rather than listing them one might as well look into the git log inste

[PATCH 05/12] iwlwifi: increase DEFAULT_MAX_TX_POWER

2014-09-08 Thread Emmanuel Grumbach
From: Eliad Peller The chip is able to transmit up to 22dBm, so set the constant appropriately. CC: [3.13+] Signed-off-by: Eliad Peller Signed-off-by: Emmanuel Grumbach --- drivers/net/wireless/iwlwifi/iwl-config.h| 2 ++ drivers/net/wireless/iwlwifi/iwl-nvm-parse.c | 4 +--- 2 files cha

[PATCH 10/12] iwlwifi: dvm: disable power save by default

2014-09-08 Thread Emmanuel Grumbach
From: Emmanuel Grumbach In https://bugzilla.kernel.org/show_bug.cgi?id=84031, the submitter said that disabling power saving helped, do just that. Signed-off-by: Emmanuel Grumbach --- drivers/net/wireless/iwlwifi/dvm/power.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/d

[PATCH 07/12] iwlwifi: mvm: treat EAPOLs like mgmt frames wrt rate

2014-09-08 Thread Emmanuel Grumbach
From: Eyal Shapira Using the LQ table which is initially set according to the rssi could lead to EAPOLs being sent in high legacy rates like 54mbps. It's better to avoid sending EAPOLs in high rates as it reduces the chances of a successful 4-Way handshake. Avoid this and treat them like other mg

Re: 802.11p rate control

2014-09-08 Thread Felix Fietkau
On 2014-09-08 18:30, Rostislav Lisovy wrote: > The possible obstacles are: > * 802.11p will be used mainly for two independent C2X protocol stacks -- > one is the European ETSI ITS-G5, the other one is the US WAVE (IEEE > 1609). I assume that these two protocol stack implementations will > differ m

[PATCH 08/12] iwlwiwi: mvm: use bss_conf->dtim_period instead of conf.ps_dtim_period

2014-09-08 Thread Emmanuel Grumbach
From: Emmanuel Grumbach The latter is meant for software implementation of power save and is not per-virtual interface. Since our driver supports multiple virtual interfaces, we need to use vif->bss_conf.dtim_period. Signed-off-by: Emmanuel Grumbach --- drivers/net/wireless/iwlwifi/mvm/debugfs

[PATCH 06/12] iwlwifi: mvm: correctly handle PM/QoS changes from mac80211

2014-09-08 Thread Emmanuel Grumbach
From: Johannes Berg When mac80211 requests multiple BSS config changes, as for example while associating, we ignore power management and QoS changes and only apply them later. Fix that by removing the "else" and making the conditions independent. Also move it after (potential) beacon filter enab

[PATCH 03/12] iwlwifi: mvm: set MAC_FILTER_IN_BEACON correctly for STA/P2P client

2014-09-08 Thread Emmanuel Grumbach
From: Luciano Coelho In commit cad3f08c (iwlwifi: mvm: enable MAC_FILTER_IN_BEACON when forced_assoc_off is set) the code to set the MAC_FILTER_IN_BEACON flag was accidentally moved to the main block of the if statement, while it should be in the else block instead. Move it to the right place.

[PATCH 04/12] iwlwifi: mvm: fix endianity issues with Smart Fifo commands

2014-09-08 Thread Emmanuel Grumbach
From: Emmanuel Grumbach This code was broken on big endian systems. Sparse didn't catch the bug since the firmware command was not tagged as little endian. Fix the bug for big endian systems and tag the field in the firmware command to prevent such issues in the future. Cc: sta...@vger.kernel.or

[PATCH 09/12] iwlwifi: mvm: BT Coex - always initialize smps_mode

2014-09-08 Thread Emmanuel Grumbach
From: Johannes Berg smps_mode is used uninitialized in a debug statement in AP mode, so always initialize it. While at it, fix a typo. Signed-off-by: Johannes Berg Reviewed-by: Luciano Coelho Signed-off-by: Emmanuel Grumbach --- drivers/net/wireless/iwlwifi/mvm/coex.c | 7 +++ 1 file ch

[PATCH 11/12] iwlwifi: add PCI IDs and add then new 3165 series

2014-09-08 Thread Emmanuel Grumbach
From: Oren Givon This change does the following: 1) Add a new 7265 series PCI ID 2) Add two new 3160 series PCI IDs 3) Add the new 3165 series PCI IDs and configurations Signed-off-by: Oren Givon Signed-off-by: Emmanuel Grumbach --- drivers/net/wireless/iwlwifi/iwl-7000.c | 16 +

[PATCH 12/12] iwlwifi: mvm: fix an overflow in iwl_mvm_get_signal_strength

2014-09-08 Thread Emmanuel Grumbach
From: Eyal Shapira The idea here is to translate a value of 0 received from the firmware to the lowest rssi figure. As rx_status->chain_signal is a signed byte the lowest possible value is -128 and not -256. -256 was causing 0 to get stored in the signed byte. Signed-off-by: Eyal Shapira Review

[PATCH 02/12] iwlwifi: mvm: BT Coex - remove shadowing variable

2014-09-08 Thread Emmanuel Grumbach
From: Johannes Berg The variable 'u32 mode' exists twice, the latter shadowing the former - remove the latter since there's no need for two variables. Signed-off-by: Johannes Berg Signed-off-by: Emmanuel Grumbach --- drivers/net/wireless/iwlwifi/mvm/coex.c | 2 -- 1 file changed, 2 deletions(

[PATCH 01/12] iwlwifi: mvm: enable scheduled scan on newest firmware

2014-09-08 Thread Emmanuel Grumbach
From: Emmanuel Grumbach Scheduled scan was disabled because of a bug in the firmware. The firmware reported support for this feature, but enabling it led to assertions. The bugs have been fixes in latest firmware versions, so that we can re-enable the feature on latest firmwares only. Signed-off

pull request: iwlwifi 2014-09-08

2014-09-08 Thread Emmanuel Grumbach
Hi John, I think I have caught up completely now - and because I had quite a bit to cover this pull request is rather big for an -rc5. Sorry about that. I re-enable scheduled scan on firmware that contain the fix for the bug that Linus reported. A few trivial fixes: endianity issues, the same D

Re: [PATCH 1/2] mac80211: Unify rate statistic variables between Minstrel & Minstrel_HT

2014-09-08 Thread Felix Fietkau
On 2014-08-22 16:05, Thomas Huehn wrote: > Minstrel and Mintrel_HT use individual structs to keep track of rate > statistics. Unify those variables in struct minstrel_rate_stats and > move it to rc80211_minstrel.h for common usage. This is a clean-up > patch to prepare Minstrel and Minstrel_HT code

802.11p rate control

2014-09-08 Thread Rostislav Lisovy
Dear 802.11 experts; Short introduction before the actual question: Some of you have probably noticed my effort of bringing the 802.11p support for the mainline Linux kernel. (Side note: I know that "802.11p" is already part of the IEEE 802.11-2012 but calling it ".11p" makes it easier to determine

Re: [PATCH 2/2] mac80211: improve minstrel_ht rate sorting by throughput & probability

2014-09-08 Thread Felix Fietkau
On 2014-08-22 16:05, Thomas Huehn wrote: > This patch improves the way minstrel_ht sorts rates according to throughput > and success probability. 3 FOR-loops across the entire rate and mcs group set > in function minstrel_ht_update_stats() which where used to determine the > fastest, second fastest

pull-request: mac80211 2014-09-08

2014-09-08 Thread Johannes Berg
Hi John, One more for mac80211, hopefully that should be it. If anyone thinks I missed anything please holler. I'll have one more for mac80211-next later this week. Note I'm going to be on vacation soon (EOW) until early October, so if anything super urgent shows up I'd appreciate if you could me

Re: [PATCH] {nl, cfg, mac}80211: Implement hidden mesh ID

2014-09-08 Thread Johannes Berg
On Mon, 2014-09-08 at 08:24 -0400, Bob Copeland wrote: > On Mon, Sep 08, 2014 at 02:01:22PM +0800, Chun-Yeow Yeoh via Devel wrote: > > The hidden mesh ID is use to enhance the security of > > open mesh and possible secured mesh later on by not > > advertising the mesh ID during beacon generation, >

Re: wmediumd performance penalty

2014-09-08 Thread Bob Copeland
On Sat, Sep 06, 2014 at 10:17:34AM +0200, Dani Camps wrote: > Hi Bob, > > Our use case is that we have some research code implemented on mac80211, > and we want to test it over a virtual testbed with wmediumd before going on > real hw. Being able to have realistic radio capacities would help us in

Re: [PATCH] {nl, cfg, mac}80211: Implement hidden mesh ID

2014-09-08 Thread Yeoh Chun-Yeow
On Mon, Sep 8, 2014 at 8:24 PM, Bob Copeland wrote: > On Mon, Sep 08, 2014 at 02:01:22PM +0800, Chun-Yeow Yeoh via Devel wrote: >> The hidden mesh ID is use to enhance the security of >> open mesh and possible secured mesh later on by not >> advertising the mesh ID during beacon generation, >> sim

Re: [PATCH] {nl, cfg, mac}80211: Implement hidden mesh ID

2014-09-08 Thread Bob Copeland
On Mon, Sep 08, 2014 at 02:01:22PM +0800, Chun-Yeow Yeoh via Devel wrote: > The hidden mesh ID is use to enhance the security of > open mesh and possible secured mesh later on by not > advertising the mesh ID during beacon generation, > similar to hidden SSID implemented in AP mode. I'm unconvince

Re: ath9k and AMD IOMMU alias breakage on 3.16?

2014-09-08 Thread Joerg Roedel
On Fri, Sep 05, 2014 at 10:01:44PM -0600, Alex Williamson wrote: > On Fri, 2014-09-05 at 20:00 -0700, Jason Newton wrote: > > Hi, > > > > I have an AR9462 connected over minipcie, it came with the ASRock > > FM2A88x-itx motherboard and I'm using an AMD A10-7850K cpu with it. When I > > have IOMMU

Re: [PATCH 2/2] cfg80211: fix processing world regdomain when non modular

2014-09-08 Thread Helmut Schaa
Hi, On Fri, Sep 5, 2014 at 11:43 PM, Luis R. Rodriguez wrote: > Yeah this seems to be a corner case of the fact that we deal with > locking for the last request only through RCU and we only annotate > that the request was processed but don't add checks for when its > about to be processed. At lea

[PATCH] mac80211: annotate MMIC head/tailroom warning

2014-09-08 Thread Johannes Berg
From: Johannes Berg This message occasionally triggers for some people as in https://bugzilla.redhat.com/show_bug.cgi?id=740 but it's not clear which (headroom or tailroom) is at fault. Annotate the message a bit to get more information. Signed-off-by: Johannes Berg --- net/mac80211/wpa.c

Re: Broadcom Wi-Fi/Bluetooth on GPIO? (Baytrail tablet)

2014-09-08 Thread Arend van Spriel
On 09/05/14 10:06, Rafał Miłecki wrote: On 5 September 2014 00:39, Bastien Nocera wrote: On this tablet, based on a Baytrail SoC, I found reference of this Broadcom device in the DSDT, and I believe it could be the Bluetooth/Wi-Fi chipset (this one[1]?): ---8<--- Device (BRC3) { Name (_ADR

Re: [PATCH v6 2/2] mac80211: support DTPC IE (from Cisco Client eXtensions)

2014-09-08 Thread Johannes Berg
On Wed, 2014-09-03 at 06:48 -0700, Steinar H. Gunderson wrote: > Linux already supports 802.11h, where the access point can tell the > client to reduce its transmission power. However, 802.11h is only > defined for 5 GHz, where the need for this is much smaller than on > 2.4 GHz. > > Cisco has the

Re: [RFC v2] device coredump: add new device coredump class

2014-09-08 Thread Johannes Berg
On Fri, 2014-09-05 at 15:13 -0700, Greg Kroah-Hartman wrote: > > + /* > > +* this seems racy, but I don't see a notifier or such on > > +* a struct device to know when it goes away? > > +*/ > > + if (devcd->failing_dev->kobj.sd) > > + sysfs_delete_link(&devcd->failing_dev

Re: [RFC v2] device coredump: add new device coredump class

2014-09-08 Thread Arend van Spriel
On 09/05/14 10:50, Johannes Berg wrote: From: Johannes Berg Many devices run firmware and/or complex hardware, and most of that can have bugs. When it misbehaves, however, it is often much harder to debug than software running on the host. Introduce a "device coredump" mechanism to allow dumpin