lantiq: fix patching the wifi mac address on BTHOMEHUBV3A
The firmware hotplug script tries to read the mac address from a
partition with the name "uboot-env" which does not exist (instead it's
name is uboot_env). This broke calculation of the new checksum (after
patching the mac address) which resulted in ath9k refusing to use the
EEPROM data.
The original error reported by ath9k was:
PCI: Enabling device 0000:00:0e.0 (0000 -> 0002)
ath: phy0: Bad EEPROM checksum 0x2523
ath: phy0: Unable to initialize hardware; initialization status: -22
ath9k 0000:00:0e.0: Failed to initialize device
Fixes: a20616863d
("lantiq: use ath9k device tree bindings
binding/owl-loader")
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
This commit is contained in:
parent
4c09f99605
commit
70395ae8cb
1 changed files with 1 additions and 1 deletions
|
@ -129,7 +129,7 @@ case "$FIRMWARE" in
|
||||||
;;
|
;;
|
||||||
BTHOMEHUBV3A)
|
BTHOMEHUBV3A)
|
||||||
ath9k_eeprom_extract "art-copy" 0 1
|
ath9k_eeprom_extract "art-copy" 0 1
|
||||||
ath9k_patch_fw_mac_crc $(macaddr_add $(mtd_get_mac_ascii uboot-env ethaddr) +2) 268
|
ath9k_patch_fw_mac_crc $(macaddr_add $(mtd_get_mac_ascii uboot_env ethaddr) +2) 268
|
||||||
;;
|
;;
|
||||||
BTHOMEHUBV5A)
|
BTHOMEHUBV5A)
|
||||||
ath9k_ubi_eeprom_extract "caldata" 4096 0
|
ath9k_ubi_eeprom_extract "caldata" 4096 0
|
||||||
|
|
Loading…
Reference in a new issue