#20218: No VALID WLAN MAC-ADDR on brcm63xx (WAG325N) with miniPCI AR5416
-------------------------------------------------+-------------------------
Reporter: anonymous | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Chaos
Component: kernel | Calmer (trunk)
Keywords: ATH9K BRCM63XX AR5416 NO MAC ON | Version: Trunk
SPECIAL MINIPCI CARD |
-------------------------------------------------+-------------------------
The WLAN-macaddr is not correctly assigned by using
a "long" AR5416 miniPCI Card in a WAG325N and other Linksys Routers.
This PCI-Card has no mac-address in it´s customized eeprom, so ath9k ets
the adress to 01:02:03:04:05:06
Alternative is a 00:90er fake/unprogrammed mac-addr inside eeprom.
miniPCI-cards on brcm63xx are not using "ath9k-pci-fixup.c",
so this situation is still not correctly handled.
The variable "nvram_get_mac_address" is correctly filled up by the real
mac from the cfe NVRAM and can be used.
Can the ath9k driver itself enhanced, to check this variable and use it
for such "non-standard" cards, or in case, the eeprom from a miniPCI card
has no valid mac-addr ?
Means: use the known base-mac++ and give the wlan a real IP
instead a fake one.
I found the same problem on orion platform and some brcm47xx, too, which
is using the linksys AR5416 "long" card.
Here are one of the problematic cards:
phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81 mem=0xc0b80000, irq=39
--
Ticket URL: <https://dev.openwrt.org/ticket/20218>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
