Email change

Hi everyone, I'm parting ways with Tieto today so my email is going to become defunct. I'll be reachable via: kazikcz at gmail dot com. Michał ___ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k

Re: Recent driver changes destabilized QCA9377 connection quality

On 26 February 2017 at 16:40, Tobias Predel wrote: > Hello, [...] > (2) Many FCS (frame check sequence) errors paired with "len 0"? > > [ 872.338194] ath10k_pci :02:00.0: rx skb 88003765ec00 len 0 peer > 00:XX:XX:XX:XX:88 mcast sn 1470 legacy rate_idx 0 vht_nss

Re: [RFC] ath10k: silence firmware file probing warnings

On 20 January 2017 at 13:51, Kalle Valo <kv...@qca.qualcomm.com> wrote: > Michal Kazior <michal.kaz...@tieto.com> wrote: >> Firmware files are versioned to prevent older >> driver instances to load unsupported firmware >> blobs. This is reflected with a fallbac

Re: [PATCH] ath10k: prevent sta pointer rcu violation

On 13 January 2017 at 08:24, Johannes Berg wrote: > >> Unless you then continue to use that sta pointer after you release >> data_lock. > > Ouch, ok. That's rather strangely hidden though. > >> Consider this: >> >> > CPU0 CPU1 >> > 1

[PATCH] ath10k: prevent sta pointer rcu violation

elf can't be set to NULL/ERR_PTR because it is later used in sta_state() for extra sanity checks. Signed-off-by: Michal Kazior <michal.kaz...@tieto.com> --- drivers/net/wireless/ath/ath10k/core.h | 1 + drivers/net/wireless/ath/ath10k/mac.c | 18 ++ 2 files changed, 19 i

Re: Regular firmware crashes with QCA6174

On 9 January 2017 at 13:36, Shaun Crampton <sh...@cantab.net> wrote: > On Mon, 9 Jan 2017, 08:49 Michal Kazior, <michal.kaz...@tieto.com> wrote: >> On 7 January 2017 at 22:41, Shaun Crampton <sh...@cantab.net> wrote: >> > Hi, >> > >> > I'm ge

Re: Regular firmware crashes with QCA6174

On 7 January 2017 at 22:41, Shaun Crampton wrote: > Hi, > > I'm getting regular QCA6174 firmware crashes on Ubuntu 16.10 with the > QCA6174 (new Dell XPS 13, which shipped with Ubuntu 16.04). Crash > seems to be at random, roughly every 30 minutes. After the crash, > wifi

Re: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2

On 5 January 2017 at 14:28, Xavier Bestel wrote: > Hi, > > [Sorry if this is a FAQ, I didn't find the answer on > https://wireless.wiki.kernel.org/en/users/drivers/ath10k/firmware > and the mailing-list isn't searchable] > > I have an XPS 13 9360 with a stock Killer 1535,

Re: [RFC v2 05/11] ath10k: htc: refactorization

On 13 December 2016 at 19:37, Erik Stromdahl <erik.stromd...@gmail.com> wrote: > > > On 12/13/2016 06:26 PM, Valo, Kalle wrote: >> Michal Kazior <michal.kaz...@tieto.com> writes: >> >>> On 13 December 2016 at 14:44, Valo, Kalle <kv...@qca.qualcomm

Re: [RFC v2 05/11] ath10k: htc: refactorization

On 13 December 2016 at 14:44, Valo, Kalle wrote: > Erik Stromdahl writes: > >> Code refactorization: >> >> Moved the code for ep 0 in ath10k_htc_rx_completion_handler >> to ath10k_htc_control_rx_complete. >> >> This eases the implementation of

Re: ath10k raw mode

On 12 December 2016 at 14:23, Andreas Christoforou wrote: > Dear Michal, > > unfortunately I am getting the following error > > [ 50.416483] ath10k_pci :07:00.0: firmware crashed! (uuid > bdf6b230-c8f5-4e61-b174-93b0980ee5dc) > [ 50.425506] ath10k_pci :07:00.0:

Re: ath10k raw mode

On 8 December 2016 at 20:13, Andreas Christoforou wrote: > Dear All, > > could you please someone send me or let me know where I can download a > firmware with raw mode flag enabled for my QCA988X card. You can check this:

Re: [PATCH 1/3] ath10k: Ensure there are no stale ar->txqs entries.

On 2 December 2016 at 01:24, Ben Greear <gree...@candelatech.com> wrote: > On 12/01/2016 02:52 PM, Ben Greear wrote: >> >> On 08/19/2016 06:34 AM, Ben Greear wrote: >>> >>> >>> >>> On 08/18/2016 11:59 PM, Michal Kazior wrote: >>>&

Re: [PATCH 1/2] mac80211: do not iterate active interfaces when in re-configure

On 2 December 2016 at 03:29, wrote: > From: Ben Greear > > This appears to fix a problem where ath10k firmware would crash, > mac80211 would start re-adding interfaces to the driver, but the > iterate-active-interfaces logic would then try to

Re: ath10k qca988x: hostapd does not start properly

On 23 November 2016 at 23:02, Zoilo Gomez wrote: > Hi guys, > > I am trying to build an AP using QCA988X. All seems to go well to the > point where I can load the ath10k drivers, and (after installing > firmware in /lib/firmware/QCA988X/HW2.0), firmware seems to be

Re: IPQ4019 Firmware: board-2.bin vs board.bin

On 18 November 2016 at 17:46, Christian Lamparter wrote: > Hello, > > I've acquired a IPQ4019 Router (Asus RT-AC58U). And It has a IPQ4019-SoC. > I'm currently in the process of porting it to LEDE. I can report that the > router is booting and I got the ath10k to work

Re: Connection Problems with on QCA9880-BR4A

On 15 November 2016 at 23:42, Felix wrote: > Hi, > > Connected is usually a few minutes away from dsiconnected. I am running > tcpdump without pcap filters. Here are my iptables and udev rules. If I use > the SR71 everything works fine therefore I doubt it has anything to do

Re: Re[4]: Linux freezes after a time while running

On 16 November 2016 at 23:21, Conrad Kostecki <ck+ath...@bl4ckb0x.de> wrote: > Hello Michal, > > Am 07.11.2016 17:43:02, "Michal Kazior" <michal.kaz...@tieto.com> schrieb: > >> >> I assume you used a different kernel in the past compared to the &g

Re: [RFC 04/12] ath10k: htc: refactorization

On 17 November 2016 at 17:32, Erik Stromdahl <erik.stromd...@gmail.com> wrote: > > > On 11/15/2016 11:19 AM, Michal Kazior wrote: >> On 14 November 2016 at 17:33, Erik Stromdahl <erik.stromd...@gmail.com> >> wrote: >>> Code refact

Re: [RFC 03/12] ath10k: htc: Changed order of wait target and ep connect

On 15 November 2016 at 18:07, Erik Stromdahl <erik.stromd...@gmail.com> wrote: > On 11/15/2016 11:13 AM, Michal Kazior wrote: >> On 14 November 2016 at 17:33, Erik Stromdahl <erik.stromd...@gmail.com> >> wrote: >>> This patch changes the order in which

Re: Connection Problems with on QCA9880-BR4A

On 15 November 2016 at 13:59, Felix wrote: [...] >>> cat /etc/wpa_supplicant/wpa_supplicant.conf > ctrl_interface=/var/run/wpa_supplicant > network={ > ssid="eduroam" > proto=RSN > pairwise=CCMP > group=CCMP > key_mgmt=WPA-EAP > eap=TTLS >

Re: Getting ATH10K to work with Linksys WUSB6100M

On 15 November 2016 at 11:41, Johan Lindström <johan.von.lindst...@gmail.com> wrote: > >> 14 nov. 2016 kl. 12:40 wrote Michal Kazior <michal.kaz...@tieto.com>: >> >> On 11 November 2016 at 00:56, Johan Lindström >> <johan.von.lindst...@gmail.com> wrote

Re: [RFC 10/12] ath10k: Added QCA65XX hw definition

On 14 November 2016 at 17:33, Erik Stromdahl wrote: > Signed-off-by: Erik Stromdahl > --- > drivers/net/wireless/ath/ath10k/hw.h |1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/net/wireless/ath/ath10k/hw.h >

Re: [RFC 09/12] ath10k: Mailbox address definitions

On 14 November 2016 at 17:33, Erik Stromdahl wrote: > Address definitions for SDIO/mbox based chipsets. > > Signed-off-by: Erik Stromdahl > --- > drivers/net/wireless/ath/ath10k/hw.h | 53 > ++ > 1 file

Re: [RFC 06/12] ath10k: bmi: Added SOC reg read/write functions

On 14 November 2016 at 17:33, Erik Stromdahl wrote: > Added functions implementing the following BMI commands: > > BMI_READ_SOC_REGISTER > BMI_WRITE_SOC_REGISTER > > Reading and writing BMI registers is sometimes needed for > SDIO chipsets. I didn't see

Re: [RFC 05/12] ath10k: htc: Added ATH10K_HTC_FLAG_BUNDLE_LSB

On 14 November 2016 at 17:33, Erik Stromdahl wrote: > Signed-off-by: Erik Stromdahl > --- > drivers/net/wireless/ath/ath10k/htc.h |2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/net/wireless/ath/ath10k/htc.h >

Re: [RFC 04/12] ath10k: htc: refactorization

On 14 November 2016 at 17:33, Erik Stromdahl wrote: > Code refactorization: > > Moved the code for ep 0 in ath10k_htc_rx_completion_handler > to ath10k_htc_control_rx_complete. > > This eases the implementation of SDIO/mbox significantly since > the ep_rx_complete cb is

Re: [RFC 03/12] ath10k: htc: Changed order of wait target and ep connect

On 14 November 2016 at 17:33, Erik Stromdahl wrote: > This patch changes the order in which the driver waits for the > target to become ready and the service connect of the HTC > control service. > > The HTC control service is connected before the driver starts > waiting

[PATCH] ath10k: add spectral scan support to wmi-tlv

Command structure and event flow doesn't seem to be any different compared to existing implementation for other firmware branches. This patch effectively adds in-driver support for spectral scanning on QCA61x4 and QCA9377. Tested QCA9377 w/ WLAN.TF.1.0-00267-1. Signed-off-by: Michal Kazior

[PATCH] ath10k: fix null deref on wmi-tlv when trying spectral scan

u_down_read+0x12/0x60 [ 168.116680] [] vfs_write+0xb8/0x1a0 [ 168.118293] [] SyS_write+0x46/0xa0 [ 168.119912] [] entry_SYSCALL_64_fastpath+0x1a/0xa4 [ 168.121737] Code: Bad RIP value. [ 168.123318] RIP [< (null)>] (null) Signed-off-by: Michal Kazi

Re: Connection problems with Qualcomm Atheros QCA6174

On 13 November 2016 at 06:57, Henrý Þór Baldursson wrote: > Hello > > I have a Lenovo Ideapad Yoga 910 running Athergos, kernel version 4.8.7. > > My problem is that intermittently my wifi will just grind to a halt > and even stop working. > > The driver reports the

Re: Getting ATH10K to work with Linksys WUSB6100M

On 11 November 2016 at 00:56, Johan Lindström wrote: > This device is running QCA9377 chipset with the usb.id 13b1:0042 > > Any ideas on how to add this device to the working devices? Does ath10k even > work with USB devices? > > See info:

Re: Connection Problems with on QCA9880-BR4A

On 11 November 2016 at 13:07, Felix wrote: > Hello, > > I am running a Debian Jessie server on the backports kernel > 4.7.0-0.bpo.1-amd64. An Ubiquiti SR71 with its AR928X is working just fine > under ath9k. > > The mikrotik R11e-5HacT with its QCA9880-BR4A is recognized

Re: QCA988X firmware crash when sending in monitor mode

On 7 November 2016 at 15:22, Ouri Lipner wrote: > Hi all, > I’m consistently encountering issues with raw wifi packet injection. > > Sending a raw packet in monitor mode keeps crashing the firmware. > This happens consistently with every firmware that supports raw mode. >

Re: Re[2]: Linux freezes after a time while running

On 7 November 2016 at 06:38, Conrad Kostecki <ck+ath...@bl4ckb0x.de> wrote: > Hello Michal, > >> Michal Kazior <michal.kaz...@tieto.com> hat am 2. November 2016 um 16:27 >> geschrieben: > >> Were the cards working with this particular microATX mainboard befo

Re: Re[2]: Linux freezes after a time while running

On 2 November 2016 at 10:00, Conrad Kostecki <ck+ath...@bl4ckb0x.de> wrote: > Hi! > >> Michal Kazior <michal.kaz...@tieto.com> hat am 2. November 2016 um 04:31 >> geschrieben: >> I suspect the pcie link gets broken one direction because attempting a >>

Re: Re[2]: Linux freezes after a time while running

On 31 October 2016 at 17:48, Conrad Kostecki <ck+ath...@bl4ckb0x.de> wrote: > Hello Michał, > > Am 31.10.2016 11:12:03, "Michal Kazior" <michal.kaz...@tieto.com> schrieb: > >> You could try loading ath10k_pci with reset_mode=1 parameter. >> >&

Re: Question on 10.4 firmware and fetch-indication logic.

On 1 November 2016 at 19:12, Adrian Chadd wrote: > On 1 November 2016 at 11:04, Ben Greear wrote: > >> >> I do not know the code well around the fetch-ind logic: This is how the >> firmware tells the driver that it has fully transmitted a frame and

Re: Question on 10.4 firmware and fetch-indication logic.

On 1 November 2016 at 18:21, Ben Greear wrote: > I am testing on modified 4.7 kernel and modified firmware with QCA9984 NIC > and lots of virtual station vdevs. > > The issue I am looking at currently is that I am seeing floods of these > messages > in some cases: > > Nov

Re: Linux freezes after a time while running

On 28 October 2016 at 21:05, Conrad Kostecki wrote: > Hi! > In order to create a dual band AP, I've bought two Compex LE900VX cards. > As the mainboard has only one PCIe slot, I also bought a Mikrotik RB14e > miniPCIe->PCIe adapter, which can carry up to 4 miniPCIe cards.

Re: qca6174 missing firmware or subsystem id?

On 14 October 2016 at 10:05, Jiří Prchal wrote: [...] >> What channel is your AP in? Are there multiple APs in the area? This >> could be also a channel problem, 'iw list' helps to investigate that (or >> changing the channel on AP). >> > > As I wrote the problem was

Re: ath10k: about packet injection

On 6 October 2016 at 04:11, Xuebing Wang <xbi...@gmail.com> wrote: > On 2016年09月19日 19:13, Michal Kazior wrote: >> >> On 19 September 2016 at 01:27, Xuebing Wang <xbi...@gmail.com> wrote: >>> >>> Hi Community, >>> >>> ath10k

Re: Beacon sending information

On 3 October 2016 at 15:47, Ricardo Santos wrote: > Hi, > > I recently started to go through the ath10k driver and mac80211 source to > understand where events happen in the code. Currently I'm trying to find > where the beacon > generation and their tx is being handled,

Re: [PATCH] ath10k: cache calibration data when the core is stopped.

On 13 September 2016 at 23:11, Marty Faltesek wrote: [...] > +int > +ath10k_cal_data_alloc(struct ath10k *ar, void **buf) > +{ > + u32 hi_addr; > + __le32 addr; > + int ret; > + > + vfree(*buf); > + *buf = vmalloc(QCA988X_CAL_DATA_LEN);

Re: ath10k: about packet injection

On 19 September 2016 at 01:27, Xuebing Wang wrote: > Hi Community, > > ath10k wiki says packet injection isn't supported yet. Is it difficult to > add packet injection for chip like QCA6174 hw 2.1 in Killer 1525? Thanks. This would require some tricks: - monitor vdev can't tx

Re: [PATCH 4/4] ath10k: fix spurious tx/rx during boot

On 17 September 2016 at 00:37, Hsu, Ryan wrote: [...] >> + /* WMI and HTT may use separate HIF pipes and are not guaranteed to be >> + * serialized properly implicitly. >> + * >> + * Moreover (most) WMI commands have no explicit acknowledges. It is >>

Re: accessing ath10k calibration data

On 15 September 2016 at 01:54, Marty Faltesek wrote: > I sent out the patch. > > I ran into another related issue. Let me explain what we are trying to do: > > We want to examine cal_data for a possibly mis-calibrated OTP, and if > so, patch it and store > the result in /tmp

Re: accessing ath10k calibration data

On 9 September 2016 at 19:42, Marty Faltesek wrote: > It's blocked by the code below which I tried to ifdef out, but then it > returns all 0's. > > diff --git a/drivers/net/wireless/ath/ath10k/debug.c > b/drivers/net/wireless/ath/ath10k/debug.c > index 8b01e3e..bb8b7ec

Re: Ath10k probe response error related to mac80211 commit.

On 1 September 2016 at 22:52, Ben Greear wrote: > On 09/01/2016 11:53 AM, Johannes Berg wrote: >> On Thu, 2016-09-01 at 11:23 -0700, Ben Greear wrote: >>> >>> Could easily be that others are corrupted too, but since probe resp >>> is bad, the association will not proceed.

Re: Questions for ath10k rate control, bandwidth, and channel sensing

On 26 August 2016 at 11:00, Changmok Yang wrote: > Hi. > We are trying to change transmission bandwidth and data rate. > > 1. We found that we can only control per-station channel width, and > rate control, like Minstrel, is not controlled by ath10k and in > firmware. Then,

Re: [PATCH 4/4] ath10k: fix spurious tx/rx during boot

On 24 August 2016 at 19:20, Ben Greear <gree...@candelatech.com> wrote: > On 07/19/2016 03:34 AM, Michal Kazior wrote: >> >> HW Rx filters and masks are not configured >> properly by firmware during boot sequences. The >> MAC_PCU_ADDR1 is set to 0s instead of 1s

Re: ath10k: qca6174 firmware: difference between hw2.1/firmware-5 and hw3.0/firmware-4

On 24 August 2016 at 05:57, Xuebing Wang wrote: > Hi Kalle, > > I cloned your ath10k-firmware from your github. Would you please advise what > are the differences of hw2.1/firmware-5 and hw3.0/firmware-4 for qca6174? > Does hw3.0/firmware-4 support Monitor Mode? > > I have a

Re: [PATCH 1/3] ath10k: Ensure there are no stale ar->txqs entries.

On 19 August 2016 at 03:26, wrote: > From: Ben Greear > > I was seeing kernel crashes due to accessing freed memory > while debugging a 9984 firmware that was crashing often. > > This patch fixes the crashes. I am not certain if there > is a

Re: [PATCHv2 2/2] ath10k: Allow setting coverage class

On 3 August 2016 at 17:37, Sebastian Gottschall wrote: > >>> + if (value < 0) >>> + value = ar->fw_coverage.coverage_class; >>> + >>> + /* Break out if the coverage class and registers have the >>> expected >>> +* value. >>> +*/

Re: [PATCHv2 2/2] ath10k: Allow setting coverage class

On 1 August 2016 at 12:21, Benjamin Berg wrote: > Unfortunately ath10k does not generally allow modifying the coverage class > with the stock firmware and Qualcomm has so far refused to implement this > feature so that it can be properly supported in ath10k. If we

Re: [PATCH] ath10k: Allow setting coverage class

On 29 July 2016 at 17:09, Ben Greear wrote: > On 07/29/2016 07:52 AM, Benjamin Berg wrote: [...] >> Yeah, I am aware of the fact that the firmware may do internal resets >> from time to time. The interesting question (and one for which I do not >> know the answer) is

Re: ath10k fail to load firmware

On 2 August 2016 at 14:10, Valo, Kalle <kv...@qca.qualcomm.com> wrote: > Michal Kazior <michal.kaz...@tieto.com> writes: > >> On 19 July 2016 at 09:09, Stanislaw Gruszka <sgrus...@redhat.com> wrote: >>> Perry from Dell has ath10k device, which do not wor

Re: Use Channel Switch Announcement (CSA) without DFS

On 28 July 2016 at 00:42, Gaurang Ramesh Naik wrote: > Hi All, > > Is it possible to use CSA when the AP operates on channel that do not > require DFS? Can I trigget CSA from the AP in some way? You can ask hostapd via hostapd_cli to: chan_switch 5 5180 This will start CSA

Re: [PATCH 2/4] ath10k: Add provision for Rx descriptor abstraction

On 27 July 2016 at 14:59, Thiagarajan, Vasanthakumar <vthia...@qti.qualcomm.com> wrote: > On Wednesday 27 July 2016 06:13 PM, Michal Kazior wrote: >> On 27 July 2016 at 14:36, Vasanthakumar Thiagarajan [...] >>> --- a/drivers/net/wireless/ath/ath10k/core.c >>> +++

Re: [PATCH 2/4] ath10k: Add provision for Rx descriptor abstraction

On 27 July 2016 at 14:36, Vasanthakumar Thiagarajan wrote: > There are slight differences in Rx hw descriptor information > among different chips. So far driver does not use those new > information for any functionalities, but there is one important > information which

Re: [PATCH] ath10k: Allow setting coverage class

On 27 July 2016 at 10:33, Benjamin Berg wrote: > Unfortunately ath10k does not generally allow modifying the coverage class > with the stock firmware and Qualcomm has so far refused to implement this > feature so that it can be properly supported in ath10k. If we

Re: 9984 issues solution

On 26 July 2016 at 11:31, Sebastian Gottschall wrote: > i found the reason and the solution. i disabled all beamforming vht caps. > this will prevent the firmware of beeing crashing. > so it seems, beamforming is responsible for it > could the firmware be fixed? This

Re: Not able to capture qos data packets - QCA988x

On 26 July 2016 at 05:06, sudheer thota wrote: > wireless interface(ath10k) monitor failing to capture data packets when > WMM enabled on AP. > > AP Status reflects in following state: (when no QOS data Packets. MGMT and > CTRL Packets are able to captured) > 1) 0x03 (3) -

Re: ath10k fail to load firmware

On 21 July 2016 at 03:24, wrote: > HI All: > > I got two board files for subsystem id 0310 . > > eeprom_ar6320_3p0_NFA344A_power1213_DE_5459.bin > eeprom_ar6320_3p0_NFA344A_power1213.bin > > But I am not sure which files should be used , and I want know which board > file

Re: [PATCH 2/2] ath10k: Fix sending NULL/ Qos NULL data frames for QCA99X0 and later

On 20 July 2016 at 13:43, Shajakhan, Mohammed Shafi (Mohammed Shafi) wrote: > Michal, > > Can you please let me know if this change is fine or not ? > I am waiting infinitely for your reply long time Sorry. I was absent for a while and this email slipped by. Quoting

Re: rx rate issue

On 20 July 2016 at 13:10, Sebastian Gottschall <s.gottsch...@dd-wrt.com> wrote: > Am 20.07.2016 um 13:03 schrieb Michal Kazior: >> >> On 20 July 2016 at 12:50, Sebastian Gottschall <s.gottsch...@dd-wrt.com> >> wrote: >>> >>> Am 20.07.2016 um 12:

Re: rx rate issue

On 20 July 2016 at 12:50, Sebastian Gottschall <s.gottsch...@dd-wrt.com> wrote: > Am 20.07.2016 um 12:23 schrieb Michal Kazior: >> >> On 20 July 2016 at 10:51, Sebastian Gottschall <s.gottsch...@dd-wrt.com> >> wrote: >>> >>> Hello >>>

Re: rx rate issue

On 20 July 2016 at 10:51, Sebastian Gottschall wrote: > Hello > > while hunting a link stability (packet transmission stop) issue i discovered > a maybe cosmetic, but maybe als serious issue. > AP is a QCA9880 3x3 card configured as WDS AP > Station is a QCA9880 2x2 card

Re: ath10k fail to load firmware

Hi Perry, I've been told that Dell apparently maintains their subsystem ids independently (from QCA). You should probably ask your Windows driver team (or whoever is responsible for the subsystem id stuff at Dell) for subsystem ids and board/eeprom files associated with them and then provide them

Re: [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform

On 20 July 2016 at 08:11, Adrian Chadd wrote: > Hi, > > The ath10k on-chip DMA engine only knows how to address the low 32 > bits of physical address space. It can't do DMA elsewhere without a > hardware IOMMU in the system. Even then, as far as the device is > concerned, it's

Re: [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform

On 20 July 2016 at 07:44, Adrian Chadd wrote: > Hi, > > dma coherent doesn't /have/ to mean "low 32 bits". It's just supposed > to mean "try really hard to use uncached memory on platforms that > support it." Good point. Maybe it does on x86, or at least some machines. @Ben:

Re: [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform

On 19 July 2016 at 18:53, Ben Greear wrote: > On 07/19/2016 09:13 AM, Adrian Chadd wrote: [...] >> Try allocating WMI memory with GFP_DMA32. The way it currently is >> working in linux is that caling dma map ends up allocating iommu slots >> to map that 64 bit memory back

Re: [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform

On 19 July 2016 at 17:25, Manoharan, Rajkumar <rmano...@qti.qualcomm.com> wrote: > On June 30, 2016 12:39 PM, Michal Kazior <michal.kaz...@tieto.com> wrote: >> On 29 June 2016 at 18:35, Manoharan, Rajkumar <rmano...@qti.qualcomm.com> >> wrote: >>>&

[RFC] ath10k: silence firmware file probing warnings

firmware files making things even more confusing. Hence use request_firmware_direct() which does not produce extra warnings. This shouldn't really break anything because most modern systems don't rely on udev/hotplug helpers to load firmware files anymore. Signed-off-by: Michal Kazior <michal.

[PATCH 3/4] ath10k: add wmi command barrier utility

This allows placing command barriers for explicit serializing and synchronizing state. Useful for future driver development. Signed-off-by: Michal Kazior <michal.kaz...@tieto.com> --- drivers/net/wireless/ath/ath10k/core.h | 1 + drivers/net/wireless/ath/ath10k/wmi.c

[PATCH 1/4] ath10k: implement wmi echo command

Will be useful for implementing command barriers. Signed-off-by: Michal Kazior <michal.kaz...@tieto.com> --- drivers/net/wireless/ath/ath10k/wmi-ops.h | 17 + drivers/net/wireless/ath/ath10k/wmi-tlv.c | 29 + drivers/net/wireless/ath/ath10k

[PATCH 2/4] ath10k: implement wmi echo event

Will be useful for implementing command barriers. Signed-off-by: Michal Kazior <michal.kaz...@tieto.com> --- drivers/net/wireless/ath/ath10k/wmi-ops.h | 12 drivers/net/wireless/ath/ath10k/wmi-tlv.c | 28 drivers/net/wireless/ath/ath10k/wmi.c

[PATCH 4/4] ath10k: fix spurious tx/rx during boot

...@tieto.com> Signed-off-by: Michal Kazior <michal.kaz...@tieto.com> --- drivers/net/wireless/ath/ath10k/core.c | 68 ++ 1 file changed, 68 insertions(+) diff --git a/drivers/net/wireless/ath/ath10k/core.c b/drivers/net/wireless/ath/ath10k/core.c index e889

[PATCH 0/4] ath10k: fix spurious tx/rx during boot

etails. I didn't do extensive testing but I can confirm that I am no longer able to reroduce "no channel" warnings and Marek tells me he no longer sees any signal bumps on oscilloscope with his QCA9882. Michal Kazior (4): ath10k: implement wmi echo command ath10k: implement wmi echo e

Re: ath10k fail to load firmware

On 19 July 2016 at 11:02, wrote: > Dell - Internal Use - Confidential > > I rename the bin file . and capture new full logs from booting to firmware > error . > The error still happened. Please help to check it . > I want to know whether the new firmware bin are updated

Re: ath10k fail to load firmware

On 19 July 2016 at 10:24, wrote: > Dell - Internal Use - Confidential > > HI All: > I have replaced the new firmware files to old one. And I build new > ath10k_pci.ko ,ath10k_core.ko to get some > debug info. > > The new firmware is still not loaded by ath10k driver . >

Re: ath10k fail to load firmware

On 19 July 2016 at 09:09, Stanislaw Gruszka wrote: > Perry from Dell has ath10k device, which do not work with current > linux-firmware. It's on RHEL kernel, however wirelss stack and drivers > are from 4.7-rc1 (I did not update to 4.7 final yet, since I do not see > ath10k

Re: ath10k usb support

On 29 June 2016 at 20:10, Francois Gervais wrote: > Hi, > > We are evaluating the new WUSB6100M wireless adapter for use with our > embedded platform. This is a wireless usb dongle based on the QCA9377 chipset. > > At first glance it seems that the current ath10k

Re: [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform

On 29 June 2016 at 18:35, Manoharan, Rajkumar wrote: >>> Am 29.06.2016 um 16:04 schrieb Sebastian Gottschall: >>> this fix will crash QCA9980 on QCA IPQ8064 cpu based systems. >>> so please rework it, or leave it out. >>> note: >>> maybe the limit of 256kb is too low

[PATCH] mac80211: fix fq lockdep warnings

] [] pci_device_remove+0x38/0xb0 ... Fixes: 5caa328e3811 ("mac80211: implement codel on fair queuing flows") Fixes: fa962b92120b ("mac80211: implement fair queueing per txq") Tested-by: Kalle Valo <kv...@qca.qualcomm.com> Reported-by: Kalle Valo <kv...@qca.qualcomm.com&

[PATCH] ath10k: disable wake_tx_queue for older devices

. Therefore disable it unless it is really beneficial with current codebase (which is when firmware supports smart pull-push tx scheduling). Signed-off-by: Michal Kazior <michal.kaz...@tieto.com> --- Notes: v1: - improve commit log drivers/net/wireless/ath/ath10k/core.h | 1 + drive

Re: [PATCH 2/2] ath10k: Fix sending NULL/ Qos NULL data frames for QCA99X0 and later

On 27 June 2016 at 16:36, Mohammed Shafi Shajakhan <moham...@codeaurora.org> wrote: > Hi Michal, > > thanks for the review .. > > On Mon, Jun 27, 2016 at 11:27:27AM +0200, Michal Kazior wrote: >> On 23 June 2016 at 18:40, Mohammed Shafi Shajakhan >> <moham..

Re: Cannot initialize Compex WLE600VX for 802.11ac?

On 24 June 2016 at 05:27, Tom Marble wrote: > Tomasz Skapski writes: >> In your config file set 'fragm_threshold=-1', or comment it. > > Indeed this was the last critical configuration change... > Now I'm able to bring up the interface! > > Then I was

[RFT] mac80211: fix fq lockdep warnings

("mac80211: implement codel on fair queuing flows") Fixes: fa962b92120b ("mac80211: implement fair queueing per txq") Reported-by: Valo, Kalle <kv...@qca.qualcomm.com> Signed-off-by: Michal Kazior <michal.kaz...@tieto.com> --- Hi Kalle, Can you verify this fixes c

Re: ath10k firmware version - 10.4

On 22 June 2016 at 08:13, sunder Kumaresan wrote: > Hello all, [...] > But, When boardData_AR900B_CUS239_5G_v2_001.bin and > boardData_AR900B_CUS260_2G_v2_002.bin have been renamed as board xxx. bin > files. It shows up as mismatch in the magic number. I'm *guessing*

Re: [PATCH 2/2] ath10k: Fix sending NULL/ Qos NULL data frames for QCA99X0 and later

On 23 June 2016 at 18:40, Mohammed Shafi Shajakhan wrote: > From: Mohammed Shafi Shajakhan > > For chipsets like QCA99X0, IPQ4019 and later we are not getting proper > NULL func status (always acked/successs !!) when hostapd does a >

Re: [PATCH] ath10k: fix potential null dereference bugs

On 10 June 2016 at 14:52, Bob Copeland wrote: > Smatch warns about a number of cases in ath10k where a pointer is > null-checked after it has already been dereferenced, in code involving > ath10k private virtual interface pointers. > > Fix these by making the dereference

Re: Number of Transmission retries

On 8 June 2016 at 11:01, Gaurang Ramesh Naik wrote: > Hi, > > I know there is an iw command to set the number of transmission > retries using "iw phy phyx set retry short 'y' long 'z'". When I used > this command though, I did not observe any change in the performance > of the

Re: Question on "ath10k: document ofdm/5ghz rate offset with a macro"

On 7 June 2016 at 14:57, Ben Greear <gree...@candelatech.com> wrote: > On 06/06/2016 11:23 PM, Michal Kazior wrote: >> On 6 June 2016 at 23:25, Ben Greear <gree...@candelatech.com> wrote: >>> >>> While porting some patches forward, I notice the c

Re: Any tips on where per-packet antenna selection could be pushed?

On 7 June 2016 at 09:40, Adrian Chadd wrote: > On 6 June 2016 at 23:24, Janusz Dziedzic wrote: >> On 6 June 2016 at 21:22, Zach Sherin wrote: >>> That's what I thought. Thanks for confirming, and thanks again for >>> your

Re: Question on "ath10k: document ofdm/5ghz rate offset with a macro"

On 6 June 2016 at 23:25, Ben Greear wrote: > While porting some patches forward, I notice the change below > that renamed the method to "ath10k_mac_sta_has_ofdm_only". But, > that is not really what that is checking, since it just throws > away the CCK rates (and they

Re: Please don't puke: Modifying Frame Version, Beacon and Probe-Response values

On 31 May 2016 at 10:44, jpo wrote: > Hello all, > to implement a "Stealth feature", e.g. the WLAN network does not show up in > normal Scans, we modified the Frame version, Beacon and Probe-Response > values for an old ATH5K card running on the now dormant Madwifi driver. >

Re: DFS fails with QCA6174 and QCA9377

On 21 May 2016 at 16:19, The Dark Avenger wrote: > Hello, > > I'm currently trying to set-up an AP in the 5 GHz band. I have a QCA6174 > (Killer 1525) and a QCA9377 adapter at hand. > > Unfortunately, while both cards work otherwise well, e.g. I can create an AP > in the

[RFC/RFT] ath10k: disable wake_tx_queue for older devices

Some setups suffer performance regressions with current wake_tx_queue implementation. Signed-off-by: Michal Kazior <michal.kaz...@tieto.com> --- Hi Roman, Can you give this patch a try and see if it helps with your performance problems, please? drivers/net/wireless/ath/ath10k/core.

Re: QCA9984 VHT160 support

+ re-adding ath10k list On 17 May 2016 at 14:05, Sebastian Gottschall <s.gottsch...@dd-wrt.com> wrote: >Am 17.05.2016 um 14:00 schrieb Michal Kazior: >> On 17 May 2016 at 13:43, Sebastian Gottschall <s.gottsch...@dd-wrt.com> >> wrote: >>> Attached you

  1   2   3   4   5   6   7   8   >