Date: Sun, 19 Nov 2017 01:43:51 +0200 From: "Andriy Voskoboinyk" <s3erios@gmail.com> To: "Farhan Khan" <khanzf@gmail.com> Cc: freebsd-wireless@freebsd.org Subject: Re: rtwn card not delivering interrupts from beacon frames Message-ID: <op.y9xavdiziew4ia@localhost> In-Reply-To: <80883a0a-5ca3-0492-d10d-ceeb3fd41b4b@gmail.com>
index | next in thread | previous in thread | raw e-mail
Hi, For correct work pc_enable_intr / sc_start_xfers need to be adapted too; also, there may be need to utilize R88E_HIMRE / R88E_HISRE registers in addition to R88E_HIMR / R88E_HISR pair (see '8188 IMR/ISR bits' section in include/hal_com_reg.h in the vendor driver). > Hi all, > > As discussed, I am working on the rtwn rtl8188ee driver. Per Adrian's > advice, I am focusing on having the card reading beacon frames. I am > running the following tcpdump line, which works on another machine with > an rtwn card. > > # tcpdump -y IEEE802_11_RADIO -i wlan0 -e -s 256 type mgt > > Unfortunately, my card still does not receive beacon frames. Per IRC > conversations, this information is delivered to the driver via an > interrupt. > > I retracted my sc_init_intr code and found that the interrupt register > was incorrectly set, so I updated them per the Linux driver and started > having sc_classify_intr trigger very slowly (1-2 a minute), rather than > with every beacon frame from a nearby Access Point. The 'status' was set > to 0xffffffff, so it immediately exited. > > What might this mean? > > I am stuck and not certain why I am not receiving more beacon frames. I > have retraced the code, but am not finding what I might have left out. > Any ideas? I can show code if requested. Been on this driver for a > little more than a year now and would like to start making progress. :/ > > Thank you, > Farhan > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to > "freebsd-wireless-unsubscribe@freebsd.org"help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.y9xavdiziew4ia>