From: Johannes Berg <johannes@sipsolutions.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Exposing enum ieee80211_channel_flags to user
Date: Thu, 11 Jun 2015 11:45:22 +0200 [thread overview]
Message-ID: <1434015922.1915.6.camel@sipsolutions.net> (raw)
In-Reply-To: <CACna6rwHXzGTZ+NS9PpZENJATVzRzm1Wkija0_CrveMoM05d5g@mail.gmail.com> (sfid-20150611_113544_857208_070F0480)
On Thu, 2015-06-11 at 11:35 +0200, Rafał Miłecki wrote:
> iw also wasn't helpful:
> Frequencies:
> * 5180 MHz [36] (30.0 dBm)
> * 5200 MHz [40] (30.0 dBm)
> * 5220 MHz [44] (30.0 dBm)
> * 5240 MHz [48] (30.0 dBm)
>
> After some in-kernel debugging (nl80211_set_wiphy,
> cfg80211_chandef_usable, cfg80211_secondary_chans_ok) I finally
> realized it was because of:
> IEEE80211_CHAN_NO_80MHZ
>
> Do you have any idea how we could handle such cases nicely? To let
> user find out what's going on (wrong)?
>
> Should "iw" be extended to print flag names? Or should hostapd check
> for channels in some smarter way? Any other ideas?
We already have the flags exposed to iw, it's just not printing them.
There was a patch to print them, but it wasn't complete, and the
submitter kinda went away. You can see the discussion here:
http://mid.gmane.org/1425452686-28196-1-git-send-email-arnagara@qti.qualcomm.com
johannes
next prev parent reply other threads:[~2015-06-11 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 9:35 Exposing enum ieee80211_channel_flags to user Rafał Miłecki
2015-06-11 9:45 ` Johannes Berg [this message]
2015-06-11 9:46 ` Johannes Berg
2015-06-11 10:00 ` Rafał Miłecki
2015-06-11 10:01 ` Johannes Berg
2015-06-11 13:16 ` Ben Greear
2015-06-11 13:27 ` Johannes Berg
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=1434015922.1915.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@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).