Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: linux-wireless@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH 1/4] cfg80211: regulatory, introduce DFS CAC time
Date: Fri, 21 Feb 2014 11:11:56 +0100	[thread overview]
Message-ID: <1392977516.4346.47.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CALhHN=ommG9hB7HmMecJPb1UHdn1OqHRnSbS16b-BxowwP61FQ@mail.gmail.com> (sfid-20140221_110909_899698_3CFDCAEF)

On Fri, 2014-02-21 at 11:09 +0100, Janusz Dziedzic wrote:
> On 21 February 2014 10:55, Johannes Berg <johannes@sipsolutions.net> wrote:
> > On Fri, 2014-02-21 at 10:47 +0100, Janusz Dziedzic wrote:
> >> On 21 February 2014 09:52, Johannes Berg <johannes@sipsolutions.net> wrote:
> >> > On Wed, 2014-02-12 at 19:54 +0100, Janusz Dziedzic wrote:
> >> >
> >> >> +++ b/include/net/regulatory.h
> >> >> @@ -155,6 +155,7 @@ struct ieee80211_reg_rule {
> >> >>       struct ieee80211_freq_range freq_range;
> >> >>       struct ieee80211_power_rule power_rule;
> >> >>       u32 flags;
> >> >> +     u32 dfs_cac_ms;
> >> >>  };
> >> >
> >> > Does that really have to be per channel? That's a significant investment
> >> > into bss size since we have a lot of channel structs.
> >> >
> >> This seems easiest way to handle ETSI VHT80/40 case for channels with
> >> different CAC time (eg):
> >> VHT80:
> >> - 116 (60s)
> >> - 120 (600s)
> >> - 124 (600s)
> >> - 128 (600s)
> >>
> >> VHT40/HT40:
> >> - 132 (600s)
> >> - 136 (60s)
> >
> > Huh, but you don't distinguish between channel widths in this whole
> > patchset?
> >
> In patch  cfg80211: DFS get CAC time from regulatory I check whole
> chandef and get max channel cac value.

Oh, right, I misunderstood your other email.

johannes


      reply	other threads:[~2014-02-21 10:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 18:54 [PATCH 1/4] cfg80211: regulatory, introduce DFS CAC time Janusz Dziedzic
2014-02-12 18:54 ` [PATCH 2/4] cfg80211: parse DFS CAC time for internal regdb option Janusz Dziedzic
2014-02-12 18:54 ` [PATCH 3/4] cfg80211/mac80211: DFS pass CAC time as a parameter Janusz Dziedzic
2014-02-21  8:53   ` Johannes Berg
2014-02-12 18:54 ` [PATCH 4/4] cfg80211: DFS get CAC time from regulatory Janusz Dziedzic
2014-02-21  8:54   ` Johannes Berg
2014-02-12 18:54 ` [PATCH] wireless-regdb: add DFS CAC time parameter Janusz Dziedzic
2014-02-12 18:54 ` [PATCH] crda: add DFS CAC time support Janusz Dziedzic
2014-02-12 18:54 ` [PATCH] iw: handle DFS CAC time param Janusz Dziedzic
2014-02-19  0:31 ` [PATCH 1/4] cfg80211: regulatory, introduce DFS CAC time Luis R. Rodriguez
2014-02-19 11:03 ` Johannes Berg
2014-02-19 11:27   ` Janusz Dziedzic
2014-02-19 11:28     ` Johannes Berg
2014-02-19 22:11       ` Luis R. Rodriguez
2014-02-20  7:12         ` Janusz Dziedzic
2014-02-22  0:31           ` Luis R. Rodriguez
2014-02-21  8:52 ` Johannes Berg
2014-02-21  9:47   ` Janusz Dziedzic
2014-02-21  9:55     ` Johannes Berg
2014-02-21 10:09       ` Janusz Dziedzic
2014-02-21 10:11         ` Johannes Berg [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=1392977516.4346.47.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=janusz.dziedzic@tieto.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@do-not-panic.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