Al 08/09/13 18:08, En/na Luca Olivetti ha escrit:
> As per the subject, the function ath_pci_fixup (in
> arch/mips/lantiq/xway/pci-ath-fixup.c) is called very early in the boot
> process, before ath9k_eeprom_probe (in arch/mips/lantiq/xway/ath_eep.c)
> has had any possibility to call ltq_pci_ath_fixup.
> The net result is that the fixup isn't done and the wireless adapter
> doesn't work.
> What can I change to revert the order of those calls? (i'm lost in the
> 75 levels of indirection, I had it working 3 years ago but then the
> levels of indirection where only 63 ;-)
Found the solution, change the call from
late_initcall(of_ath9k_eeprom_init)
to
subsys_initcall(of_ath9k_eeprom_init).
Now I have to see why it doesn't get the mac address and the regdomain
from the eeprom (things, again, that I had working but it seems this
platform is an easy target for being broken again and again).
Bye
--
Luca
Index: target/linux/lantiq/patches-3.8/0037-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch
===================================================================
--- target/linux/lantiq/patches-3.8/0037-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch (revisión: 37909)
+++ target/linux/lantiq/patches-3.8/0037-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch (copia de trabajo)
@@ -202,7 +202,7 @@
+{
+ return platform_driver_probe(&ath9k_eeprom_driver, of_ath9k_eeprom_probe);
+}
-+late_initcall(of_ath9k_eeprom_init);
++subsys_initcall(of_ath9k_eeprom_init);
+
+
+static int ath5k_pci_plat_dev_init(struct pci_dev *dev)
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
