From owner-freebsd-wireless@freebsd.org Tue Nov 14 23:55:15 2017 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94116DB99E0 for ; Tue, 14 Nov 2017 23:55:15 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BBF575B0C for ; Tue, 14 Nov 2017 23:55:15 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: by mail-qt0-x232.google.com with SMTP id p44so20078028qtj.6 for ; Tue, 14 Nov 2017 15:55:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=6h8CpPyFi8gzAi5Uef8JvBzZSC3cmhv4IqxUssUWWDA=; b=ff+xunxoReAiI1PTQzS4SrMPLCDqudbbf9BRJfjDqrks4cQLIGdm2pdIKhir/CLiYW T3ZLq2o014+H2xkI3p4ZhrGOirTRbt70oICuU0NthC6/fdMDaVFfw3UdkHCg6/I55Pj1 N1y9xfEd0qg18tFQfn/SSk91nsxX79k0K0K3o9r6sttsBPzAgFVnRD4yG+OVHwfbBa9U Ht7XSeeWVue41L5pnrOOKh1EPtFrnJEsRJ3fi1YEPVqF3vFKpppOzmQIInaJlmZD4oe8 sPqPGWjkzPMFnZUgNg/aq+MJwG/dNJX5ReNL2LCg4ZwKeTXWa3+pWh1TV9HLVwKr1uk5 rlYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=6h8CpPyFi8gzAi5Uef8JvBzZSC3cmhv4IqxUssUWWDA=; b=Q8AE7IKggU/Rn+nLJWIs4SLFNNtu28W9edoxbntWPc2CNJYfV9NRvQC3R0cbBggndE EmfqOwatv02cvGe4DPgsA/P6mJL+czqeA+6XJ63s8m9N6H+B1QaBLD7yao5VKFXgxsBe jA5LdENWJhpKhhcZ0rLT4cvJ+x92roussGGScT+e4QSrUy3bB/pNoGd41/FFKhWlQeXV X9Ml4jJrxlOYKzJRXfzTUmycG0qwEmIl9Vgb1HBiunoq6OvfnJEfDHRMJYNT7RJ7pfDT I119jMS9TvOSX20xNiYdZGcEzFEixhmiV4ZYI8fu/y+4AH3ipwR7MjLm/xknpQasfmHQ 41Ow== X-Gm-Message-State: AJaThX43WOvsd2/9Lqgh0n2hFRumIl698eOPQKjuU8Uyxy8lylvLHyfh Fl7zbOzJXzY3oegyTXG0lHfUc0u6 X-Google-Smtp-Source: AGs4zMYjrBtiVtxM23HHrlw4PcjIDyNSnThZDf9Kr5V5Na5tWj1s8bY7k4kejvz4BZvT/LCISx2Qog== X-Received: by 10.55.146.65 with SMTP id u62mr8485834qkd.112.1510703714067; Tue, 14 Nov 2017 15:55:14 -0800 (PST) Received: from pc.farhan.codes ([2001:470:8:209::dead:c0de]) by smtp.gmail.com with ESMTPSA id e96sm9775480qtb.84.2017.11.14.15.55.13 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Nov 2017 15:55:13 -0800 (PST) From: Farhan Khan Subject: rtwn card not delivering interrupts from beacon frames To: freebsd-wireless@freebsd.org Message-ID: <80883a0a-5ca3-0492-d10d-ceeb3fd41b4b@gmail.com> Date: Tue, 14 Nov 2017 18:55:13 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 23:55:15 -0000 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