A new release of wireless-regdb (master-2015-01-30) is available at:
https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2015.01.30.tar.gz
Note that this is the first release signed with my key. As of yet there
is no release of CRDA which by default trusts a regulatory.bin
On 01/30/2015 03:57 AM, Marcel Holtmann wrote:
Marcel,
Hi Kalle,
I'm adding bluetooth list to the discussion. Full patch is available
here:
https://patchwork.kernel.org/patch/5712591/
Larry Finger larry.fin...@lwfinger.net writes:
From: Troy Tan troy_...@realsil.com.cn
This patch adds
On 01/27/2015 12:49 AM, Priit Laes wrote:
Signed-off-by: Priit Laes pl...@plaes.org
---
drivers/net/wireless/rtlwifi/core.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/net/wireless/rtlwifi/core.h
b/drivers/net/wireless/rtlwifi/core.h
index 624e1dc..3b37557 100644
---
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/bcma/bcma_private.h| 3 +++
drivers/bcma/driver_pcie2.c| 24 ++--
drivers/bcma/host_pci.c| 2 +-
include/linux/bcma/bcma_driver_pcie2.h | 2 ++
4 files changed, 28
It doesn't operate on PCI core, but PCI host device, so there is no
point of passing core related struct.
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/bcma/driver_pci.c | 6 +++---
drivers/net/wireless/b43/main.c| 2 +-
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/bcma/bcma_private.h | 1 +
drivers/bcma/host_pci.c | 15 ++-
drivers/bcma/main.c | 2 +-
3 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/drivers/bcma/bcma_private.h b/drivers/bcma/bcma_private.h
Bringing PCIe hosted bus up requires operating on host-related core.
Since we plan to support PCIe Gen 2 devices we should provide a helper
picking the correct one (PCIE or PCIE2).
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/bcma/bcma_private.h| 2 ++
On Friday, January 30, 2015 10:40 PM, Arend van Spriel wrote:
I'm running kernel 3.18.4, my brcmfmac43241b4-sdio.bin is identical to
the one in the linux-firmware repository, and I have attached the
brcmfmac43241b4-sdio.txt that I have extracted from the EFI variables.
When you say your
On 01/30/2015 06:22 PM, Rafał Miłecki wrote:
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/bcma/bcma_private.h| 3 +++
drivers/bcma/driver_pcie2.c| 24 ++--
drivers/bcma/host_pci.c| 2 +-
Hi,
On 01/27/2015 11:37 PM, Johannes Berg wrote:
On Tue, 2015-01-27 at 21:39 -0800, Peter Oh wrote:
Ok, sure, but I/O ordering two different writes, and ensuring device
has seen a posted write, are related but different things, no?
yes, they are different and wmb guarantees both.
No, wmb()
On 30 January 2015 at 20:59, Hauke Mehrtens ha...@hauke-m.de wrote:
On 01/30/2015 06:22 PM, Rafał Miłecki wrote:
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
drivers/bcma/bcma_private.h| 3 +++
drivers/bcma/driver_pcie2.c| 24 ++--
On 01/26/15 21:44, Arend van Spriel wrote:
Hi Hauke,
The commit below causes the error mentioned in the Subject: field. I
would like to fix this, but could use a bit of help here how to do this
type of things.
commit 4b681c82d2f9bef121c912ffcaac89a004af3f2c
Author: Vadim Kochan
On 01/30/2015 07:18 PM, Arend van Spriel wrote:
On 01/26/15 21:44, Arend van Spriel wrote:
Hi Hauke,
The commit below causes the error mentioned in the Subject: field. I
would like to fix this, but could use a bit of help here how to do this
type of things.
commit
From: Johannes Berg johannes.b...@intel.com
The current wireless tree changes the surrounding code to
use the exported string constants, so adjust the patch to
make it apply again.
Signed-off-by: Johannes Berg johannes.b...@intel.com
---
Hi Larry,
I'm adding bluetooth list to the discussion. Full patch is available
here:
https://patchwork.kernel.org/patch/5712591/
snip
So the wireless driver communicates with the bluetooth driver (which is
not in upstream) via a localhost UDP connection?
I think the first order of
Good Day am Dr. Raymond Atu I have very important issue to discuss
with you Please kindly get back to me urgently .E-mail :
raymon...@hotmail.com raymno...@gmail.com
== =
Disclosure: This e-mail is intended only for the above
A new release of CRDA has been released, this might be the last since
we have some ideas of how to just shift this functionality directly
into the kernel and in the future may not need any userspace tool
other than to help debug stuff perhaps. The major thing here is
trusting Seth's new key as he
On 01/30/15 19:32, Hauke Mehrtens wrote:
Or we just backport this version every time:
struct net *get_net_ns_by_fd(int fd)
{
return ERR_PTR(-EINVAL);
}
I was going for the easy way out over here. Either way is fine by me,
but is net namespace support can not be properly backported I
On Fri, 2015-01-30 at 18:35 +0100, Johannes Berg wrote:
From: Johannes Berg johannes.b...@intel.com
The current wireless tree changes the surrounding code to
use the exported string constants, so adjust the patch to
make it apply again.
Wrong list, and Arend sent the same patch already
On Fri, 2015-01-30 at 19:38 +0100, Arend van Spriel wrote:
On 01/30/15 19:32, Hauke Mehrtens wrote:
Or we just backport this version every time:
struct net *get_net_ns_by_fd(int fd)
{
return ERR_PTR(-EINVAL);
}
I was going for the easy way out over here. Either way is fine by
Hello,
since upgrading to 3.19-rc6-wl (3.19-rc5-wl is working fine). I can no
longer use the IWL 3160 in my laptop. As soon as the link goes up (the
modules load fine, just ip/ifconfig up), I get this:
[5.960381] iwlwifi :01:00.0: L1 Enabled - LTR Disabled
[5.960722] iwlwifi
On Fri, 2015-01-30 at 21:23 +0100, Christian Lamparter wrote:
[6.274625] iwlwifi :01:00.0: 0x0038 | BAD_COMMAND
[6.275034] iwlwifi :01:00.0: FW error in SYNC CMD SCD_QUEUE_CFG
WTF. How did the firmware even announce support for this command??
Perhaps I missed it in the
On 01/30/2015 05:16 PM, Sujith Manoharan wrote:
Peter Oh wrote:
As I addressed wmb uses dsb (in arm arch) and here is the description of
arm architecture.
What about other architectures ?
Please refer the email thread that I mentioned about other architectures.
(dsb is for ARM and other
Using ioread() to perform draining write buffer is excessive.
Use compact API, mb(), that intended to be used for the case.
It reduces total 14 CPU clocks per interrupt.
Signed-off-by: Peter Oh p...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath10k/pci.c | 12
1 file changed, 4
Peter Oh wrote:
Please refer the email thread that I mentioned about other architectures.
(dsb is for ARM and other platforms have the equivalent instruction such
as sfence, sync, mf, and dcs).
Ok.
Also the patch is updated with 2nd patch set replacing wmb to mb.
Would be good to test this
Peter Oh wrote:
As I addressed wmb uses dsb (in arm arch) and here is the description of
arm architecture.
What about other architectures ?
Sujith
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to majord...@vger.kernel.org
More majordomo
Salutem
Is the combination with Bluetooth only essential difference between RTL8821AE
and RTL8812AE?
*If* the undermentioned two devices are based on RTL8812AE chipset,
whether they supported via 'rtl8821ae.ko' 'rtl8821aefw.bin'?
PCIe RTL8812AE 802.11abgn+ac 2x2:2
Amped Wireless PCI20E
On 30 January 2015 at 14:31, Johannes Berg johan...@sipsolutions.net wrote:
On Fri, 2015-01-30 at 14:22 +0100, Michal Kazior wrote:
You'd probably have to add quite a few mutex_lock(iflist_mtx) around
drv_*() calls (not directly but somewhere at their call trees) to
guarantee driver can use
On 30 January 2015 at 14:10, Johannes Berg johan...@sipsolutions.net wrote:
On Fri, 2015-01-30 at 14:06 +0100, Michal Kazior wrote:
I'm a bit reluctant to freely use mac80211 owned structures out of
mac80211_ops callback context, i.e. from a tasklet fearing
inconsistencies. Or am I worrying
On Fri, 2015-01-30 at 15:01 +0100, Michal Kazior wrote:
With `width` you'll change `center_freq1` in many cases. Reading a
pair of old-and-new of each may not necessarily be fatal but may
introduce subtle bugs that are hard to debug. Even if the current code
doesn't really use these values
On Fri, 2015-01-30 at 14:47 +0100, Arend van Spriel wrote:
Indeed and that is what we would like to address in our wireless
drivers. I will setup some experiments using the fraction sizing and
post my findings. Again sorry if I offended you.
You did not, but I had no feedback about my
On Fri, 2015-01-30 at 14:39 +0100, Michal Kazior wrote:
I've briefly tried playing with this knob to no avail unfortunately. I
tried 256K, 1M - it didn't improve TCP performance. When I tried to
make it smaller (e.g. 16K) the traffic dropped even more so it does
have an effect. It seems
On Fri, 2015-01-30 at 14:47 +0100, Michal Kazior wrote:
I'm not sure if you refer to iwlwifi or mac80211 now? If it's the
latter: even if you have an ops with, e.g. vif pointer, driver may
still need to iterate over interfaces in order to propagate some
side-effect changes or aggregate some
On 01/28/15 08:15, Sébastien Bourdeauducq wrote:
Hi,
The Lenovo Thinkpad Tablet 10 is a complete disaster under Linux, and
among many problems the SDIO brcmfmac wifi does not work.
I get the following messages in the kernel log:
brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength
On Fri, Jan 23, 2015 at 01:51:58PM +0200, Jouni Malinen wrote:
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
Applied all three (this one plus Samoa and Tanzania), thanks.
--
To unsubscribe from this list: send the line unsubscribe
Fellow netheads:
Yours truly posting on behalf of rgb.
The preliminary schedule was published late yesterday.
https://www.netdev01.org/schedule
We wanted to get something out quickly while we make it pretty
afterwards. There will be some minor changes later on.
Talks are all on Mon/Tuesday and
Hi,
I'm adding bluetooth list to the discussion. Full patch is available
here:
https://patchwork.kernel.org/patch/5712591/
Larry Finger larry.fin...@lwfinger.net writes:
From: Troy Tan troy_...@realsil.com.cn
This patch adds the routines used to communicate between the RTL8812AE (wifi)
From: Yuwei Zheng yuweizh...@139.com
In the environment with heavy wifi traffic, set the ar9271 into monitor mode,
will
trigger a deadloop panic.
The ath9k_hif_usb_rx_cb function excute on the interrupt context, and
ath9k_rx_tasklet excute
on the soft irq context. In other words, the
On Fri, 2015-01-30 at 10:42 +0100, Helmut Schaa wrote:
diff --git a/event.c b/event.c
[]
@@ -565,6 +565,31 @@ static int print_event(struct nl_msg *msg, void *arg)
nla_data(tb[NL80211_ATTR_VENDOR_DATA]),
Hi Kalle,
I'm adding bluetooth list to the discussion. Full patch is available
here:
https://patchwork.kernel.org/patch/5712591/
Larry Finger larry.fin...@lwfinger.net writes:
From: Troy Tan troy_...@realsil.com.cn
This patch adds the routines used to communicate between the
Sorry, the patch ruined by the mail editor, I will send the patch with another
mail account witch support smtp.
I use tasklet_hrtimer_start for delayed submit, and the hrtimer callback
function is excuted in the lower priority than normal tasklet. (TASKLET_SOFTIRQ
5, HRTIMER_SOFTIRQ 7 )
The
On Fri, 2015-01-30 at 09:17 +0100, Rafał Miłecki wrote:
In hostapd, there is a routine that monitors such netlink messages,
process_global_event, which eventually parses the CMD_DEL_STATION event in
nl80211_del_station_event, where a call is made to drv_event_disassoc if the
current
Signed-off-by: Helmut Schaa helmut.sc...@googlemail.com
---
event.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/event.c b/event.c
index c175c66..71ab7f7 100644
--- a/event.c
+++ b/event.c
@@ -565,6 +565,31 @@ static int print_event(struct nl_msg *msg, void *arg)
This processes and pushes fw stats to the debug
module (if enabled).
Changing the generic ath10k_wmi_requests_stats()
call to use more stat bits has no effect on older
firmware binaries.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/debug.c | 5 +-
New qca6174 wmi-tlv firmware revisions support
more stat event bits.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/debug.c | 2 +-
drivers/net/wireless/ath/ath10k/wmi.h | 10 +++---
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git
New qca6174 wmi-tlv firmware supports vdev stats.
This patch adds support for it in the debug
frontend.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/core.h | 20 +++
drivers/net/wireless/ath/ath10k/debug.c | 96 +
2
The expected parameter is not a single value but a
mask of values.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/wmi-ops.h | 7 +++
drivers/net/wireless/ath/ath10k/wmi-tlv.c | 5 ++---
drivers/net/wireless/ath/ath10k/wmi.c | 7 ---
3 files
There are some slight differences in fw stats
(sic) in wmi-tlv.
Firmware has changed the querying scheme and no
longer requires the ping-pong to get all stats.
The patchset doesn't change this behaviour so with
wmi-tlv it's possible to see the following
warnings when reading fw stats:
If firmware advertises support for TxBF then the
driver has to instruct the firmware accordingly
during runtime. Without this patch connecting to
an AP with beamformer support would yield abysmal
Rx performance.
This has been tested with wmi-tlv and qca6174
while acting as a STA beamformee only.
On 01/29/15 14:14, Eric Dumazet wrote:
On Thu, 2015-01-29 at 12:48 +0100, Michal Kazior wrote:
Hi,
I'm not subscribed to netdev list and I can't find the message-id so I
can't reply directly to the original thread `BW regression after tcp:
refine TSO autosizing`.
I've noticed a big TCP
On 30 January 2015 at 09:41, Michal Kazior michal.kaz...@tieto.com wrote:
The chanctx API will allow ath10k to support
multi-channel operation.
[...]
Oh snap. I just rebased to latest master and Yanbo's patch for 2G VHT
makes this patch null deref on assoc. I'll respin a v2 later.
Michał
--
On Fri, 2015-01-30 at 07:15 +0100, Rafał Miłecki wrote:
On 29 January 2015 at 15:58, Johannes Berg johan...@sipsolutions.net wrote:
Obviously, another consequence is that the wiki markup will change
somewhat. Moin and Mediawiki aren't too far from each other (except for
table syntax), but
On Fri, 2015-01-30 at 07:19 +0100, Rafał Miłecki wrote:
On 29 January 2015 at 15:58, Johannes Berg johan...@sipsolutions.net wrote:
It's actually at http://linuxwireless.sipsolutions.net/ and is just a
static dump of the old wiki contents. Please don't copy content I
removed from the new
Memory is leaked after downloading already processed packet. This
patch fixes the problem by freeing returned skb. Other transmit
paths don't have this problem.
Signed-off-by: Amitkumar Karwar akar...@marvell.com
Signed-off-by: Cathy Luo c...@marvell.com
---
drivers/net/wireless/mwifiex/wmm.c |
Wakeup timer is in sync with 'pm_wakeup_fw_try' flag. It
has been started instead of cancelling at one place. This
patch corrects it.
Signed-off-by: Amitkumar Karwar akar...@marvell.com
Signed-off-by: Cathy Luo c...@marvell.com
---
drivers/net/wireless/mwifiex/sta_event.c | 3 +--
1 file
When AP is started, firmware exits power save mode. This
means power save manager of AP takes priority over station.
Firmware stop sending periodic AWAKE events to host.
We may have UAPSD enabled on station which buffers data
packets until AWAKE event from firmware. Data path is
unnecessarily
qca6174 wmi-tlv firmware defines a new wmi event
for host tx pausing (i.e. stop/wake tx queues).
Map these events to ath10k/mac80211 tx queue
control.
This is important for multi-channel thourghput
performance.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
New qca6174 with wmi-tlv firmware supports
multi-channel operation. To make use of it
ath10k needs a few changes: implement mac80211's
chanctx API and rework tx queue control a bit.
There are still rough edges (involving seldom
beacon reports from firmware causing beacon loss
in some cases, etc).
The chanctx API will allow ath10k to support
multi-channel operation.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/core.c | 1 +
drivers/net/wireless/ath/ath10k/core.h | 8 +
drivers/net/wireless/ath/ath10k/htt_rx.c | 87 -
This patch makes sure that skb is freed after downloading
NULL packet in error cases. Also, USB chipsets return
-EINPROGRESS after downloading packets, they are freed in
USB completion handler later. We will add missing change
to set tx_lock_flag for USB which blocks further packets.
Tx queue locking was very simple until now.
Multi-channel support will require a more flexible
and fine grained control.
This introduces a per-hw and per-vif (each with a
bitmask of reasons) tx queue locking.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
This effectively enables multi-channel operation
on qca6174 WLAN.RM.2.0-00073 (and possibly any
newer firmware release for qca6174).
This adds appopriate interface combinations and
initializes firmware channel scheduler.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
It doesn't make much sense to reject a valid
firmware configuration combination.
Since SSID isn't known early on it might make
sense to allow driver to start vdev without SSID
and restart it later.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
This command will be used to configure
multi-channel scheduler in firmware.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/wmi-ops.h | 16
drivers/net/wireless/ath/ath10k/wmi-tlv.c | 30 ++
This will make it possible to iterate over
interface list while in an atomic context,
i.e. tasklet.
Caller should still be careful with accessing
arvif structures though.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/mac.c | 8
1 file changed,
yuweizh...@139.com writes:
From: Yuwei Zheng yuweizh...@139.com
In the environment with heavy wifi traffic, set the ar9271 into
monitor mode, will trigger a deadloop panic.
The ath9k_hif_usb_rx_cb function excute on the interrupt context, and
ath9k_rx_tasklet excute
on the soft irq
On Fri, 2015-01-30 at 13:31 +0100, Michal Kazior wrote:
+ INIT_LIST_HEAD(ar-arctxs);
INIT_LIST_HEAD(ar-arvifs);
I'm not sure why you have an interface list, but I'd say you don't need
either since you have enumeration APIs:
ieee80211_iterate_active_interfaces[_atomic,...]
and
On Fri, 2015-01-30 at 14:02 +0100, Michal Kazior wrote:
I recall that at least there's one case where using these helpers is
impossible: drv_config() which can be called while mac80211 is already
holding iflist_mtx. ath10k needs to iterate over vifs and issue
blocking commands sometimes so it
From: Sujith Manoharan c_man...@qca.qualcomm.com
ath9k patches for -next.
Sujith Manoharan (17):
ath9k: Remove ATH9K_HW_WOW_DEVICE_CAPABLE
ath9k: Return early for error conditions
ath9k: Remove redundant device_can_wakeup() check
ath9k: Check early for multi-vif/STA conditions
ath9k:
From: Sujith Manoharan c_man...@qca.qualcomm.com
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/ar9003_wow.c | 1 +
drivers/net/wireless/ath/ath9k/reg.h| 120
drivers/net/wireless/ath/ath9k/reg_wow.h| 136
From: Sujith Manoharan c_man...@qca.qualcomm.com
WOW capability is registered with mac80211 only when
the device has the ability to wakeup, so there is no
need to check in the suspend() routine.
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/wow.c |
From: Sujith Manoharan c_man...@qca.qualcomm.com
Registering the card as a wakeup source needs to
be done once, during initialization. When the WOW
configuration changes, the card's status as wakeup
source needs to be changed too and this is done
via the set_wakeup() callback. Also, make sure
the
From: Sujith Manoharan c_man...@qca.qualcomm.com
There is no need to allocate a new structure and
free it for every user pattern, instead use local
variables.
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/ath9k.h | 6 -
From: Sujith Manoharan c_man...@qca.qualcomm.com
Since the number of patterns that can be configured in
the HW is higher for newer chips, store the chip-specific
value in ath9k_hw_wow.
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/hw.c | 7 +++
From: Sujith Manoharan c_man...@qca.qualcomm.com
* Remove unnecessary comments.
* Remove unused macros.
* Indent the macros.
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/reg_wow.h | 68 +++-
1 file changed, 15
From: Sujith Manoharan c_man...@qca.qualcomm.com
This can be used to force WOW for cards that
are not present in the supported PCI ID list.
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/ath9k.h | 1 +
drivers/net/wireless/ath/ath9k/debug.c | 68
From: Sujith Manoharan c_man...@qca.qualcomm.com
If CONFIG_ATH9K_CHANNEL_CONTEXT is enabled, check whether
multiple contexts are active and if so, return 1 without
enabling WOW since we don't support it in this case.
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
From: Sujith Manoharan c_man...@qca.qualcomm.com
If multiple interfaces are active or there is no
associated station interface, bail out early and
return 1 so that mac80211 can proceed with the normal
suspend routine.
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
From: Sujith Manoharan c_man...@qca.qualcomm.com
This can be used to hold the WOW state in
ath9k_hw.
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/ar9003_wow.c | 10 +-
drivers/net/wireless/ath/ath9k/hw.h | 6 +-
2 files
+++ b/drivers/net/wireless/ath/ath10k/core.h
@@ -277,6 +282,7 @@ struct ath10k_vif {
dma_addr_t beacon_paddr;
struct ath10k *ar;
+ struct ath10k_chanctx *arctx;
you also have vif-chanctx_conf pointer, which you could use
ultimately it's a software architecture decision
On 30 January 2015 at 13:45, Johannes Berg johan...@sipsolutions.net wrote:
On Fri, 2015-01-30 at 13:31 +0100, Michal Kazior wrote:
+ INIT_LIST_HEAD(ar-arctxs);
INIT_LIST_HEAD(ar-arvifs);
I'm not sure why you have an interface list, but I'd say you don't need
either since you have
On 30 January 2015 at 13:58, Johannes Berg johan...@sipsolutions.net wrote:
+++ b/drivers/net/wireless/ath/ath10k/core.h
@@ -277,6 +282,7 @@ struct ath10k_vif {
dma_addr_t beacon_paddr;
struct ath10k *ar;
+ struct ath10k_chanctx *arctx;
you also have vif-chanctx_conf
On Fri, 2015-01-30 at 14:06 +0100, Michal Kazior wrote:
I'm a bit reluctant to freely use mac80211 owned structures out of
mac80211_ops callback context, i.e. from a tasklet fearing
inconsistencies. Or am I worrying unnecessarily? If so I guess I'll
redo this and use mac80211's structures
On 30 January 2015 at 14:04, Johannes Berg johan...@sipsolutions.net wrote:
On Fri, 2015-01-30 at 14:02 +0100, Michal Kazior wrote:
I recall that at least there's one case where using these helpers is
impossible: drv_config() which can be called while mac80211 is already
holding iflist_mtx.
On Fri, 2015-01-30 at 14:22 +0100, Michal Kazior wrote:
You'd probably have to add quite a few mutex_lock(iflist_mtx) around
drv_*() calls (not directly but somewhere at their call trees) to
guarantee driver can use lock-free iterate() version (which doesn't
exist yet). This could be tricky.
From: Sujith Manoharan c_man...@qca.qualcomm.com
The various variables tracking bmiss interrupts
are not really used anywhere except in a debug
message. Remove them since they have no functional
purpose.
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
From: Sujith Manoharan c_man...@qca.qualcomm.com
Printing the value of the wakeup status is sufficient.
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/ar9003_wow.c | 15 ---
drivers/net/wireless/ath/ath9k/hw.h | 5 -
Am 29.01.2015 um 00:14 schrieb yuweizh...@139.com:
From: Yuwei Zheng yuweizh...@139.com
In the environment with heavy wifi traffic, set the ar9271 into monitor mode,
will
trigger a deadloop panic.
The ath9k_hif_usb_rx_cb function excute on the interrupt context, and
ath9k_rx_tasklet
The chanctx API will allow ath10k to support
multi-channel operation.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
Notes:
v2:
* prevent null deref in ath10k_peer_assoc_h_vht()
after rebasing to latest master branch
drivers/net/wireless/ath/ath10k/core.c | 1 +
Tx queue locking was very simple until now.
Multi-channel support will require a more flexible
and fine grained control.
This introduces a per-hw and per-vif (each with a
bitmask of reasons) tx queue locking.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
This effectively enables multi-channel operation
on qca6174 WLAN.RM.2.0-00073 (and possibly any
newer firmware release for qca6174).
This adds appopriate interface combinations and
initializes firmware channel scheduler.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
It doesn't make much sense to reject a valid
firmware configuration combination.
Since SSID isn't known early on it might make
sense to allow driver to start vdev without SSID
and restart it later.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
New qca6174 with wmi-tlv firmware supports
multi-channel operation. To make use of it
ath10k needs a few changes: implement mac80211's
chanctx API and rework tx queue control a bit.
There are still rough edges (involving seldom
beacon reports from firmware causing beacon loss
in some cases, etc).
93 matches
Mail list logo
