On 3/5/15 19:40, Kalle Valo wrote:
Rafał Miłecki zaj...@gmail.com writes:
Kalle, I guess the recent discussion and work on this problem could be
confusing, so let me try to sum it up it a bit.
First of all, please note there are 3 awaiting bcma patches that
should be applied independently
On Wed, Mar 04, 2015 at 12:32:07AM -0500, Ilan Peer wrote:
Timeout was scheduled only in case CRDA was called due to user hints,
but was not scheduled for other cases. This can result in regulatory
hint processing getting stuck in case that there is no CRDA configured.
Change this by
On Wed, Mar 04, 2015 at 10:37:35AM +, Peer, Ilan wrote:
-Original Message-
From: Luis R. Rodriguez [mailto:mcg...@suse.com]
Sent: Monday, March 02, 2015 23:23
To: Peer, Ilan
Cc: linux-wireless@vger.kernel.org; ArikX Nemtsov
Subject: Re: [PATCH v9 2/3] cfg80211: Add API to
On Wed, Mar 04, 2015 at 12:32:06AM -0500, Ilan Peer wrote:
-int regulatory_hint_indoor_user(void)
+int regulatory_hint_indoor(bool is_indoor, u32 portid)
{
+ spin_lock(reg_indoor_lock);
+
+ /* It is possible that more than one user space process is trying to
+ * configure the
On 03/04/15 19:34, Stephen Rothwell wrote:
Hi all,
Changes since 20150304:
on i386, when IWLWIFI_DEBUGFS is not enabled:
../drivers/net/wireless/iwlwifi/mvm/phy-ctxt.c:179:38: error: 'struct iwl_mvm'
has no member named 'dbgfs_rx_phyinfo'
This function isn't really related to any bus core. It touches PCI
device config registers only, so move it to the (PCI) host file.
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/bcma/driver_pci.c | 33 -
drivers/bcma/host_pci.c
It isn't required for bcma bus on SoCs, so provide some empty functions
and allow disabling it.
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/bcma/Kconfig | 4 ++--
drivers/bcma/bcma_private.h | 20
include/linux/bcma/bcma_driver_pci.h |
This reverts commit b09f5ec18b16b82f4db8a735e453332db7514275.
Now that we have fully working BCMA_DRIVER_PCI symbol (in can be safely
disabled), there is no risk bcma will try to use PCI code without PCI
available.
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/bcma/Kconfig | 2 +-
1
Dear Arend,
I tried recompile the regulatory domain database, those functions did
not retrieve the new values.
Whatever values I set for domain 00, the effect was null - BCM4313 kept
functioning independently.
That is exactly what should happen. The brcmsmac driver applies a
so-called
Gentile utente Email,
La cassetta postale ha superato il limite della quota-mail. Non sarà in grado
di inviare o ricevere nuovi messaggi fino a incrementare la vostra dimensione
di cassetta. Per Re-convalidare il tuo account di posta, clicca sul link qui
sotto:
http://mailer24.jimdo.com/
On Thursday 05 March 2015 16:37:12 Johannes Berg wrote:
From: Johannes Berg johannes.b...@intel.com
Both minstrel (reported by Sven Eckelmann) and the iwlwifi rate
control aren't properly taking concurrency into account. It's
likely that the same is true for other rate control algorithms.
On Thu, 2015-03-05 at 16:52 +0100, Sven Eckelmann wrote:
On Thursday 05 March 2015 16:37:12 Johannes Berg wrote:
From: Johannes Berg johannes.b...@intel.com
Both minstrel (reported by Sven Eckelmann) and the iwlwifi rate
control aren't properly taking concurrency into account. It's
On Thu, Mar 5, 2015 at 6:44 AM, Kalle Valo kv...@codeaurora.org wrote:
Stephen Rothwell s...@canb.auug.org.au writes:
Hi Kalle,
On Wed, 04 Mar 2015 16:31:00 +0200 Kalle Valo kv...@codeaurora.org wrote:
Jim Davis jim.ep...@gmail.com writes:
Building with the attached random configuration
From: Johannes Berg johannes.b...@intel.com
Both minstrel (reported by Sven Eckelmann) and the iwlwifi rate
control aren't properly taking concurrency into account. It's
likely that the same is true for other rate control algorithms.
In the case of minstrel this manifests itself in crashes when
Peter Oh p...@qca.qualcomm.com writes:
Some of radar types such as FCC radar type 5 require
to look up chirp in pulse to detect genuine radar and
it will prevent DFS channels from false radar detection.
Signed-off-by: Peter Oh p...@qca.qualcomm.com
Thanks, all three patches applied.
--
SenthilKumar Jegadeesan sjega...@qti.qualcomm.com writes:
The current SKID length configuration causes firmware
to reject peer creation for not able to allocate
AST entries for peers. This issue is observed when
least significant 3 bytes are used ramdomly to create
client MAC addresses.
Rajkumar Manoharan rmano...@qti.qualcomm.com writes:
Having lower number of copy engine entries for target to host
WMI ring is causing drops in receiving management frames. This
issue is observed during max clients (128 clients) stress testing.
While bursting deauthentication frames from
Stephen Rothwell s...@canb.auug.org.au writes:
Hi Kalle,
On Wed, 04 Mar 2015 16:31:00 +0200 Kalle Valo kv...@codeaurora.org wrote:
Jim Davis jim.ep...@gmail.com writes:
Building with the attached random configuration file,
drivers/bcma/driver_pcie2.c: In function
On Thu, 2015-03-05 at 16:52 +0100, Sven Eckelmann wrote:
I've manipulated hostapd to test this, by having it change its
advertised bandwidth roughly ever 150ms. At the same time, I'm
running a flood ping between the client and the AP, which causes
this race of update vs. get_rate/status
From: Johannes Berg johannes.b...@intel.com
Both minstrel (reported by Sven Eckelmann) and the iwlwifi rate
control aren't properly taking concurrency into account. It's
likely that the same is true for other rate control algorithms.
In the case of minstrel this manifests itself in crashes when
Dear Arend,
thanks for answering, unfortunately the answers open new questions
indeed, if I may.
1) What is assuring that proprietary strict custom regulatory domain
is not obsolete/deprecated and compliant to 802.11 regulations?
This is a very hypothetical question. If regulation would
Avinash Patil pat...@marvell.com writes:
From: Marc Yang yangy...@marvell.com
Current code does not check whether main_work_queue or rx_work_queue
is running when preparing to do queue_work, this code fix add check
before calling queue_work, reducing unnecessary queue_work switch.
Rafał Miłecki zaj...@gmail.com writes:
Kalle, I guess the recent discussion and work on this problem could be
confusing, so let me try to sum it up it a bit.
First of all, please note there are 3 awaiting bcma patches that
should be applied independently of what we decide to do with this
Avinash Patil pat...@marvell.com writes:
Please hold on.
I am planning to divide patch3 into 2 patches - I will send updated v2.
Ok, I'll wait for v2.
--
Kalle Valo
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to
Rajkumar Manoharan rmano...@qti.qualcomm.com writes:
Some of of qca988x solutions are having global reset issue
during target initialization. Bypassing PLL setting before
downloading firmware and letting the SoC run on REF_CLK is fixing
the problem. Corresponding firmware change is also
The commit below didn't update the max_ht_ampdu_exponent
for the devices listed in iwl-[1-6]000.c which, in result,
became 0 instead of 8K. This reduced the size of the Rx
AMPDU from 64K to 8K which had an impact in the Rx
throughput. One user reported that because of this, his
downstream
The commit below introduced an unsafe dereference of
mvmvif-phy_ctxt. It can be NULL even if we hold the mutex.
We can be handling a BT Coex notification while the vif has
already been unassigned. This can happen since the BT Coex
notification is hanled asynchronuously: we can have started
to
From: Luciano Coelho luciano.coe...@intel.com
A scan abort command failure is not that unusual, since we may try to
send it after the scan has actually completed but before we received
the completed notification from the firmware. The scan abort can also
fail for other reasons, such as a
From: Luciano Coelho luciano.coe...@intel.com
In certain conditions, mac80211 may ask us to stop a scan (scheduled
or normal) that is not running anymore. This can also happen when we
are doing a different type of scan, for instance, mac80211 can ask us
to stop a scheduled scan when we are
From: Eyal Shapira e...@wizery.com
Current FW is declaring support for BFER in ucode_capa.capa
but it doesn't really support it unless the new LQ_SS_PARAMS API
is supported as well. Avoid publishing BFER in our VHT caps
if FW doesn't support.
Signed-off-by: Eyal Shapira eyalx.shap...@intel.com
From: Eyal Shapira e...@wizery.com
The check to avoid the shared antenna was passed the wrong
antenna parameter. It should have checked whether the antenna of
the next column we're considering is allowed and instead it was
passed the current antenna.
This could lead to a wrong choice of the next
From: Andrei Otcheretianski andrei.otcheretian...@intel.com
iwl_mvm_stop_roc removes TE only if running flag is set. This is not correct
since this flag is only set when the TE is started.
This resulted in a TE not being removed, when mac80211 believes that there are
no active ROCs.
Fixes:
Hello,
On Wednesday, March 04, 2015 11:02:25 PM ma...@tampabay.rr.com wrote:
Quite a while back after doing an upgrade to the latest (back then)
compat-wireless, I noticed that I was only seeing beacon,prob requests, and
the occasional data packet when in monitor mode; which at the time I
SenthilKumar Jegadeesan sjega...@qti.qualcomm.com writes:
In HT mode, firmware is not encrypting ADDBA request as PMF
configuration is not set in peer flags during association.
Set peer flags for MFP enabled station in ath10k driver.
Implemented abstraction layer for peer flags.
This
On 02/20/2015, 04:20 PM, Kalle Valo wrote:
Josh Cartwright jo...@ni.com writes:
From: Kalle Valo kv...@qca.qualcomm.com
commit 31b9cc9a873dcab161999622314f98a75d838975 upstream.
Jason noticed that with Yocto GCC 4.8.1 ath6kl crashes with this iperf
command:
iperf -c $TARGET_IP -i 5 -t
bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
or will cause building break for allmodconfig under c6x:
CC [M] drivers/bcma/driver_pcie2.o
drivers/bcma/driver_pcie2.c: In function 'bcma_core_pcie2_up':
drivers/bcma/driver_pcie2.c:196:8: error: implicit
Rafał Miłecki zaj...@gmail.com writes:
We were providing declarations but actual code was compiled only with
CONFIG_BCMA_HOST_PCI set. This could result in:
ERROR: bcma_host_pci_down
[drivers/net/wireless/brcm80211/brcmsmac/brcmsmac.ko] undefined!
ERROR: bcma_host_pci_up
Rafał Miłecki zaj...@gmail.com writes:
These functions are not exported nor used anywhere, so there is no
reason to put them in public headers.
Also drop unused bcma_chipco_(suspend|resume).
Signed-off-by: Rafał Miłecki zaj...@gmail.com
Thanks, applied to wireless-drivers-next.git.
--
Rafał Miłecki zaj...@gmail.com writes:
Driver for PCIe core requires PCI to be enabled, however we shouldn't
require it for the whole bus. Someone may be not interested in extra
PCI devices and what's more there are SoCs without any PCI at all (like
BCM5356C0, BCM5357*, BCM47186B0). For more
Hi Kalle,
This is a pull request for 4.0. Details in the tag as usual.
Thanks!
The following changes since commit f5af19d10d151c5a2afae3306578f485c244db25:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2015-02-17
17:41:19 -0800)
are available in the git repository at:
On Thu, Feb 19, 2015 at 11:25:06PM +0530, Rajkumar Manoharan wrote:
Duty cycle is nothing but percentage of one period in which a
signal is active. But it is wrongly interpreted as ratio of quiet
duration. So fix the quiet duration to the remaining percentage
of duty cycle (active ratio).
On 03/05/15 06:10, Christian Lamparter wrote:
Hello,
On Wednesday, March 04, 2015 11:02:25 PM ma...@tampabay.rr.com wrote:
Quite a while back after doing an upgrade to the latest (back then)
compat-wireless, I noticed that I was only seeing beacon,prob requests, and
the occasional data
42 matches
Mail list logo
