On Sun, May 8, 2016 at 10:33 AM, Sebastian Ortwein <k...@animeland.de> wrote: > I get the eeprom from the ath9k driver working, but wifi will not showed. > First, I get a error message that from the ath9k driver that the eeprom > couldn't load. After PCI Bus is initialize the eeprom is loaded. That is "normal" - nothing to worry about here.
> [ 1.188886] found entry name -> annex=B > [ 1.192650] found entry name -> maca=BC:05:43:D7:1E:7C > [ 1.197738] found entry name -> macb=BC:05:43:D7:1E:7D > [ 1.202875] found entry name -> macwlan=BC:05:43:D7:1E:7E > [ 1.208269] found entry name -> macdsl=BC:05:43:D7:1E:7F > [ 1.213632] found entry name -> macwlan2=BC:05:43:D7:1E:81 > [ 1.219063] found entry name -> wlan_key=4004584479108575 > [ 1.227509] ath9k,eeprom ath9k_eep: endian check enabled. > [ 1.231483] ath9k,eeprom ath9k_eep: using random mac > [ 1.236475] ath9k,eeprom ath9k_eep: loaded ath9k eeprom > [ 1.246508] UBIFS error (pid: 1): cannot open "ubi0:rootfs", error -19 > [ 1.257496] VFS: Mounted root (squashfs filesystem) readonly on device > 31:3. > [ 1.265035] Freeing unused kernel memory: 1224K (804fe000 - 80630000) > [ 2.475280] init: Console is alive > ............. > > As you can see OpenWrt will find the mac-adesses from all devices, how can I > asign it in the dts file? I think you can't (at least not with the current tffs driver). All it currently does is printing the mac addresses: [0] My fritz_tffs_read tool is userspace only. The only downside is that you currently cannot userspace tools to set the mac address in the ath9k calibration data. We would need a solution like Christian's OWL-loader, see [1] (or another TFFS kernel driver). > The wiki is right. I will upload some images to the openwrt Wiki when the > box is working. > But phy0 and phy1 works only somtimes. In my dts file I assigned the reset > GPIO's like in the FRITZ3370.dts file. > I have take GPIO config from the AVM GPL sources. Is there anything I forgot > orwrong in my new DTS file ? I think the GPIOs definition is in the wrong place - it has to be per PHY (thus you should put it into the mdio@0 section below). I cannot see any ath9k messages in your kernel log - are you sure it's being installed (/lib/modules/*/ath9k.ko)? Your first patch lists kmod-ath9k, but if you added that after you generated your .config then you're probably still missing it. Please check "grep kmod-ath9k .config" and enable (set it to =y/built-in) it if it's missing. Martin [0] https://github.com/openwrt/openwrt/blob/master/target/linux/lantiq/patches-4.4/0007-MIPS-lantiq-add-basic-tffs-driver.patch [1] https://lists.openwrt.org/pipermail/openwrt-devel/2016-April/040755.html _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
