From owner-freebsd-wireless@freebsd.org Sat Nov 18 23:47:28 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 D468EDDFC89 for ; Sat, 18 Nov 2017 23:47:28 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 567E5227E for ; Sat, 18 Nov 2017 23:47:28 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id e143so6348853lfg.12 for ; Sat, 18 Nov 2017 15:47:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=PlSm4uwhFgFaMST8HJK7XkZ9F8vcDhbFpCmxQ6qlvPU=; b=UTJM6690h4Dl26mLQvVJz3twcviE3941iRAtRUNekCZCKTrKSRQsBRhKl3gwYhnz6G wz+SqOmBNdl4cmNl7rQxrqfVqlwWzaKVud2vqsr/uq3SRpYdV+EWRnzUb0EbTQBikwDr EUTQn4qgwRrZGP/q79vtx6mzFdVhEGswCyYoRrrvKRYGX9t9VgVwViENsXfqgjG6WGAZ MjfH4cm9gFcVHpjj6xiRvrzk0ayd7PbPNRyvyUmMtw7arqjSRieVUtW0PHSLHU6v6VYz hCGjIp3FieQbWnl2IRQGLt4JdzDbSWYFPs71nmR84M8o69LqV401EkOrk8+odE/WTNXb TFXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=PlSm4uwhFgFaMST8HJK7XkZ9F8vcDhbFpCmxQ6qlvPU=; b=X6apXoToM8YiMpm0tl9CGJONVGxrdwOVTiJKqE6zrcFVu+98cbKPfQmGUApV9Ls8bw DmnDh8FQchlWiq9zm4PetV7XR5n3ALTjBoR/k+UBvYyA+B0hA7B/E4gKFnDjticl9U/2 059+owo9n9Yz1exKFGgSynE2TC172AXkGGa9VGvq8rpT0RL2PJuvO2hnQgWnJQ3/pSOs eyF0iQoqbXygtiWgwQa0EaDXoidPav000ATTvg1c5Lh091czF8b3uYZvovIc0E2EBx3c QgWXX+Jnt7x4pZuIPyFf9eTU41MgMEpVC0nav6zd7wUfHlhHaZozDOYLU4rnYZrg7CzD q2Jg== X-Gm-Message-State: AJaThX7KPCSRuJZ+GZSH2/r7uvoFOGwzb+rHyvHFFM/I6W3pm85cn8fl EZXhF+2rAbCZgwE5XJd19AA= X-Google-Smtp-Source: AGs4zMbAY4BGhHCy0u63xiAQRv09e08J4rbFS41VKsWh8E+sb0bzeC0xg7BXD2VSuGFf1LTWpubI+Q== X-Received: by 10.46.41.212 with SMTP id p81mr2407299ljp.173.1511048846032; Sat, 18 Nov 2017 15:47:26 -0800 (PST) Received: from localhost (46-133-109-44.dialup.umc.net.ua. [46.133.109.44]) by smtp.gmail.com with ESMTPSA id 2sm1693910lju.17.2017.11.18.15.47.24 (version=TLS1 cipher=AES128-SHA bits=128/128); Sat, 18 Nov 2017 15:47:25 -0800 (PST) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Farhan Khan" Subject: Re: rtwn card not delivering interrupts from beacon frames References: <80883a0a-5ca3-0492-d10d-ceeb3fd41b4b@gmail.com> Date: Sun, 19 Nov 2017 01:43:51 +0200 Cc: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <80883a0a-5ca3-0492-d10d-ceeb3fd41b4b@gmail.com> User-Agent: Opera Mail/12.15 (FreeBSD) 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: Sat, 18 Nov 2017 23:47:28 -0000 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"