Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8973CC282C8 for ; Mon, 28 Jan 2019 08:36:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5834220881 for ; Mon, 28 Jan 2019 08:36:40 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="DhcEUUD7"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="bvMJd9Qu" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726864AbfA1Igj (ORCPT ); Mon, 28 Jan 2019 03:36:39 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:57772 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726681AbfA1Igj (ORCPT ); Mon, 28 Jan 2019 03:36:39 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 0BDCB6086A; Mon, 28 Jan 2019 08:36:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1548664598; bh=sN+njMVV1/6/6XvScW8m/cNT3hDDESAdC3Sxs4AUawU=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=DhcEUUD7CT+TCrTk0QBqO8f2Aau0UywYLr3uVfhEAVN2CxYRwf/Y+d1jPrdyAw+Lx Qgzuw+Uw0TH9MWsYkPN2tmsfixXGV03wFKtUZH1937avQ25GYyVpsb1E0Dw1ju8Ptm Kbpw9FVUr7evNqvONtu0EIkad9A3ifvOVuoKQs/M= Received: from x230.qca.qualcomm.com (87-93-85-88.bb.dnainternet.fi [87.93.85.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: kvalo@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id C849660740; Mon, 28 Jan 2019 08:36:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1548664597; bh=sN+njMVV1/6/6XvScW8m/cNT3hDDESAdC3Sxs4AUawU=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=bvMJd9QuClRx6cXEaWOSAaSxBKXg75Fg6lzEFXcCig5rBgyO0vF3snEXxszrUGnYT u9mH3ksdGBCtHtg0gQ83+igRwkuDY2FeF9PXiXD9O5ZTpz7OQ05aARuXySL1px8eul XS9effw+HiPX7B1pcYtDT1yDg7wwEJPutlWwdsVc= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org C849660740 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=kvalo@codeaurora.org From: Kalle Valo To: Cc: , , , , , , Subject: Re: [PATCH v3 00/13] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips References: <1548654407-28469-1-git-send-email-yhchuang@realtek.com> Date: Mon, 28 Jan 2019 10:36:32 +0200 In-Reply-To: <1548654407-28469-1-git-send-email-yhchuang@realtek.com> (yhchuang@realtek.com's message of "Mon, 28 Jan 2019 13:46:34 +0800") Message-ID: <87tvht18mn.fsf@codeaurora.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org writes: > From: Yan-Hsuan Chuang > > This is a new mac80211 driver for Realtek 802.11ac wireless network chips. > rtw88 supports 8822BE and 8822CE chips, and will be able to support > multi-vif combinations in run-time. > > For now, only PCI bus is supported, but rtw88 was originally designed > to optionally support three buses includes USB & SDIO. USB & SDIO modules > will soon be supported by rtw88, with configurable core module to fit > with different bus modules in the same time. > > For example, if we choose 8822BE and 8822CU, only PCI & USB modules will > be selected, built, loaded into kernel. This is one of the major > difference from rtlwifi, which can only support specific combinations. > > Another difference from rtlwifi is that rtw88 is designed to support > the latest Realtek 802.11ac wireless network chips like 8822B and > 8822C series. Compared to the earlier chips supported by rtlwifi like > the 802.11n 8192EE chipset or 802.11ac 8821AE/8812AE chips, newer ICs > have different MAC & PHY settings, such as new multi-port feature for the > MAC layer design and Jaguar2/Jaguar3 PHY layer IPs. > > Multi-Port feature is also supported under rtw88's software architecture. > rtlwifi can only support one vif in the same time, most because of the > hardware limitations for early chips, hence the original design of it > also restricts the usage of multi-vif support, so latest chipset seems not > take advantages from its new MAC engine. > > However, rtw88 can run multiple vifs concurrently by holding them on > hardware ports provided by MAC engine, hence can easily start different > roles on a single device. > > Based on the reasons mentioned before, we implemented rtw88. It had many > authors, they are listed here alphabetically: > > Ping-Ke Shih > Tzu-En Huang > Yan-Hsuan Chuang > > > v2 > > - add comment for watch dog > > > v3 > > - change tree location to wireless-next What does this mean? wireless-next has not been used for years, do you mean wireless-drivers-next instead? -- Kalle Valo