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 the tables. You could just go ahead and post it, so it will be picked up. > 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 > ... Does the device work? Can you scan for networks, connect to networks and create networks? That would be good to know. Regards, Christian _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
