On 6 February 2014 13:01, Helmut Schaa <helmut.sc...@googlemail.com> wrote: > On Thu, Feb 6, 2014 at 11:40 AM, Roman Yeryomin <leroi.li...@gmail.com> wrote: >> On 5 February 2014 09:21, Helmut Schaa <helmut.sc...@googlemail.com> wrote: >>>>>>> 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. >> >> Do you mean plat_irq_dispatch() from arch/mips/ralink/irq.c ? > > I thought about rt2800mmio_interrupt.
then it's these two: INT_SOURCE_CSR_TBTT INT_SOURCE_CSR_PRE_TBTT >>>> 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? >> >> Only with android tablet with wifi scanner. Do you think I should try >> a better scanner (kismet?) ? > > Just use a second linux machine with a reasonable wifi card (ath9k > will do for example), > put it into monitor mode and run tcpdump/wireshark on it ... I will check it little bit later today. Regards, Roman _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel