Hello, So with some modifications to pci.c, hw.h and core.c I was able to get the radio initialized! :)
pci.c: added QCA9887_DEVICE_ID, modified ath10k_pci_id_table and ath10k_pci_supp_chips core.c: Duplicated QCA988X entry in ath10k_hw_params_list and passed 0x4100016d as the ID ( left everything else the same ) hw.h: added definitions for QCA9887 I found "https://github.com/kvalo/ath10k-firmware/blob/master/QCA9887/firmware-5.bin_10.2.3.31.7-1"; on your github and replaced /lib/firmware/ath10k/QCA988X/hw2.0/firmware-5.bin on my board. hotplug.d then loaded QCA9887 firmware on next boot. Of course my approach was very much a hack. If there is anything I can contribute to creating a patch for ath10k, please let me know. I would love to help! dmesg [ 18.920000] ath10k_pci 0000:00:00.0: pci irq legacy interrupts 0 irq_mode 0 reset_mode 0 [ 19.030000] rev_id 00000000 QCA9887 [ 19.030000] dev_id 00000050 QCA9887 [ 20.460000] ath10k_pci 0000:00:00.0: qca988x hw2.0 (0x4100016d, 0x004000ff sub 0000:0000) fw 10.2.3.31.7-1 fwapi 5 bdapi 1 htt-ver 2.1 wmi-op 5 htt-op 2 cal file max-sta 1p [ 20.480000] ath10k_pci 0000:00:00.0: debug 1 debugfs 1 tracing 0 dfs 0 testmode 1 iw phy phy1 info Wiphy phy1 max # scan SSIDs: 16 max scan IEs length: 199 bytes Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports AP-side u-APSD. Available Antennas: TX 0x1 RX 0x1 Configured Antennas: TX 0x1 RX 0x1 Supported interface modes: * managed * AP * AP/VLAN * monitor * mesh point Band 2: Capabilities: 0x19e3 RX LDPC HT20/HT40 Static SM Power Save RX HT20 SGI RX HT40 SGI TX STBC RX STBC 1-stream Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 8 usec (0x06) HT TX/RX MCS rate indexes supported: 0-7 VHT Capabilities (0x338001b2): Max MPDU length: 11454 Supported Channel Width: neither 160 nor 80+80 RX LDPC short GI (80 MHz) TX STBC RX antenna pattern consistency TX antenna pattern consistency VHT RX MCS set: 1 streams: MCS 0-9 2 streams: not supported 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT RX highest supported: 0 Mbps VHT TX MCS set: 1 streams: MCS 0-9 2 streams: not supported 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT TX highest supported: 0 Mbps Frequencies: * 5180 MHz [36] (23.0 dBm) * 5200 MHz [40] (23.0 dBm) * 5220 MHz [44] (23.0 dBm) * 5240 MHz [48] (23.0 dBm) * 5260 MHz [52] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5280 MHz [56] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5300 MHz [60] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5320 MHz [64] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5500 MHz [100] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5520 MHz [104] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5540 MHz [108] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5560 MHz [112] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5580 MHz [116] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5600 MHz [120] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5620 MHz [124] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5640 MHz [128] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5660 MHz [132] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5680 MHz [136] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5700 MHz [140] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5720 MHz [144] (23.0 dBm) (radar detection) DFS state: usable (for 39 sec) DFS CAC time: 60000 ms * 5745 MHz [149] (30.0 dBm) * 5765 MHz [153] (30.0 dBm) * 5785 MHz [157] (30.0 dBm) * 5805 MHz [161] (30.0 dBm) * 5825 MHz [165] (30.0 dBm) valid interface combinations: * #{ AP, mesh point } <= 8, total <= 8, #channels <= 1, STA/AP BI must match HT Capability overrides: * MCS: ff ff ff ff ff ff ff ff ff ff * maximum A-MSDU length * supported channel width * short GI for 40 MHz * max A-MPDU length exponent * min MPDU start spacing -- Davey On Mon, Apr 25, 2016 at 9:21 AM, Valo, Kalle <kv...@qca.qualcomm.com> wrote: > Christian Lamparter <chunk...@googlemail.com> writes: > >> 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 table [0] and there's no definition of it in the hardware >> header either [1]. The chip-id is also not present. I CC'ed ath10k, since >> this seems to be a new chip that might be easy to add. > > Currently ath10k does not support QCA9887. > > -- > Kalle Valo _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
