Return-path: Received: from mail-lb0-f175.google.com ([209.85.217.175]:38546 "EHLO mail-lb0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754329AbaF3S4I (ORCPT ); Mon, 30 Jun 2014 14:56:08 -0400 Received: by mail-lb0-f175.google.com with SMTP id n15so6084818lbi.6 for ; Mon, 30 Jun 2014 11:56:05 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20140630095508.GA23387@sig21.net> References: <20140630095508.GA23387@sig21.net> Date: Mon, 30 Jun 2014 21:56:05 +0300 Message-ID: (sfid-20140630_205611_311126_66D13B92) Subject: Re: Setup of wireless AP using an intel 7260-ac on 5Ghz+ band, linux 3.15.1 (was: No channels available (no IR) in 5Ghz band for intel 7260-ac From: Emmanuel Grumbach To: Johannes Stezenbach Cc: Victor , "Luis R. Rodriguez" , linux-wireless Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Jun 30, 2014 at 12:55 PM, Johannes Stezenbach wrote: > Hi Emmanuel, > > On Tue, Jun 24, 2014 at 03:50:43PM +0300, Emmanuel Grumbach wrote: >> >> On 06/24/2014 03:50 AM, Luis R. Rodriguez wrote: >> >>> On Mon, Jun 23, 2014 at 10:55:48PM +0200, Victor wrote: >> >>>> Hello, first of all i'm not sure if this is the proper place to ask >> >>>> since it seems mostly dev-related, but i have been looking everywhere >> >>>> trying to find a solution without luck, so i'm not sure if i >> >>>> encountered some kind of bug. >> >>>> >> >>>> Context: Setup of wireless AP using an intel 7260-ac on 5Ghz+ band, linux 3.15.1 >> >> >> >> This configuration is not supported. >> > >> > Do you know why? it is supported in other kernel version?, i got the >> > device mainly for to be used as 802.11ac AP :/, on the product brief >> > they state it is designed for AP mode >> > http://www.intel.es/content/dam/www/public/us/en/documents/product-briefs/dual-band-wireless-ac-7260-bluetooth-brief.pdf, >> > and in iw it appears as supported too >> >> AP mode is supported - not on 5.2 GHz band. > > Just out of curiosity, may I ask why? Shouldn't regdb/crda allow > you to support it? > We don't use CRDA - we enforce the regulatory in the device itself - hence it can't change its behavior based on the location.