Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3681409ybl; Tue, 20 Aug 2019 00:14:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqxr7pKOtmcGy/ovqPopfefZGOcV7MHKCRRcg2zFkI9YVSRxHSkJ8ZtZL28K+aQouLBqhZw2 X-Received: by 2002:a17:902:246:: with SMTP id 64mr21289032plc.112.1566285264782; Tue, 20 Aug 2019 00:14:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566285264; cv=none; d=google.com; s=arc-20160816; b=0XMaXX7vB50+1FGy0mL/Ove1+a+Tr//xrun0kO3Sb/TgReBqMCUqQYMQfr3WGqlE5v qSRIkFtt0+DHHtfR5iRgu1rcas6q5fy44yyfuXMoPbx6GP04UrtUxK4SgIy8VDe5/wfP AxdHcBTFkMVqcQYKFPEJXZAmOAylmDGP0rAXxp07elVt+J8eVqXTzJpDDKOeFXmn8SfJ MY8baYr1CwXbpSO8/UeM63voXYwTNXdMyj2Bmv6ynfwI6SEiACVXwTNTDlWho0Bh5pCI CVGp3ESNLHQb+ce3aEt1idL8frZTbIeQWXPMwDwOrm2whhCN37duVU0b+6XfGJRlXQE7 tYwg== 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 :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=KD+zxhOewX7TGomI46gXQFDsgZtLnWXB8QAlLaQYzMY=; b=Zhz0kAnR/pJb6HcGHnfyEOBfk1ZOPirXU94clDnC/ShQh9OSX8Jlq2JKRgE8KTUi0+ XfniPXd9feljCKYmmVA/7tm9ZBeynnq/DAEueuD05WJW3ntcGs2NeRp5w/N+dVcKVcGe 94nU04iv0tTGqDItYP2MVTBsXQfTnlmTmRsCroZBXEWp8msPifHbRM3w3M7mQgNXJITN lvVnNkK8OJvYboFnQ2XrBL7MbZPE7TIPlo8oJWQtC3sZl9KsEfQBrh5sto67OPNAjJkE DvKRTT5irBPzDz0NU7S+jyrMQ56ISlZ3b2lZ5PFmNI10YjNwXA59PHTfrnmLcU4wWvEy exLA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 29si11333213pgu.584.2019.08.20.00.14.04; Tue, 20 Aug 2019 00:14:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729047AbfHTHN6 (ORCPT + 99 others); Tue, 20 Aug 2019 03:13:58 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:59412 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726049AbfHTHN6 (ORCPT ); Tue, 20 Aug 2019 03:13:58 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hzyKx-0008Og-L7; Tue, 20 Aug 2019 09:13:47 +0200 Message-ID: Subject: Re: [PATCH 4/4] iwlwifi: Enable Extended Key ID for mvm and dvm From: Johannes Berg To: Alexander Wetzel , Luca Coelho Cc: linux-wireless@vger.kernel.org Date: Tue, 20 Aug 2019 09:13:46 +0200 In-Reply-To: <42653433-58b5-10f0-288e-1e5731e012d1@wetzel-home.de> References: <20190629195015.19680-1-alexander@wetzel-home.de> <20190629195015.19680-4-alexander@wetzel-home.de> <42653433-58b5-10f0-288e-1e5731e012d1@wetzel-home.de> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi, > You are thinking about keeping the tx API untouched and modify the key > install logic? > Just prevent the firmware to activate a key for Tx when it's installed > and notify the firmware by some means when the key can be used for Tx > and then switch everything to the new key? Something like that, yes. > I guess there is no practical way I can get access to the firmware code, > correct? There isn't, yeah. > For me it sounds harder than the optional flag extension I had > in mind for the new tx API. Much more of the TX path is actually wired into the hardware, rather than being software. I'm not sure how much of this (key selection) really is though. > So let's wait and see what you can turn up. Till then we have more than > enough other cards supporting Extended Key ID:-) Yeah. I'll take a look, but I can't promise right now to work on it high priority. johannes