On Sunday, April 24, 2016 01:16:11 AM David Hutchison wrote:
> I spoke too soon:
> https://pci-ids.ucw.cz/read/PC/168c/0050
>
> It is the QCA9887, so it's definitely on the PCIe bus and is being seen.
Does ath10k support the QCA9887? I see no entry for this pci-id (168c:0050)
in ath10k's pci
Hello,
On Monday, April 25, 2016 10:53:41 AM David Hutchison wrote:
> So with some modifications to pci.c, hw.h and core.c I was able to get
> the radio initialized! :)
Hey, that's nice! Can you make and post a patch for that?
I'm sure if it's just a matter of adding the new pci and chip
ids to
On Tuesday, April 26, 2016 07:20:32 AM Valo, Kalle wrote:
> Christian Lamparter <chunk...@googlemail.com> writes:
> > On Monday, April 25, 2016 10:53:41 AM David Hutchison wrote:
> >> So with some modifications to pci.c, hw.h and core.c I was able to get
> >> the
On Tuesday, February 28, 2017 7:22:32 PM CET Rajkumar Manoharan wrote:
> On 2017-02-27 23:58, Sven Eckelmann wrote:
> > It looks to me now that this information is contradicting your
> > implementation
> > (which now loads the data from 0:ART partition [1] like pre-cal data
> > [2] and
> > then
On Friday, November 18, 2016 8:12:58 PM CET Michal Kazior wrote:
> On 18 November 2016 at 19:40, Christian Lamparter
> <chunk...@googlemail.com> wrote:
> > On Friday, November 18, 2016 6:25:24 PM CET Michal Kazior wrote:
> >> On 18 November 2016 at 17:46, Chri
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 with 4.8.8 +
LEDE's compat-wireless (2016-10-08-1).
Now, I ran across a small discrepancy with
Hello Shafi,
On Thursday, December 15, 2016 10:13:39 PM CET Mohammed Shafi Shajakhan wrote:
> I am also thinking, as of now there is not much use in appending
> the extended peer stats (which gets periodically ) to the linked list
> '>debug.fw_stats.peers_extd)' and should we get rid of the
Hello,
It looks like google put your mail into the spam-can.
I'm sorry for not answering sooner.
On Wednesday, December 7, 2016 11:58:24 AM CET Mohammed Shafi Shajakhan wrote:
> On Mon, Dec 05, 2016 at 10:52:45PM +0100, Christian Lamparter wrote:
> > The 10.4 firmware adds exte
On Wednesday, December 14, 2016 1:03:38 PM CET Mohammed Shafi Shajakhan wrote:
> > On Wednesday, December 7, 2016 11:58:24 AM CET Mohammed Shafi Shajakhan
> > wrote:
> > > On Mon, Dec 05, 2016 at 10:52:45PM +0100, Christian Lamparter wrote:
> > >
<https://lkml.kernel.org/r/992a4e2676037a06f482cdbe2d3d39e287530be5.1480974623.git.chunk...@googlemail.com>
Cc: Mohammed Shafi Shajakhan <moham...@codeaurora.org>
Signed-off-by: Christian Lamparter <chunk...@googlemail.com>
---
drivers/net/wireless/ath/ath10k/core.h| 2
ath10k_wmi_tlv_op_pull_fw_stats() uses tb = ath10k_wmi_tlv_parse_alloc(...)
function, which allocates memory. If any of the three error-paths are
taken, this tb needs to be freed.
Signed-off-by: Christian Lamparter <chunk...@googlemail.com>
---
drivers/net/wireless/ath/ath10k/wmi-tlv.
is because the
ath10k_wmi_10_4_op_pull_fw_stats() function tries to
pull the same amount (num_peer_stats) for every statistic
data unit.
Fixes: 4a49ae94a448faa ("ath10k: fix 10.4 extended peer stats update")
Signed-off-by: Christian Lamparter <chunk...@googlemail.com>
---
drive
On Thu, Dec 29, 2016 at 3:11 PM, Kalle Valo <kv...@qca.qualcomm.com> wrote:
> Christian Lamparter <chunk...@googlemail.com> wrote:
>> The 10.4 firmware adds extended peer information to the
>> firmware's statistics payload. This additional info is
>>
Hello Shafi and Kalle,
On Tuesday, January 3, 2017 10:58:27 AM CET Mohammed Shafi Shajakhan wrote:
> On Fri, Dec 30, 2016 at 03:35:10PM +0100, Christian Lamparter wrote:
> > On Thu, Dec 29, 2016 at 3:11 PM, Kalle Valo <kv...@qca.qualcomm.com> wrote:
> > > Ch
Hello Shafi,
On Monday, December 19, 2016 10:19:57 PM CET Mohammed Shafi Shajakhan wrote:
> On Sat, Dec 17, 2016 at 06:46:34PM +0100, Christian Lamparter wrote:
> > The 10.4 firmware adds extended peer information to the
> > firmware's statistics payload. This additional inf
Hello Shafi,
On Thursday, December 22, 2016 9:18:01 PM CET Mohammed Shafi Shajakhan wrote:
> > On Monday, December 19, 2016 10:19:57 PM CET Mohammed Shafi Shajakhan wrote:
> > > On Sat, Dec 17, 2016 at 06:46:34PM +0100, Christian Lamparter wrote:
> > > > The 10.4
On Monday, March 27, 2017 1:33:54 PM CEST Sebastian Gottschall wrote:
> i dont know how to prove you that the firmware format is identical without
> simply showing you the hexdump.
We sort of know what is encoded in these calibration files in the flash and
in the board files. I've told you about
On Saturday, March 25, 2017 8:24:59 AM CET Sebastian Gottschall wrote:
> Am 24.03.2017 um 16:01 schrieb Christian Lamparter:
> > On Friday, March 24, 2017 11:09:03 AM CET Sebastian Gottschall wrote:
> >> i have a r7800 running. consider to use the board.bin file which is
&g
On Friday, March 24, 2017 11:09:03 AM CET Sebastian Gottschall wrote:
> i have a r7800 running. consider to use the board.bin file which is
> stored in flash memory of the r7800.
Well, this is a bit beside the point. But what makes you think that
what is stored in the flash memory of R7800 is
On Thursday, March 9, 2017 1:46:00 PM CET Sven Eckelmann wrote:
> On Donnerstag, 9. März 2017 11:51:13 CET Valo, Kalle wrote:
> [...]
> > I haven't followed the discussion very closely, so I might be way off,
> > but for laptop SMBIOS implementations Waldemar added a variant field to
> >
On Friday, March 10, 2017 9:06:15 AM CET Sven Eckelmann wrote:
> Board Data File (BDF) is loaded upon driver boot-up procedure. The right
> board data file is identified on QCA4019 using bus, bmi-chip-id and
> bmi-board-id.
>
> The problem, however, can occur when the (default) board data file
On Friday, December 1, 2017 4:05:10 PM CET Maxime Bizon wrote:
>
> On Fri, 2017-12-01 at 19:18 +0530, ako...@codeaurora.org wrote:
>
> > Hope CONFIG_MAC80211_DEBUGFS is enabled in your build.
>
> it wasn't and IMHO it's confusing because tx rate is filled by the other
> drivers without it.
>
>
Sven's boarddata for the OpenMesh A42 has been accepted. \o/
So let's try to get the board data for the RT-AC58U merged.
On Friday, December 8, 2017 10:50:12 AM CET Kalle Valo wrote:
> > I've attached the necessary bmi-board-id=16 and bmi-board-id=17 board
> > files to this mail as well. So, all
On Tuesday, 17. April 2018 10:15:42 CEST Sven Eckelmann wrote:
> The support for this device was added a while ago to OpenWrt. This AP
> requires
> two special BDFs to get the Wi-Fi PHYs working (correctly). The bmi-board-
> id='s would clash with one of the the IPQ401X AP-DK boards because QCA
On Donnerstag, 19. April 2018 16:56:36 CEST Kalle Valo wrote:
> [...]
> I have added them now, please check:
>
> https://github.com/kvalo/ath10k-firmware/commit/a47bcf1e58c4d8914af0951a80fd8861368b700d
Yes, The RT-AC58U is now working much better.
The updated RT-AC58U board-data is here:
On Donnerstag, 19. April 2018 16:47:22 CEST Sven Eckelmann wrote:
> On Donnerstag, 19. April 2018 14:33:04 CEST Kalle Valo wrote:
> > >> Unfortunately, this is wrong. Please check the mail again. The
> > >> bus=pci,bmi-chip-id=0,bmi-board-id=16,variant=OM-A62 BDF is for the
> > >> QCA9888
> >
On Montag, 23. April 2018 22:31:22 CEST Arvid Picciani wrote:
> from where does ath10k know where to look for it? all i know about is
> ath79_register_wmac in arch init. That points to a partition called
> "wifi" which makes ath9k work, but not ath10k.
It's this file:
On Monday, October 8, 2018 2:36:12 PM CEST Kalle Valo wrote:
> Christian Lamparter writes:
> > Hi,
> >
> > This is a set of board.bin files for the ZyXEL NBG6617 Router [0],
> > which I wish to be added to the ath10k-firmware repository.
> >
> > As
On Monday, October 8, 2018 3:04:56 PM CEST Kalle Valo wrote:
> Christian Lamparter writes:
>
> > Hello,
> >
> > On Friday, September 28, 2018 9:28:44 PM CEST Hauke Mehrtens wrote:
> >> the ath10k-firmware repository already contains updated board-2.bin
> &g
On Monday, February 4, 2019 4:45:12 PM CET Kalle Valo wrote:
> Christian Lamparter writes:
>
> > Many integrated QCA9984 WiFis in various IPQ806x platform routers
> > from various vendors (Netgear R7800, ZyXEL NBG6817, TP-LINK C2600,
> > etc.) have either blank, bogus or
quot;ath10k: retrieve MAC address from system firmware if
provided")
Cc: Brian Norris
Cc: Ben Greear
Cc: Felix Fietkau
Cc: Mathias Kresin
Signed-off-by: Christian Lamparter
---
Changed from v1:
- removed support for obsolete, untested firmwares
- removed unsupported TLV ops
...@vger.kernel.org
Fixes: 1a7fecb766c8 ("ath10k: reset chip before reading chip_id in probe")
Signed-off-by: Christian Lamparter
---
drivers/net/wireless/ath/ath10k/pci.c | 36 +++
1 file changed, 25 insertions(+), 11 deletions(-)
diff --git a/drivers/net/wireless/
very optimistic that this will need some more time though.
So, "let's cross that bridge whenever we get there."
Cheers,
Christian>From 38ac13d668f237941c8b77f16375f8f0e4de966a Mon Sep 17 00:00:00 2001
From: Christian Lamparter
Date: Mon, 25 Mar 2019 13:50:19 +0100
Subject: [PATCH 4
On Tuesday, September 17, 2019 8:44:12 AM CEST Kalle Valo wrote:
> Christian Lamparter wrote:
>
> > This patch restores the old behavior that read
> > the chip_id on the QCA988x before resetting the
> > chip. This needs to be done in this order since
> > the unsup
id=0,bmi-board-id=16,variant=AVM-FRITZBox-4040.bin
8212551ef77695270eef08c1feb61c6a
bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=AVM-FRITZBox-4040.bin
Best Regards,
Christian Lamparter
[0] <http://ftp.avm.de/fritzbox/fritzbox-4040/deutschland/fritz.os/info_en.txt>
(s
8cc873384c
bus=pci,bmi-chip-id=1,bmi-board-id=2,variant=ASRock-G10
Best wishes
Christian Lamparter
[1] <https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles>
bus=pci,bmi-chip-id=1,bmi-board-id=2,variant=ASRock-G10.bin
Description: Binary data
bus=pci,bmi-chip-id=1,bmi-bo
On 19/10/2020 17:05, t...@redhat.com wrote:
From: Tom Rix
A break is not needed if it is preceded by a return or goto
Signed-off-by: Tom Rix
diff --git a/drivers/net/wireless/intersil/p54/eeprom.c
b/drivers/net/wireless/intersil/p54/eeprom.c
index 5bd35c147e19..3ca9d26df174 100644
---
On 2020-09-18 18:29, Ansuel Smith wrote:
Document use of qcom,ath10k-pre-calibration-data-mtd bindings used to
define from where the driver will load the pre-cal data in the defined
mtd partition.
Signed-off-by: Ansuel Smith
Q: Doesn't mtd now come with nvmem support from the get go? So
the
On 2020-09-18 20:31, ansuels...@gmail.com wrote:
-Messaggio originale-
Da: Christian Lamparter
Inviato: venerdì 18 settembre 2020 18:54
A: Ansuel Smith ; Kalle Valo
Cc: devicet...@vger.kernel.org; net...@vger.kernel.org; linux-
wirel...@vger.kernel.org; linux-ker...@vger.kernel.org
Hello,
On 2020-09-15 17:02, Hans Geiblinger wrote:
The support for this device is currently being added into OpenWrt. This AP
requires
two special BDFs to get the Wi-Fi PHYs working (correctly).
* description for what hardware this is:
- it is a IPQ4019 based board
- one QCA40xx radio
On 23/06/2021 21:14, Pavel Skripkin wrote:
In case of not supported chip the code jump
to the error handling path, but _ret_ will be set to 0.
Returning 0 from probe means, that ->probe() succeeded, but
it's not true when chip is not supported.
Fixes: f8914a14623a ("ath10k: restore QCA9880-AR1A
: Robert Marko
Cc: Thibaut VARÈNE
Signed-off-by: Christian Lamparter
---
v1 -> v2:
- use %zu and %u in the format string for size_t
and u32 types (catched by the "kernel test robot").
- reworded commit message + successfully tested on QCA9880v2
I placed t
On 10/10/2021 00:17, Robert Marko wrote:
Some ath10k IPQ40xx devices like the MikroTik hAP ac2 and ac3 require the
BDF-s to be extracted from the device storage instead of shipping packaged
API 2 BDF-s.
This is required as MikroTik has started shipping boards that require BDF-s
to be updated,
On 14/10/2021 14:01, Robert Marko wrote:
On Thu, 14 Oct 2021 at 13:54, Christian Lamparter wrote:
On 10/10/2021 00:17, Robert Marko wrote:
Some ath10k IPQ40xx devices like the MikroTik hAP ac2 and ac3 require the
BDF-s to be extracted from the device storage instead of shipping packaged
API
ch is required for initializing
the WIFI.
Tested with Netgear EX6150v2 (IPQ4018)
Cc: Robert Marko
Cc: Thibaut Varène
Signed-off-by: Christian Lamparter
---
This idea came up during the discussion of:
"ath10k: support bus and device specific API 1 BDF selection"
I do not
: If device_get_mac_address() didn't get a valid MAC from
either the DT/ACPI, nvmem, etc... the driver will just generate
random MAC (same as it did before).
Signed-off-by: Christian Lamparter
---
@Kalle from what I can tell, this is how nvmem-mac could be
done with the existing device_get_mac_address
stments.
Signed-off-by: Christian Lamparter
---
net/ethernet/eth.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/net/ethernet/eth.c b/net/ethernet/eth.c
index c7d9e08107cb..5e55b08577b1 100644
--- a/net/ethernet/eth.c
+++ b/net/ethernet/eth.c
@@ -602,7 +602,9 @@ static int
On 28/10/2021 10:58, Kalle Valo wrote:
Christian Lamparter writes:
ATH10K chips are used it wide range of routers,
accesspoints, range extenders, network appliances.
On these embedded devices, calibration data is often
stored on the main system's flash and was out of reach
for the driver
On 28/10/2021 20:57, Ansuel Smith wrote:
The "[1/2] ath10k: Try to get mac-address from dts" patch
will need a respin, so it can apply cleanly.
Is Anyone interested? If not, I can take a shot at it on Saturday.
A refreshed patch is applied to atk10k-ct repo so it would be good to
have the
On 28/10/2021 13:52, Kalle Valo wrote:
v1 -> v2:
- use %zu and %u in the format string for size_t
and u32 types (catched by the "kernel test robot").
- reworded commit message + successfully tested on QCA9880v2
I placed the nvmem code in front of the current "file"
Hi Mathias,
On 02/11/2021 23:08, Mathias Kresin wrote:
10/30/21 7:41 PM, Christian Lamparter:
--- a/drivers/net/wireless/ath/ath10k/ahb.c
+++ b/drivers/net/wireless/ath/ath10k/ahb.c
@@ -745,9 +745,11 @@ static int ath10k_ahb_probe(struct platform_device *pdev)
size = sizeof(*ar_pci
On 08/12/2021 13:21, Robert Marko wrote:
On Tue, 7 Dec 2021 at 19:06, Kalle Valo wrote:
Robert Marko wrote:
Some ath10k IPQ40xx devices like the MikroTik hAP ac2 and ac3 require the
BDF-s to be extracted from the device storage instead of shipping packaged
API 2 BDF-s.
This is required as
Hi,
On 16/02/2022 14:38, Robert Marko wrote:
Silent ping,
Does anybody have an opinion on this?
As a fallback, I've cobbled together from the old scripts that
"concat board.bin into a board-2.bin. Do this on the device
in userspace on the fly" idea. This was successfully tested
on one of the
Hi,
On 21/01/2022 15:09, Kalle Valo wrote:
Hans Geiblinger writes:
The support for this device is currently being added into OpenWrt. This AP
requires
two special BDFs to get the Wi-Fi PHYs working (correctly).
* description for what hardware this is:
- it is a QCA9888 based radio
On 26/02/2022 14:24, Kalle Valo wrote:
Josh Boyer writes:
On Wed, Feb 23, 2022 at 2:53 PM Christian Lamparter wrote:
syncs linux-firmware.git with the latest releases from Kalle Valo (QCA):
<https://github.com/kvalo/ath10k-firmware/tree/master/QCA4019/hw1.0>
Includes the following c
files
2d85666 QCA99X0 hw2.0: add board-2.bin
WHENCE updated accordingly.
Cc: Kalle Valo
Signed-off-by: Christian Lamparter
---
v1->v2: sent to linux-wireless + ath10k mailing list too (Valo)
---
WHENCE | 2 +-
ath10k/QCA99X0/hw2.0/board-2.bin | Bin 0 -> 157680 b
-2.bin
b44d86f QCA6174 hw3.0: update board-2.bin
8ba5ed7 QCA6174 hw3.0: update board-2.bin
3ce0d6d QCA6174 hw3.0: update board-2.bin
Cc: Kalle Valo
Signed-off-by: Christian Lamparter
---
v1->v2: sent to linux-wireless + ath10k mailing list too (Valo)
---
ath10k/QCA6174/hw3.0/board-2.bin | B
0: Add Linksys MR8300 V1.0 specific
BDFs
43ebf8e ath10k-firmware: QCA9984 hw1.0: Add NEC Platforms WG2600HP3 specific
BDFs
26dfc83 ath10k-firmware: QCA9984 hw1.0: Add Buffalo WTR-M2133HP specific BDF
Cc: Kalle Valo
Signed-off-by: Christian Lamparter
---
v1->v2: sent to linux-wireless + ath10
0: Add EnGenius EMR5000 specific BDFs
7ac0eb3 ath10k-firmware: QCA9888 hw2.0: Add EnGenius EAP2200 specific BDFs
75d699b ath10k-firmware: QCA9888 hw2.0: Update OpenMesh A62 specific BDFs
Cc: Kalle Valo
Signed-off-by: Christian Lamparter
---
v1->v2: sent to linux-wireless + ath10k mailing list
0: Add 8devices Habanero specific BDFs
38ebb2d ath10k-firmware: QCA4019 hw1.0: Add EnGenius EAP2200 specific BDFs
bc42587 ath10k-firmware: QCA4019 hw1.0: Update OpenMesh A42 specific BDFs
f305604 ath10k-firmware: QCA4019 hw1.0: Update OpenMesh A62 specific BDFs
Cc: Kalle Valo
Signed-off-by: Chr
Hi Kalle,
On 21/01/2022 15:05, Kalle Valo wrote:
Christian Lamparter writes:
this is a set of board.bin files for the ASRock G10,
which I wish to be added to the ath10k-firmware repository.
As per the current "Submitting board files" guidelines [1]:
* description for wha
From: Jeff Kletsky
This is a IPQ4019-based device with a PCI-attached QCA9888
supplying a third radio on 5 GHz. The OEM's firmware and source
suggest that this device is "based on Qualcomm AP DK07.1-c1"
Linksys ships four market-specific variants of this device, notated as
-AH, -EU, (no
From: Tim Davis
Hello,
This is the board files for P R619ac, a dual-band wireless router with an
IPQ4019 inside.
The boardfiles are extracted from the stock firmware:
/lib/firmware/IPQ4019/hw.1/boarddata_0.bin
/lib/firmware/IPQ4019/hw.1/boarddata_1.bin
The MD5 hashes are consistent with the
From: 张鹏 <1805692...@qq.com>
Modified the radio frequency hardware part of e2600ac c2,
need to cooperate with the modified board.bin file.
For the questions from the wiki page:
* description for what hardware this is:
it is a IPQ4019 based board (AP-DK04 and AP-DK07)
- one QCA40xx
From: Jeff Kletsky
This is a QCA4019-based device with a PCI-attached QCA9888
supplying a third radio on 5 GHz. The OEM's firmware and source
suggest that this device is "based on Qualcomm AP DK07.1-c1"
Linksys ships four market-specific variants of this device, notated as
-AH, -EU, (no
On 3/15/23 07:28, Kalle Valo wrote:
Christian Lamparter writes:
On 2/20/23 06:56, Kalle Valo wrote:
Christian Lamparter writes:
On 2/15/23 10:17, Kalle Valo wrote:
Here's a new pull request for ath10k and ath11k. We have new hardware
IPQ5018 and various updates for existing hardware
On 2/20/23 06:56, Kalle Valo wrote:
Christian Lamparter writes:
On 2/15/23 10:17, Kalle Valo wrote:
Here's a new pull request for ath10k and ath11k. We have new hardware
IPQ5018 and various updates for existing hardware. Especially many have
requested the firmware update for WCN6855 which
Hi Kalle,
On 2/15/23 10:17, Kalle Valo wrote:
Here's a new pull request for ath10k and ath11k. We have new hardware
IPQ5018 and various updates for existing hardware. Especially many have
requested the firmware update for WCN6855 which seems to fix an
important suspend problem.
Please let me
-freq-limit")
Signed-off-by: Christian Lamparter
---
Note: this is for ath10k. The other patch is for a different driver (ath11k).
---
.../devicetree/bindings/net/wireless/qcom,ath10k.yaml| 5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/wir
t;ath10k: limit available channels via DT
ieee80211-freq-limit")
Link:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=e3b8ae2b09e137ce2eae33551923daf302293a0c
Signed-off-by: Christian Lamparter
---
v1->v2:
- AllOf is a list. So add it to the existing one?
-
On 3/17/23 12:38, Kalle Valo wrote:
Giammarco Marzano writes:
this file is for add definition for ZTE MF289F.
The device is currently under review as PR on OpenWRT:
https://github.com/openwrt/openwrt/pull/10418
Please ignore my email of 3 August, this board binary add support for
5Ghz on
71 matches
Mail list logo
