Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp3284682ybd; Fri, 28 Jun 2019 06:06:32 -0700 (PDT) X-Google-Smtp-Source: APXvYqypQVd2BJX2YAIEJOgopTuhmnAsyuMmysA6VJPy3shwWf4LbM3Z2ATx5RfETVNQ7zboboS0 X-Received: by 2002:a17:90a:9281:: with SMTP id n1mr12745016pjo.25.1561727192150; Fri, 28 Jun 2019 06:06:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561727192; cv=none; d=google.com; s=arc-20160816; b=T/k9XZYGLTI9J6MnuLEyd4W++N6mmqpR4Wq2liWXWE++T0Lh/AdsFrKmInJmJbEYYU fRfk6NRmzgLxNPs+dmA5tDkwivxXnoKr/s093oGxacA1+XBB0AE7bkunD0CqOa5u94Ew qmEcgLxEfEFTReKTa2EcoJwDFUKgC2V52MfUBMc+5x2oTdiK55UjFSLh9CskV1hCKLmr kctnSvyfNkLpdDhR8EwPyFgUGLeBOWzxCrFLRLoneEtAlc3pgA84ceTWt8DPjnP1HW1H cnRNoFJNtH3jI1fhQInDSV4eW08xBzkmgsXI2/Ecdo5Ae0d39PvCTD9rfxvH1uFMdLYt 4YIw== 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:date:cc:to:from:subject:message-id; bh=c3jIsy8YpOGptEyTsE7AfyXMsVbkuBfsRHVl/+FIp+o=; b=Yspiz6whTi7pnVYVdMYSN6YlVD2lZ+GpGUAyBK4D/b8NYbOY4TH/DYAlDDg1AisrKx Jq8svpOFTeTRmNMFdGu+YxceqciQd93mkbiFFU0qLl6Uu3PlpiwsbiDBLWEewP8ahWsr uPFKKg4kuqzE08Uw92ZBSs+rX8XBsiVBsu2whjxbi3X59nZatd2CNLvyOtV/jUjNf2yt Jdc7f2xuVSj/z8gPAte59xKqkwqc51n3MEywu95Lo+t2nSZbVP9Ilt9uEyMaNYRiFSLO 1tP+qV0GH+gQC2Jy+kwTxPEi2+eyl1aQD29g1CDufGiqz35E1+bX47SfZXuNQLfxiH3B g4fw== 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 w6si2225660pjr.100.2019.06.28.06.06.16; Fri, 28 Jun 2019 06:06:32 -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 S1726912AbfF1NEM (ORCPT + 99 others); Fri, 28 Jun 2019 09:04:12 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:50244 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726828AbfF1NEM (ORCPT ); Fri, 28 Jun 2019 09:04:12 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hgqXx-0001ML-7T; Fri, 28 Jun 2019 15:04:09 +0200 Message-ID: <48a43287e65e1d24082dea2cc32ca14998acb8d1.camel@sipsolutions.net> Subject: Re: [RFC 0/8] nl80211: add 6GHz band support From: Johannes Berg To: Arend Van Spriel Cc: linux-wireless@vger.kernel.org, Jouni Malinen , Tova Mussai Date: Fri, 28 Jun 2019 15:04:06 +0200 In-Reply-To: <9ba78df6-18a3-5c1c-6c57-3fa71531b460@broadcom.com> (sfid-20190527_224659_799325_3B1770C5) References: <1558353645-18119-1-git-send-email-arend.vanspriel@broadcom.com> <16aeb2310e8.2764.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> <9ba78df6-18a3-5c1c-6c57-3fa71531b460@broadcom.com> (sfid-20190527_224659_799325_3B1770C5) Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-3.fc28) 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 Arend, all, Sorry. No, my thoughts aren't really more concrete, but Tova is starting to work on this now. > This came up in discussion with my colleagues today and I would say from > mac80211 perspective there is more to it than just scanning. In short > the 6GHz band is for HE-only operation so for example only HE rates may > be used. As the bitrates are in ieee80211_supported_band having a > separate 6GHz band seems to have a (slight?) advantage. Hmm, that's a good point too, I hadn't really looked _too_ much at 6GHz stuff. Jouni, what do you think? Perhaps we should just have both. I mean, we can treat this as a separate band, and still have code to handle operating classes properly, right? johannes