Received: by 2002:a25:23cc:0:0:0:0:0 with SMTP id j195csp1020114ybj; Tue, 5 May 2020 11:32:11 -0700 (PDT) X-Google-Smtp-Source: APiQypLe2f4bOfWL2k9S+qjyL2rn5nMrvNk5EczgVDjDsHP7fuMZxbQAGC9r9oWh+pYc46yepCJY X-Received: by 2002:a50:950a:: with SMTP id u10mr3981807eda.45.1588703531087; Tue, 05 May 2020 11:32:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588703531; cv=none; d=google.com; s=arc-20160816; b=MKe8mkXTK6HrPcre2PDCrY39eep8i9ugNCsWbwEubmyWX9s2QMYZBZ1QvbxGpUN/A0 PfmWOPVGsZUP7FZ9IfRLy/kx44jDzQPwpVDPzB14stPt/0k1bFTiKxcNFlW2g/GKScv+ 21JxFPForIfY3hW9AUbyi9KDZapnmiVrjmufiCRt65IL3jgQGNGCo3D5ZKX+0CApru63 OevTgjHRzT54ZgFYAyq8rEmV2LGNix69vang4sKfBHmkGE+Z8vHVTcFaG+i/PbtaLXLr 0RGtvw7s9892dDJ1B/bm1UpEvfBsPFzLOCDDQ/pSVVUzFpEEFMMpABLIuq8ER/y36lbk Utqw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=havhuAu7xznQ0MuR1bzbfKCs7K2MdrTertMDkyH7tfY=; b=Wn0c1fxvOLxWiWxonmdZZixEKkDMEbXc7BD5+RAbBGZF+37neU1d8gQtXwyB+0KY3b TjtZ0pBKcAnWobowcuCXwxVgKhFG//wfYt48auArV6qrE0coR+MvQuNUmMSwmRK3GXzO g0qtJofPRb8Dz9rd0HSL6wjIJnToSfM9NTdlRV1pvcSl76Z+rImFBnDW27fXRUMd7q3v V4vMyG5ETgka9IDeqPcFVqQMJqANHjvRGgWS+VnNxuEFlz5+4arjEIzegq5j6B/aZSXn bi+sa57CSdPvxUUobDGXAG8qIIJ9NQkv54Hr9JK7RWayAyPdrVxFlrLpEdvf0kIxaAsy ioUw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=FfQ366NL; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id da15si1835376edb.140.2020.05.05.11.31.34; Tue, 05 May 2020 11:32:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=FfQ366NL; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728180AbgEESbW (ORCPT + 99 others); Tue, 5 May 2020 14:31:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32820 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727083AbgEESbW (ORCPT ); Tue, 5 May 2020 14:31:22 -0400 Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F1FCCC061A0F for ; Tue, 5 May 2020 11:31:21 -0700 (PDT) Received: by mail-wr1-x442.google.com with SMTP id f13so3897544wrm.13 for ; Tue, 05 May 2020 11:31:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=havhuAu7xznQ0MuR1bzbfKCs7K2MdrTertMDkyH7tfY=; b=FfQ366NL1oalpQ62x0lekBgIFkA/wxnns/r1ujkHVEVZoC5xy4IaY/vgyexgyRfMAk rD42IepcjxIdKn5gOe92DgatCoZjnblhvDrgHrau5umekelSqtIJJAV3/pDSE974T2aY x3KikGrF5WFmFwTdHP7KKwH2VaPhtRZYX4Sqt3zDrB5XJdDPKiGNTmlH35Yiyp9Km5VQ G+GFej0QzqIPFK+HjfxXyCvR9k/0ejBgbXdAvut4VC+wf0+uJNvyh6nJgALp1jyWhMGa zRuFNjLj0nzHuxnQW0qA7wBTQutkschunrCUa3ONYTeMur9ypy7euwh1JHRK4nR8AtHh 3/Eg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=havhuAu7xznQ0MuR1bzbfKCs7K2MdrTertMDkyH7tfY=; b=aud+mI3+EiaG/p27ifxeAselairOgPWkM4lkSo1gEFnnmfSZSjQFN+FbUVDWvBLcH0 BS9AVZk4wOkHEFl6yz1jPD6asnVekPDqDkJjGcfV8MwcjpEP5umZrwLEuitXVpZ4V/Ad XaEUaNib9ixnLnVDSORUyxsH58C3AsSdiGbm1jvzROjOy6H8Py4RtSI0Os2J+kOMDIsz zDX8Vt3VwddCDRjGCbioWZa5+2Gdd4lUKSNsMgGzJK2NDStYnN2iMAUTaxp2cQM+cPiC Uqyz5XkEoDBcZG2FCWrU+ghCjEOzDnwIarDfzny+hz2iOCxM6u9lyV8MA28kuEZnmjUH xy/Q== X-Gm-Message-State: AGi0PuY9XtcJv/T3dZO9mgH2RlwB039FHFcwhfL6DNNz2oCcipbZbaHn gcO2dGvHn3tBk0aigGmtR8Q= X-Received: by 2002:adf:ce90:: with SMTP id r16mr4909729wrn.86.1588703480623; Tue, 05 May 2020 11:31:20 -0700 (PDT) Received: from debian64.daheim ([91.13.113.85]) by smtp.gmail.com with ESMTPSA id i17sm5287617wml.23.2020.05.05.11.31.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 May 2020 11:31:11 -0700 (PDT) Received: from localhost.daheim ([127.0.0.1] helo=debian64.localnet) by debian64.daheim with esmtp (Exim 4.93) (envelope-from ) id 1jW2LN-0008W4-O8; Tue, 05 May 2020 20:31:01 +0200 From: Christian Lamparter To: Kalle Valo Cc: Frank =?ISO-8859-1?Q?Sch=E4fer?= , linux-wireless@vger.kernel.org Subject: Re: [PATCH] carl9170: remove P2P_GO support Date: Tue, 05 May 2020 20:31:01 +0200 Message-ID: <27876964.GhbJDmQBxd@debian64> In-Reply-To: <87368ej1aj.fsf@tynnyri.adurom.net> References: <20200425092811.9494-1-chunkeey@gmail.com> <5ebf8e6d-d34b-aa92-d166-d8a5ca0b2c18@googlemail.com> <87368ej1aj.fsf@tynnyri.adurom.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hello, On Tuesday, 5 May 2020 09:20:20 CEST Kalle Valo wrote: > Frank Sch=E4fer writes: > > > > Am 25.04.20 um 11:28 schrieb Christian Lamparter: > >> This patch follows up on a bug-report by Frank Sch=E4fer that > >> discovered P2P GO wasn't working with wpa_supplicant. > >> This patch removes part of the broken P2P GO support but > >> keeps the vif switchover code in place. > > > > Hmm... no way to fix it ? > > P2P-GO seems to work fine with p2p_no_group_iface=3D1, so do you really > > think it's a good idea / required to remove the whole thing ? > > > >> Cc: > > > > Are you sure about that ? > > People might be using it... >=20 > Christian, what should I do? Take the patch or drop it? Well, the way I see it: AR9170's silicon die has been cast before P2P was a thing. And while it was nice back in '10 then to had have something to test ath9k with, by todays standards the lack of features like separate TSF sync and the cacheless BA makes it so that it's holding back the performance and connection quality of all the clients which are connected to it. So, I think we'll just kicking down the can on that and I'm sorry that I gave the people the wrong impression. There are much better chips now that came with P2P in mind.=20 So: please take the patch. Cheers Christian