On Tue, Feb 4, 2014 at 8:24 PM, Roman Yeryomin <[email protected]> wrote: > On 4 February 2014 19:58, Helmut Schaa <[email protected]> wrote: >> On Tue, Feb 4, 2014 at 5:19 PM, Roman Yeryomin <[email protected]> wrote: >>> On 4 February 2014 17:56, Helmut Schaa <[email protected]> wrote: >>>>>>> Currently wifi interface appears in the system and can be enabled but >>>>>>> `iw dev wlan0 scan' gives no result and wlan0 transmits one packet >>>>>>> roughly in 10 minutes as per ifconfig (ssid doesn't appear in the >>>>>>> air). >>>>>>> `iw phy' output looks like this: >>>>>> >>>>>> Maybe you should start with a simple monitor interface to get the RX >>>>>> path working (iw phy phy0 interface add mon0 type monitor). >>>>>> Just run a tcpdump on mon0 and see if you can receive something (with >>>>>> your patches applied). >>>>> >>>>> Unfortunately it doesn't give any results. >>>>> Also rx counter was always zero - I forgot to mention that. >>>>> What I thought was suspicious is "Available Antennas: TX 0 RX 0" in iw >>>>> phy output, but I've checked other chips which do work and they all >>>>> have the same record. >>>> >>>> Yeah, rt2x00 does not initialize these AFAIK. >>>> >>>> So, you ported the code from the ralink rt2860 driver, right? >>>> I haven't looked into newer ralink chips at all. Did you check if any MAC >>>> layer changes regarding RX and TX rings exist? >>> >>> Yes, from rt2860v2 2.7.1.6 to be precise. >>> Yes I did the mac registers init too. There are several new registers >>> they initialize. I tried to integrate mac init to the existing >>> function. Do you think I should try to do it separately? >> >> No, should be fine that way (for testing) I guess. >> >> Did you check if the interrupt handler is called after setting the >> device up (/proc/interrupts)? >> Just as a first evidence of life? > > Hmm.. > If I configure it as ap, yes: > CPU0 > 5: 28 MIPS 10100000.ethernet > 6: 38912 MIPS rt2800_wmac > 7: 204558 MIPS timer > 9: 0 INTC 10000100.timer > 20: 521 INTC serial > 25: 2 INTC gsw > ERR: 0
Good, so at least something happens :D Might make sense to add some code to the interrupt handler to see which interrupts get fired. > But if I put it in monitor mode (either via config or iw command) > interrupt counter remains zero. What does it mean? So, it seems as if the RX path is not working at all. But that can have several reasons ... Did you check with a second wifi device if the card transmits any frames in AP mode? Beacons? Helmut _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
