From: Arend van Spriel <arend@broadcom.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
Victor <silentworks@gmail.com>
Cc: <linux-wireless@vger.kernel.org>
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)
Date: Tue, 24 Jun 2014 10:41:30 +0200 [thread overview]
Message-ID: <53A939BA.3030700@broadcom.com> (raw)
In-Reply-To: <20140624005030.GI1390@garbanzo.do-not-panic.com>
updated subject
On 24-06-14 02:50, 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
>>
>> Problem found: the system shows all channels for Ghz band as (no IR),
>> so they can't be used
>
> NO-IR means you can't initiate radiation, it doesn't mean they are
> disabled. The NO-IR flag then means you cannot use modes of operation
> that require you to initiate radiation first, there are two ways that
> can happen:
>
> * beconing -- AP, IBSS, Mesh, P2P master mode
That is just the point, right? The context is "Setup of wireless AP".
Regards,
Arend
> * active scanning
>
> You are still able to do passive scanning. The NO-IR flag can be
> lifted from channels if the driver does like the idea of trusting
> beacon hints:
>
> http://wireless.kernel.org/en/developers/Regulatory/processing_rules#Beacon_hints
>
> If the driver does not like those then you won't get the NO-IR flag
> lifted when a beacon is found. There device follows the desire by
> the silicon manufacturer and whoever deploys the device and integrates
> it into your system so anything beyond this should be checked with
> Intel folks.
>
> Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-06-24 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 20:55 No channels available (no IR) in 5Ghz band for intel 7260-ac Victor
2014-06-24 0:50 ` Luis R. Rodriguez
2014-06-24 7:37 ` Emmanuel Grumbach
2014-06-24 8:07 ` Victor
2014-06-24 8:41 ` Arend van Spriel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53A939BA.3030700@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=silentworks@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).