From owner-freebsd-wireless@freebsd.org Sun Oct 27 21:00:55 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 268A71A6615 for ; Sun, 27 Oct 2019 21:00:55 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 471Vck6MXtz47h4 for ; Sun, 27 Oct 2019 21:00:54 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id D0E861A660C; Sun, 27 Oct 2019 21:00:54 +0000 (UTC) Delivered-To: wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D047F1A660A for ; Sun, 27 Oct 2019 21:00:54 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 471Vck3G8Gz47gn for ; Sun, 27 Oct 2019 21:00:54 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 53B4627007 for ; Sun, 27 Oct 2019 21:00:54 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x9RL0sve022889 for ; Sun, 27 Oct 2019 21:00:54 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x9RL0s3L022872 for wireless@FreeBSD.org; Sun, 27 Oct 2019 21:00:54 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201910272100.x9RL0s3L022872@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: wireless@FreeBSD.org Subject: Problem reports for wireless@FreeBSD.org that need special attention Date: Sun, 27 Oct 2019 21:00:54 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 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: Sun, 27 Oct 2019 21:00:55 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 237921 | wpi: Memory leak in function wpi_free_tx_ring of Open | 154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open | 236918 | Crash: in iwn_ampdu_tx_stop (or ieee80211_ht_node Open | 238636 | ath: Fix kernel addresses printed in if_ath_sysct Open | 240776 | iwm: Can't find wifi networks after short time si 5 problems total for which you should take action. From owner-freebsd-wireless@freebsd.org Mon Oct 28 10:40:54 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 696DB17DACE for ; Mon, 28 Oct 2019 10:40:54 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 471rps4PmKz3J2F for ; Mon, 28 Oct 2019 10:40:53 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 68A4B8D4A224 for ; Mon, 28 Oct 2019 10:40:46 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id EAED3E707B3 for ; Mon, 28 Oct 2019 10:40:45 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id F2A0kAQyGPnz for ; Mon, 28 Oct 2019 10:40:44 +0000 (UTC) Received: from [192.168.2.110] (unknown [IPv6:fde9:577b:c1a9:31:491c:92a7:1e42:71c8]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id B316AD21C68 for ; Mon, 28 Oct 2019 10:40:44 +0000 (UTC) From: "Bjoern A. Zeeb" To: freebsd-wireless@freebsd.org Subject: Looking for an official Raspberry Pi USB WiFi Dongle? Date: Mon, 28 Oct 2019 10:40:44 +0000 X-Mailer: MailMate (2.0BETAr6142) Message-ID: <3E2E38D6-363D-417B-A0A1-F48252C43D48@lists.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 471rps4PmKz3J2F X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 195.201.62.131 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net X-Spamd-Result: default: False [-4.08 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.201.62.131]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[zabbadoz.net]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.78)[ip: (-8.57), ipnet: 195.201.0.0/16(-3.55), asn: 24940(-1.79), country: DE(-0.01)] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 28 Oct 2019 10:40:54 -0000 Hi, I know there’s a lot of USB Wifi dongles out there. I am specifically looking for an official Raspberry Pi USB WiFi Dongle (which are discontinued): https://www.raspberrypi.org/products/raspberry-pi-usb-wifi-dongle/ In case anyone has one by accident and no longer needs it (or is willing to sell it) please contact me off-list. Thanks! Bjoern From owner-freebsd-wireless@freebsd.org Wed Oct 30 17:00:25 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E207B15B022 for ; Wed, 30 Oct 2019 17:00:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 473F7s5X72z4FPy for ; Wed, 30 Oct 2019 17:00:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id BBEAB15B021; Wed, 30 Oct 2019 17:00:25 +0000 (UTC) Delivered-To: wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BB9F515B020 for ; Wed, 30 Oct 2019 17:00:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 473F7s4Tn3z4FPx for ; Wed, 30 Oct 2019 17:00:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7E819D5EC for ; Wed, 30 Oct 2019 17:00:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x9UH0PsC028160 for ; Wed, 30 Oct 2019 17:00:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x9UH0PZ2028159 for wireless@FreeBSD.org; Wed, 30 Oct 2019 17:00:25 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 227044] Add support for Intel 9260 and 5165 (iwm) wireless devices Date: Wed, 30 Oct 2019 17:00:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: feature, needs-patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: markj@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: markj@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 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: Wed, 30 Oct 2019 17:00:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227044 Mark Johnston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress Assignee|wireless@FreeBSD.org |markj@FreeBSD.org --- Comment #8 from Mark Johnston --- I managed to get iwm to work with the 9560 chip in a 7th gen X1 carbon, building on the work from lwhsu and wjguo. Some fairly substantial changes= are needed to the rx path among other things. I will work on getting the combi= ned patch set into HEAD. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Wed Oct 30 22:52:23 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BC2CF16445B for ; Wed, 30 Oct 2019 22:52:23 +0000 (UTC) (envelope-from ashafer@badland.io) Received: from badland.io (badland.io [178.128.156.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 473Nxy4hn3z4hgG for ; Wed, 30 Oct 2019 22:52:22 +0000 (UTC) (envelope-from ashafer@badland.io) Received: from amadeus.attlocal.net (68-74-197-208.lightspeed.rlghnc.sbcglobal.net [68.74.197.208]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by badland.io (Postfix) with ESMTPSA id 2A0F7A9832 for ; Wed, 30 Oct 2019 18:52:14 -0400 (EDT) From: Austin Shafer Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Best way to explore the 802.11 rtwn source code? Message-Id: <1F9F7008-59C4-42DF-AF1E-0028BD9576F5@badland.io> Date: Wed, 30 Oct 2019 18:52:15 -0400 To: freebsd-wireless@freebsd.org X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 473Nxy4hn3z4hgG X-Spamd-Bar: / X-Spamd-Result: default: False [-0.73 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[badland.io:s=dkim]; RECEIVED_SPAMHAUS_PBL(0.00)[208.197.74.68.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.82)[-0.821,0]; IP_SCORE(0.37)[asn: 14061(1.92), country: US(-0.05)]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[badland.io:+]; DMARC_POLICY_ALLOW(-0.50)[badland.io,reject]; NEURAL_HAM_MEDIUM(-0.79)[-0.787,0]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:178.128.144.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 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: Wed, 30 Oct 2019 22:52:23 -0000 Hi all, I=E2=80=99m interested in hacking around with a netgear wifi adapter I = have (rtwn). Are there any good resources for learning how to read and = debug FreeBSD=E2=80=99s wireless network stack? Robert Watson has a great overview of starting points for understanding = the kernel as a whole, are there any similar "starting points" for = network drivers? http://www.watson.org/~robert/freebsd/reading/ The =E2=80=9CDesign and implementation ..=E2=80=9D book covers = networking and device driver creation which is helpful, but nothing = about wireless. I did find a few like the following: https://wiki.freebsd.org/MateuszPiotrowski/Drivers https://wiki.freebsd.org/WiFi/BringUp Any suggestions? I=E2=80=99d appreciate anything that helps me learn how = all this stuff works. Thanks in advance, Austin= From owner-freebsd-wireless@freebsd.org Thu Oct 31 04:49:37 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2F6C7178BDE for ; Thu, 31 Oct 2019 04:49:37 +0000 (UTC) (envelope-from farhan@farhan.codes) Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 473Xt72pPjz3J6Q for ; Thu, 31 Oct 2019 04:49:35 +0000 (UTC) (envelope-from farhan@farhan.codes) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id 5FCD47447; Thu, 31 Oct 2019 00:49:34 -0400 (EDT) Received: from imap22 ([10.202.2.72]) by compute5.internal (MEProxy); Thu, 31 Oct 2019 00:49:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=farhan.codes; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm1; bh=qycX9 e7N9ZuySp67PxEeyjjl9r3Ta8aYcPkjoLWSXxI=; b=FFQSFW97fLITrBcdzVSJL jkUGs+vIibMIHNrqCp3+AayFRm9E/sNxoww4y1GKHLTbgS5TBetPyaxhZQ/q5jE3 El8tmm6n31G/c+hv+xHNikts2MwlVC4Wr494SAucPEFmoVNEG/RhyLbFZ8XeEVJM zPsN5FxRxaBUNP0Ws1i/dKMY9neq8rEFzre0JBhiFkkVG5+uwIwZgqxuN1L2T8cE 9X/nutLlnyggmRyrWVv0yf7pmDMsSwtddeE5SivS4vraIGDLAZnEsMmwneIGFbul inXl76mGxHgsRpcdVihGttXbrU/+PDLKNt/svKraSnvv/7TUm1vUKohh9fRdFRq2 w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=qycX9e7N9ZuySp67PxEeyjjl9r3Ta8aYcPkjoLWSX xI=; b=ZMocr/rgVCQUTd60WA6ZH06LoECDSx0uq2dKnShNfIPgPX3lN9vO3ESvR AUCxrzVKGsbXpLFVwvKoibXvTHJriTtO4q6n5u4SaSTk0YCjXdDjzLPX60M3n1y9 dunpoPu+b5TzJNn/sUn/0EEVNiFI/JdBvmnHq0iJa6HWw/8vOJxld9QpXZ9QKdB2 /kuowe6+1+LYfpGv0JqIS0j+1iuHG7hVBhfUZW9HvwYvL0/zF1+z4cinAt24xm84 u+f1/ne6yUAta2j7i2v72kmoC0l+Z8s4YuRebzb897mKUx/ycZ+y5aK4kKX1Mdq0 O1f/saXeym5r8Yi3j9ga4jONw58VQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddtgedgjeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtgfesth hqredtreerjeenucfhrhhomhepfdfhrghrhhgrnhcumfhhrghnfdcuoehfrghrhhgrnhes fhgrrhhhrghnrdgtohguvghsqeenucffohhmrghinhepfhhrvggvsghsugdrohhrghdpfi grthhsohhnrdhorhhgnecurfgrrhgrmhepmhgrihhlfhhrohhmpehfrghrhhgrnhesfhgr rhhhrghnrdgtohguvghsnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9F866668005F; Thu, 31 Oct 2019 00:49:33 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-509-ge3ec61c-fmstable-20191030v1 Mime-Version: 1.0 Message-Id: In-Reply-To: <1F9F7008-59C4-42DF-AF1E-0028BD9576F5@badland.io> References: <1F9F7008-59C4-42DF-AF1E-0028BD9576F5@badland.io> Date: Thu, 31 Oct 2019 00:49:13 -0400 From: "Farhan Khan" To: freebsd-wireless@freebsd.org, ashafer@badland.io Subject: Re: Best way to explore the 802.11 rtwn source code? Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 473Xt72pPjz3J6Q X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=farhan.codes header.s=fm1 header.b=FFQSFW97; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=ZMocr/rg; dmarc=none; spf=pass (mx1.freebsd.org: domain of farhan@farhan.codes designates 66.111.4.224 as permitted sender) smtp.mailfrom=farhan@farhan.codes X-Spamd-Result: default: False [-3.58 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[farhan.codes:s=fm1,messagingengine.com:s=fm1]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.224]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[farhan.codes]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[farhan.codes:+,messagingengine.com:+]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-2.99)[ip: (-7.36), ipnet: 66.111.4.0/24(-4.87), asn: 11403(-2.68), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[224.4.111.66.list.dnswl.org : 127.0.5.1]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; MID_RHS_WWW(0.50)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 31 Oct 2019 04:49:37 -0000 On Wed, Oct 30, 2019, at 6:52 PM, Austin Shafer via freebsd-wireless wrote: > Hi all, >=20 > I=E2=80=99m interested in hacking around with a netgear wifi adapter I ha= ve (rtwn). Are there any good resources for learning how to read and debug = FreeBSD=E2=80=99s wireless network stack? >=20 > Robert Watson has a great overview of starting points for understanding t= he kernel as a whole, are there any similar "starting points" for network d= rivers? > http://www.watson.org/~robert/freebsd/reading/ >=20 > The =E2=80=9CDesign and implementation ..=E2=80=9D book covers networking= and device driver creation which is helpful, but nothing about wireless. I= did find a few like the following: > https://wiki.freebsd.org/MateuszPiotrowski/Drivers > https://wiki.freebsd.org/WiFi/BringUp >=20 > Any suggestions? I=E2=80=99d appreciate anything that helps me learn how = all this stuff works. >=20 > Thanks in advance, > Austin > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" >=20 Hi Austin! I contributed a bit and dived into rtwn a reasonable bit so hopefully I can= offer some useful thoughts. In short, the way rtwn and all other drivers w= ork is by attaching to an existing stack and telling it "hey! I'm here!". r= twn, like all other drivers, populates a softc with the default device stat= es and device-specific functions that interact with the hardware. (Side not= e: If you read the Design and Implementation book, you will see that "softc= " is the BSD-side naming convention for a struct that holds the device stat= e and functions that directly interact with the hardware.) After this, the = attachment code configures general PCI-settings, specifically the type of d= evice, DMA and interrupts (used to tell the device when memory has been wri= tten via DMA). Finally, the attachment code populates an ieee80211com struc= ture, which tells wireless stack how to interact with the driver. rtwn is a bit more complicated than other drivers. Any rtwn device will req= uire at least three drivers: The PCI or USB driver, the general rtwn driver= which contains shared code, and the device-specific driver. While I'm sure= you can follow the code, I would suggest starting with something a bit sim= pler. I learned the hard way :) One good approach would be to take a simple driver, look at its ieee802com = object, and see what avenues the ieee80211 stack has to interact with the d= river. I would learn about the powering on process, setting up DMA, initial= izing the interrupt code, and seeing how interrupts are handled. From there= I would look into Rx, Tx and then the rest of it. The ieee80211 man pages = are good - in addition to reading them, see how they're implemented in mult= iple drivers - don't just focus on one like I did at first. I also spent a = good bit of time tracing code, both manually and using dtrace's stack dump = functionality. Please let me know if this helps. Also, if you have any more specific quest= ions, please let us know. What are your objectives? I was writing an introduction on this very topic, but $LIFE and other proje= cts got in the way. Maybe I should get back into it? Thanks! -- Farhan Khan PGP Fingerprint: 1312 89CE 663E 1EB2 179C 1C83 C41D 2281 F8DA C0DE From owner-freebsd-wireless@freebsd.org Thu Oct 31 20:15:39 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CB36816517A for ; Thu, 31 Oct 2019 20:15:39 +0000 (UTC) (envelope-from ashafer@badland.io) Received: from badland.io (badland.io [178.128.156.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 473xQg0kNpz3Hlx for ; Thu, 31 Oct 2019 20:15:38 +0000 (UTC) (envelope-from ashafer@badland.io) Received: from [10.155.4.85] (unknown [152.7.255.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by badland.io (Postfix) with ESMTPSA id 09552B43B0; Thu, 31 Oct 2019 16:05:32 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Best way to explore the 802.11 rtwn source code? From: Austin Shafer In-Reply-To: Date: Thu, 31 Oct 2019 16:05:33 -0400 Cc: freebsd-wireless@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <512B62A4-CCB7-4C05-A988-0E19443A2DD0@badland.io> References: <1F9F7008-59C4-42DF-AF1E-0028BD9576F5@badland.io> To: Farhan Khan X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 473xQg0kNpz3Hlx X-Spamd-Bar: ++++++++ X-Spamd-Result: default: False [8.85 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(0.00)[badland.io:s=dkim]; GREYLIST(0.00)[pass,body]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(0.00)[+mx:c]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.37)[asn: 14061(1.91), country: US(-0.05)]; RECEIVED_SPAMHAUS_XBL(5.00)[194.255.7.152.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.4]; BAD_REP_POLICIES(0.10)[]; NEURAL_SPAM_MEDIUM(0.98)[0.981,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[badland.io:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(0.00)[badland.io,reject]; NEURAL_SPAM_LONG(1.00)[1.000,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:14061, ipnet:178.128.144.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Spam: Yes X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 31 Oct 2019 20:15:39 -0000 Hi Farhan, Thanks for the reply! > rtwn is a bit more complicated than other drivers. Any rtwn device = will > require at least three drivers: The PCI or USB driver, the general = rtwn > driver which contains shared code, and the device-specific driver. = While > I'm sure you can follow the code, I would suggest starting with = something > a bit simpler. I learned the hard way :) Yep I=E2=80=99ve noticed that pattern in other drivers, particularly the = i2c hid driver I messed around with. What's a good example of a "simple" driver? > One good approach would be to take a simple driver, look at its = ieee802com > object, and see what avenues the ieee80211 stack has to interact with = the driver. > I would learn about the powering on process, setting up DMA, = initializing the interrupt > code, and seeing how interrupts are handled. =46rom there I would look = into Rx, Tx > and then the rest of it. Following through the rtwn_attach function I agree that following the ieee80211com object is a good idea. If anyone else finds this useful the r21au_attach function is also informative as it adds the interface methods to the softc. The man pages are great as usual. Is ieee80211_ifattach a good point to start reading? It seems to kick off a cascade of *_attach methods which is a little tricky to keep track of. Reading all this does make me realize there are many 802.11 features I don't know about, so if you have a good 802.11 reference I'd love to hear it. > Please let me know if this helps. Also, if you have any more specific > questions, please let us know. What are your objectives? My adapter has frequent times when it will have crippling packet loss (40% to 100%) for 5 ish minutes until things all of a sudden return to normal. I'd love to be able to figure out what's actually going wrong. Also I'd enjoy some 802.11ac support, so if there is any grunt work which a newbie can help with I am glad to chip in. > I was writing an introduction on this very topic, but $LIFE and other > projects got in the way. Maybe I should get back into it? I'm not sure about others, but I would definitely read it. Thanks! Austin