aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ath79/base-files/etc/board.d/02_network
diff options
context:
space:
mode:
authorChristian Lamparter <chunkeey@gmail.com>2018-08-10 23:24:48 +0200
committerMathias Kresin <dev@kresin.me>2018-08-11 21:36:27 +0200
commita441c86d93657121afe8117f8329b7095f7154d2 (patch)
treee33e61c6fd6bb46bd554c4eb54172c19aede7405 /target/linux/ath79/base-files/etc/board.d/02_network
parentdfee452713e6b3c10aafc6174f8087a920b54402 (diff)
downloadupstream-a441c86d93657121afe8117f8329b7095f7154d2.tar.gz
upstream-a441c86d93657121afe8117f8329b7095f7154d2.tar.bz2
upstream-a441c86d93657121afe8117f8329b7095f7154d2.zip
ath79: add ath9k calibration data MAC addresses patching
This patch copies over the MAC patching helper functions from lantiq's target/linux/lantiq/base-files/etc/hotplug.d/firmware/12-ath9k-eeprom file. Not all vendors bothered to write the correct MAC addresses for the ath9k wifi into the calibration data. And while ath9k does have some special dt-properties to extract the addresses from a fixed position, there are still devices that require userspace to edit or modify the caldata. In my case, the MAC address for the Wi-Fi device is stored in an unsorted key-value based "nvram" database and there's an existing userspace tool to extract the data. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Diffstat (limited to 'target/linux/ath79/base-files/etc/board.d/02_network')
0 files changed, 0 insertions, 0 deletions