From owner-freebsd-wireless@freebsd.org Mon Jul 13 15:25:29 2020 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 A6AB1367012 for ; Mon, 13 Jul 2020 15:25:29 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B56sj2GZlz44Wm; Mon, 13 Jul 2020 15:25:28 +0000 (UTC) (envelope-from manu@bidouilliste.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1594653927; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3QnbDI7Liag/hTYhVk6N7rOIAKh2Qcar1HvVPA+k2HI=; b=Jd0fKHhXuKtAw3C+lXY6GThxjWsZ8EXgQW3Zag3x6JPeMyVIpb1BevjLQVPnksRSteU221 QTjOahBIvUsscHf+vw6xssGUNhhRLn36lHDTkYUXHXE6EOBBkLNFc7/dvXq8jOgPjoSDHR A6PfyjVnNa/BoUEro0wZWMTFjADrymk= Received: from amy (j1a01-1-78-205-69-41.fbx.proxad.net [78.205.69.41]) by mx.blih.net (OpenSMTPD) with ESMTPSA id d0c988ae (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Mon, 13 Jul 2020 15:25:26 +0000 (UTC) Date: Mon, 13 Jul 2020 17:25:26 +0200 From: Emmanuel Vadot To: "Bjoern A. Zeeb" Cc: driesm.michiels@gmail.com, freebsd-wireless@freebsd.org Subject: Re: Current state of recent wireless cards Message-Id: <20200713172526.81bb91a04198792ce8695322@bidouilliste.com> In-Reply-To: <778A3FF0-905B-49ED-ABDE-913C3451AB16@FreeBSD.org> References: <000501d655e3$90c40170$b24c0450$@gmail.com> <20200710233308.b27284cd15dec5849fb5cc32@bidouilliste.com> <778A3FF0-905B-49ED-ABDE-913C3451AB16@FreeBSD.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4B56sj2GZlz44Wm X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.33 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, 13 Jul 2020 15:25:29 -0000 On Mon, 13 Jul 2020 10:34:51 +0000 "Bjoern A. Zeeb" wrote: > On 10 Jul 2020, at 21:33, Emmanuel Vadot wrote: >=20 > > That's a bit optimistic that attach and firmware loading is half of > > the work no ? > > I don't know how much linuxkpi layer is needed for 80211 compat but I > > guess it's "a lot" ? >=20 > Part of that ?lot? is that as Adrian also indicates the net80211=20 > parts also > need doing as otherwise you cannot write the compat on top and that=20 > makes > it hard to estimate how much will be compat or native yet. I though that your plan was to have every compat needed in linuxkpi to port/update drivers more easily. Also I'm not really talking about AC here, just doing linuxkpi compat for what's already needed for G is still a lot (and needed for iwlwifi). > Also given along with ath10k this is the ?first? bits to do this in=20 > FreeBSD > it?ll always take longer than doing a 2nd or 3rd driver. >=20 > > IIRC Linux have multiple 80211 framework no ? >=20 > Well kind-of layered: mac80211 / cfg80211 and the user space config > stuff in nl80211 and I?d almost thought intermangled add the entire > regdomain parts. > https://wireless.wiki.kernel.org has at least some overview there. >=20 >=20 > > I guess your work only focus on one (used by iwlwifi), do you know=20 > > how > > many drivers used the same one ? What about FullMAC drivers like the > > SDIO broadcom one used in many ARM SBC, is that using the same > > framework ? >=20 > The Broadcom driver could be a great deal easier to port than it is. > It will be easier to port with this as some parts are already covered > as a result of this and more will be. The SDIO parts for the fmac are > not part of this as the Intel work is PCI-only but those were done last > year already.=20 So you have linuxkpi code for linux mmcstack -> mmccam ? Or are you just talking about mmccam sdio functionality ? > I am currently trying to get my hands-on a PCI card as > well as I hope that might speed up some things. >=20 > On another note, I was able to get the rtw88 driver compile in under a > day based on the iwlwifi. That?s kind-of an ideal case, other=20 > drivers > would need more time (and it?ll highly depend on whether that is other > Linux or other WiFi bits). Compile and working ? Because that's easy to compile code if you add a lot of dummy stub functions. >=20 > I had done a comparison after the initial iwlwifi work based on compile > time errors for a few Dual BSD-GPL or ISC or similarly friendly licensed > drivers: the order was iwlwifi < rtw88 < ath11k < ath10k < brcmfmac in > terms of individual errors and functions missing/to implement. I also > had numbers of how much the iwlwifi work had reduced all this but they > are outdated. >=20 > I also looked at the mt7601u GPL driver (as the hope is that some of=20 > these > could also be ported more quickly and possibly live outside the tree but > at least be avail) and it wasn?t too bad either. A handful of extra=20 > WiFi > constants and 6 or so functions and then the usual Linux noise on top. >=20 >=20 > /bz --=20 Emmanuel Vadot