diff options
author | Martin Blumenstingl <martin.blumenstingl@googlemail.com> | 2016-09-18 23:29:35 +0200 |
---|---|---|
committer | Felix Fietkau <nbd@nbd.name> | 2016-09-28 08:39:01 +0200 |
commit | e7be0decf65a2d3ecbe344bcb172151516815935 (patch) | |
tree | 397c360ae5f244c05180d5ffa58d60add85ef915 /package/base-files/files/etc/hotplug.d/net | |
parent | 3fbd235fb5484236393341f168d927c7a6feb3f4 (diff) | |
download | master-31e0f0ae-e7be0decf65a2d3ecbe344bcb172151516815935.tar.gz master-31e0f0ae-e7be0decf65a2d3ecbe344bcb172151516815935.tar.bz2 master-31e0f0ae-e7be0decf65a2d3ecbe344bcb172151516815935.zip |
ar71xx: Do not use a hardcoded ath10k firmware mac address
ar71xx has an init-script for special devices where the ath10k OTP
calibration data is stored on the PCIe card's EEPROM (and thus can only
be read by ath10k). Unfortunately the OTP data uses the default mac
address (= all devices come with the same mac address, which leads to
problems when you have multiple of these devices in the same network).
To work around this the mac address is patched in the firmware during
the first boot of the device. To prevent flash wear this was only done
if the ath10k firmware matched a hardcoded md5sum.
However, if the md5sum does not match this can mean that either the mac
address was already patched (which is fine) - unfortunately it can also
mean that the firmware version was updated without updating the
hardcoded md5sum.
Change the "was the mac address already patched" check to actually
compare the mac address inside the ath10k firmware.
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Diffstat (limited to 'package/base-files/files/etc/hotplug.d/net')
0 files changed, 0 insertions, 0 deletions