> On Thu, 25 Jun 2015 20:59:19 +0200, Matti Laakso <malaakso at elisanet.fi > <https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel>> > wrote: > > >>/ ------------------------------------------------------------------------ > />>/ On 22/06/15 20:19, Matti Laakso wrote: > />>/ >/ These patches backport the new FW API v5 to ath10k > />>/ />/ (upstream commits 8348db2, 53513c3, and dc3632a) > />>/ />/ and change mac80211 to use the new firmware. > />>/ />/ > />>/ />/ > />>/ /Could you also update > />>/ target/linux/ar71xx/base-files/lib/preinit/82_patch_ath10k? > />>/ See https://patchwork.ozlabs.org/patch/466945/ and possibly > />>/ https://patchwork.ozlabs.org/patch/481472/ > />>/ > />>/ Thanks, > />>/ Stijn > />/ > />/ Hi, > />/ > />/ That seems like a burden to maintain. Do I understand correctly that the > />/ device has valid data in the PCIe card EEPROM (so it is not necessary to > />/ create a file with the calibration data in 81_load_ath10k_board_bin), > />/ but the MAC is incorrect? Is the MAC completely bogus (like same for all > />/ devices), or valid but just not what it says on the router cover? If the > />/ latter, I'd like to drop the whole script altogether and just live with > />/ a different MAC. > / > On the dgl5500 the mac in the eeprom is the same on all devices (and iirc > it's the default mac the firmware also uses). Patching it to the right one > in the firmware file is what happens in 82_patch_ath10k. > > > Imre
That's... interesting. I'll make v2 with a patched 82_patch_ath10k then, unless someone can think of a better way to provide a proper MAC for the board. Matti _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
