On Tue, Oct 21, 2014 at 12:06 PM, Krishna Chaitanya
chaitanya.m...@gmail.com wrote:
On Tue, Oct 21, 2014 at 11:01 AM, Emmanuel Grumbach egrumb...@gmail.com
wrote:
On Tue, Oct 21, 2014 at 8:02 AM, Emmanuel Grumbach egrumb...@gmail.com
wrote:
On Mon, Oct 20, 2014 at 10:29 PM, Laurențiu Nicola
Kalle Valo kv...@qca.qualcomm.com writes:
All warning and error messages should end with '\n', fix that.
Signed-off-by: Kalle Valo kv...@qca.qualcomm.com
Joe pointed out that I had missed a few, will send v2.
--
Kalle Valo
--
To unsubscribe from this list: send the line unsubscribe
You're missing ath10k: prefix in the patch subject.
On 20 October 2014 18:38, Yanbo Li yan...@qti.qualcomm.com wrote:
The debugfs interface reg_addrreg_val used to read and write the target
register.
The interface mem_addrmem_val used to dump the targer memory and also
can be used to assign
Kalle Valo kv...@qca.qualcomm.com writes:
this adds support for loading calibration data from a file as discussed some
time ago. Please review.
Kalle
---
Kalle Valo (3):
ath10k: add back enum ath10k_bus
ath10k: refactor ath10k_init_download_firmware()
ath10k: retrieve
On Tue, Oct 21, 2014 at 12:34 PM, Emmanuel Grumbach egrumb...@gmail.com wrote:
On Tue, Oct 21, 2014 at 9:37 AM, Krishna Chaitanya
chaitanya.m...@gmail.com wrote:
On Tue, Oct 21, 2014 at 12:06 PM, Krishna Chaitanya
chaitanya.m...@gmail.com wrote:
On Tue, Oct 21, 2014 at 11:01 AM, Emmanuel
I have 3.17.1, which includes the patch you mention. I also verified
that iwconfig reports that power management is disabled.
I don't know how easy it is to recompile the DD-WRT kernel. One thing I
could do is try another firmware instead of DD-WRT to see if the issue
still occurs.
Laurentiu
On
Michal Kazior michal.kaz...@tieto.com writes:
This is a bunch of assoc-related clean ups.
Michal Kazior (3):
ath10k: clean up assoc code
ath10k: skip some commands on reassoc
ath10k: clean up sta auth/assoc code
Thanks, all three applied.
--
Kalle Valo
--
To unsubscribe from this
Michal Kazior michal.kaz...@tieto.com writes:
Using global channel won't work with chanctx. Try
to determine the channel from the information
provided in the wmi event itself alone. This
should be sufficient.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
Thanks, applied.
--
Kalle
Michal Kazior michal.kaz...@tieto.com writes:
This simply changes the source for txpower setup.
It does not make ath10k use different txpower
values for different vifs.
This will make it easier to implement chanctx in
ath10k in the future.
Signed-off-by: Michal Kazior
On Tue, Oct 21, 2014 at 10:28 AM, Laurențiu Nicola lnic...@dend.ro wrote:
I have 3.17.1, which includes the patch you mention. I also verified
that iwconfig reports that power management is disabled.
I don't know how easy it is to recompile the DD-WRT kernel. One thing I
could do is try
Michal Kazior michal.kaz...@tieto.com writes:
In some cases hw recovery was taking an absurdly
long time due to ath10k waiting for things that
would never really complete.
Instead of waiting for inevitable timeouts poke
all completions and wakequeues and check if it's
still worth waiting.
On 2014-10-21 07:02, Emmanuel Grumbach wrote:
On Mon, Oct 20, 2014 at 10:29 PM, Laurențiu Nicola lnic...@dend.ro wrote:
No, nothing in the DD-WRT syslog. The IP seems to be the one cached by
my DHCP client. I also tried various suggestions found on the internet,
but nothing helped.
Can you
On 21 October 2014 10:17, Kalle Valo kv...@qca.qualcomm.com wrote:
Michal Kazior michal.kaz...@tieto.com writes:
In some cases hw recovery was taking an absurdly
long time due to ath10k waiting for things that
would never really complete.
Instead of waiting for inevitable timeouts poke
all
Michal Kazior michal.kaz...@tieto.com writes:
On 21 October 2014 10:17, Kalle Valo kv...@qca.qualcomm.com wrote:
Michal Kazior michal.kaz...@tieto.com writes:
In some cases hw recovery was taking an absurdly
long time due to ath10k waiting for things that
would never really complete.
On 2014-10-21 10:23, Laurențiu Nicola wrote:
It's an ASUS RT-N66U running NEWD-2/K3X from r24160.
This is a Broadcom based device, so it should behave in the same way as
other APs/Routers running the Broadcom drivers.
The driver should only send Reason 7 when receiving a PS-Poll, BlockAck,
Perhaps I'm not looking at the right log :). Do you mean enabling syslog
and /tmp/var/log/messages?
Laurentiu
On Tue, Oct 21, 2014, at 11:35, Felix Fietkau wrote:
On 2014-10-21 10:23, Laurențiu Nicola wrote:
It's an ASUS RT-N66U running NEWD-2/K3X from r24160.
This is a Broadcom based
On Tue, Oct 21, 2014 at 11:37 AM, Laurențiu Nicola lnic...@dend.ro wrote:
Perhaps I'm not looking at the right log :). Do you mean enabling syslog
and /tmp/var/log/messages?
Laurentiu
On Tue, Oct 21, 2014, at 11:35, Felix Fietkau wrote:
On 2014-10-21 10:23, Laurențiu Nicola wrote:
It's an
On Tue, Oct 21, 2014 at 2:05 PM, Felix Fietkau n...@openwrt.org wrote:
On 2014-10-21 10:23, Laurențiu Nicola wrote:
It's an ASUS RT-N66U running NEWD-2/K3X from r24160.
This is a Broadcom based device, so it should behave in the same way as
other APs/Routers running the Broadcom drivers.
The
On Tue, Oct 21, 2014 at 12:05 PM, Krishna Chaitanya
chaitanya.m...@gmail.com wrote:
On Tue, Oct 21, 2014 at 2:05 PM, Felix Fietkau n...@openwrt.org wrote:
On 2014-10-21 10:23, Laurențiu Nicola wrote:
It's an ASUS RT-N66U running NEWD-2/K3X from r24160.
This is a Broadcom based device, so it
Hi John,
Here is a first pull request for 3.18. This time I chose to work with
signed tags instead of signing emails.
Let me know if this is an issue for you.
Description of the content below.
Note that this you haven't updated your trees yet and Linus released
3.18-rc1 already,
I decided to
On Tue, Oct 21, 2014 at 2:46 PM, Emmanuel Grumbach egrumb...@gmail.com wrote:
On Tue, Oct 21, 2014 at 12:05 PM, Krishna Chaitanya
chaitanya.m...@gmail.com wrote:
On Tue, Oct 21, 2014 at 2:05 PM, Felix Fietkau n...@openwrt.org wrote:
On 2014-10-21 10:23, Laurențiu Nicola wrote:
It's an ASUS
On 21.10.2014 10:35, Felix Fietkau wrote:
On 2014-10-21 10:23, Laurențiu Nicola wrote:
It's an ASUS RT-N66U running NEWD-2/K3X from r24160.
This is a Broadcom based device, so it should behave in the same way as
other APs/Routers running the Broadcom drivers.
The driver should only send
On Tue, Oct 21, 2014 at 9:42 AM, Johannes Berg
johan...@sipsolutions.net wrote:
On Tue, 2014-10-21 at 09:26 +0530, Sujith Manoharan wrote:
Johannes Berg wrote:
Maybe we need something like this:
diff --git a/net/mac80211/scan.c b/net/mac80211/scan.c
index af0d094b2f2f..45b74ab1c59d
From: Sujith Manoharan c_man...@qca.qualcomm.com
Enabling HW queue control for normal (non-mcc) mode
causes problems with queue management, resulting
in traffic stall. Since it is mainly required for
fairness in MCC mode, disable it for the general case.
Bug: https://dev.openwrt.org/ticket/18164
Am 20.10.2014 um 21:29 schrieb Johannes Berg:
On Mon, 2014-10-20 at 21:09 +0200, Oleksij Rempel wrote:
Hi Johannes,
since this function was added by you, may be you can help here (commit
f09603a259). ath9k_htc support max 8 STAs in AP or ADHOC mode. If more
then 8 stations connected, driver
Instead of defining a completely new tracepoint
use an existing tracepoint class.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/trace.h | 32 +---
1 file changed, 5 insertions(+), 27 deletions(-)
diff --git
Hi,
I've just noticed that rx_desc tracing is somewhat
wrong. This attempts to fix it and since the trace
function prototype changes I re-use some tracing
code as well.
Michal Kazior (2):
ath10k: remove tsf argument from rx_desc tracing
ath10k: re-use trace class
Hi Michal,
Thanks for your comments. answered as below,
-Original Message-
From: Michal Kazior [mailto:michal.kaz...@tieto.com]
Sent: Tuesday, October 21, 2014 2:56 PM
To: Li, Yanbo
Cc: Valo, Kalle; ath10k-devel; Balasubramanian, Senthil Kumar;
dreamfly...@gmail.com;
On Mon, Oct 20, 2014 at 09:33:17PM +0200, Johannes Berg wrote:
On Mon, 2014-10-20 at 17:34 +0200, Karl Beldan wrote:
Indeed, will resending only 4/4 do ?
Sure.
CHECK
/home/johannes/sys/wireless/net/mac80211/rc80211_minstrel_ht_debugfs.c
From: Emmanuel Grumbach emmanuel.grumb...@intel.com
The LTR is the handshake between the device and the root
complex about the latency allowed when the bus exits power
save. This configuration was missing and this led to high
latency in the link power up. The end user could experience
high
From: Emmanuel Grumbach emmanuel.grumb...@intel.com
This reverts commit aa11bbf3df026d6b1c6b528bef634fd9de7c2619.
This commit was causing connection issues and is not needed
if IWL_MVM_RS_RSSI_BASED_INIT_RATE is set to false by default.
Regardless of the issues mentioned above, this patch added
From: Emmanuel Grumbach emmanuel.grumb...@intel.com
The probe requests sent during scan must get BT prio 3.
Fix that.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
drivers/net/wireless/iwlwifi/mvm/scan.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Liad Kaufman liad.kauf...@intel.com
I changed the string but forgot to update the fix also to
MODULE_FIRMWARE().
Signed-off-by: Liad Kaufman liad.kauf...@intel.com
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
drivers/net/wireless/iwlwifi/iwl-8000.c | 3 ++-
1 file
From: Emmanuel Grumbach emmanuel.grumb...@intel.com
Cc: sta...@vger.kernel.org [3.16+]
Fixes: 2adc8949efab (iwlwifi: mvm: BT Coex - fix boost register / LUT values)
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
drivers/net/wireless/iwlwifi/mvm/coex.c| 4 ++--
From: Emmanuel Grumbach emmanuel.grumb...@intel.com
When mac80211 wants to ensure that a frame is sent, it calls
the flush() callback. Until now, iwldvm implemented this by
waiting that all the frames are sent (ACKed or timeout).
In case of weak signal, this can take a significant amount
of time,
From: Haim Dreyfuss haim.dreyf...@intel.com
The tx power should be limited from many reasons.
currently, setting the tx power is available by the mvm only for
station interface. Adding the tx power condition to
bss_info_changed_ap_ibss make it available also for AP.
Signed-off-by: Haim Dreyfuss
Fix checkpatch warnings:
WARNING: debugfs_remove(NULL) is safe this check is probably not required
Signed-off-by: Fabian Frederick f...@skynet.be
---
net/mac80211/debugfs_key.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/net/mac80211/debugfs_key.c
Dear linux-firmware.git maintainers,
Intel released a new -9 firmware for its WiFi adpaters for the 7000 family.
No new features here, but only bug fixes.
The following changes since commit 0e5f63771d0df6d7859f7c4100a74d737c62ac88:
linux-firmware: Add firmware patch for Intel Bluetooth 7265
On Tue, 2014-10-21 at 17:26 +0200, Karl Beldan wrote:
I still don't know why I don't see the smatch array warnings here, I
guess I'll live with that for now.
I'm hoping Dan will eventually pick up on it ;-)
johannes
--
To unsubscribe from this list: send the line unsubscribe linux-wireless
When an interface is deleted, an ongoing hardware scan is canceled and
the driver must abort the scan, at the very least reporting completion
while the interface is removed.
However, if it scheduled the work that might only run after everything
is said and done, which leads to cfg80211 warning
On Tue, 2014-10-21 at 18:20 +0200, Fabian Frederick wrote:
Fix checkpatch warnings:
WARNING: debugfs_remove(NULL) is safe this check is probably not required
I'll apply this; however, I think that checkpatch is a just tool, and
the commit message should reflect why you're changing the
On Mon, 2014-10-20 at 15:49 -0700, gree...@candelatech.com wrote:
@@ -2023,7 +2023,7 @@ static int mac80211_hwsim_create_radio(int channels,
const char *reg_alpha2,
const struct ieee80211_regdomain *regd,
bool
This isn't a cfg80211 patch (subject)
+ * @IEEE80211_HW_NO_AUTO_VDEV: The driver would like for no wlanX to
+ * be created. It is expected user-space will create vdevs as
+ * desired (and thus have them named as desired).
VDEV isn't a term mac80211 uses anywhere, please use VIF or
On Mon, 2014-10-20 at 15:49 -0700, gree...@candelatech.com wrote:
+u32 portid, char *hwname, bool no_vdev)
same comment regarding vdev throughout this patch.
Also, there shouldn't be a . at the end of the subject :-)
johannes
--
To unsubscribe from this
Same comment regarding vdev, here starting from the subject.
Also, this patch isn't purely cfg80211 - should probably split it into
cfg80211 and mac80211 parts?
On Mon, 2014-10-20 at 15:49 -0700, gree...@candelatech.com wrote:
From: Ben Greear gree...@candelatech.com
This is useful when
Yep! `scb_timeout` is 60 on my router.
On Tue, Oct 21, 2014, at 14:00, poma wrote:
On 21.10.2014 10:35, Felix Fietkau wrote:
On 2014-10-21 10:23, Laurențiu Nicola wrote:
It's an ASUS RT-N66U running NEWD-2/K3X from r24160.
This is a Broadcom based device, so it should behave in the same
On 10/21/2014 12:31 PM, Johannes Berg wrote:
/* give it a proper name */
-dev_set_name(rdev-wiphy.dev, PHY_NAME %d, rdev-wiphy_idx);
+if (requested_name requested_name[0]) {
+struct cfg80211_registered_device *rdev2;
+int wiphy_idx, taken = -1, result,
On Tue, Oct 14, 2014 at 12:13:13AM -0400, S. Gilles wrote:
On Mon, Oct 13, 2014 at 10:41:26PM -0500, Larry Finger wrote:
On 10/13/2014 06:45 PM, S. Gilles wrote:
(Sending this to the right people this time, hopefully.)
I have been getting a consistent boot failure with 3.17, which I
This reverts commit 093ec3c5337434f40d77c1af06c139da3e5ba6dc.
AHB bus code has been removed, since we did not have support Atheros
AR231x SoC, required for building the AHB version of ath5k. Now that
support WiSoC chips added we can restore functionality back.
Singed-off-by: Sergey Ryazanov
- Use config symbol defined in the driver instead of arch specific one for
conditional compilation.
- Rename the ATHEROS_AR231X config symbol to ATH25.
- Fix include (ar231x_platform.h - ath25_platform.h).
- Some of AR231x SoCs (e.g. AR2315) have PCI bus support, so remove !PCI
dependency,
50 matches
Mail list logo
