linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: "Arend van Spriel" <arend@broadcom.com>,
	"Jonathan Nieder" <jrnieder@gmail.com>,
	Camaleón <noelamac@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"sgruszka@redhat.com" <sgruszka@redhat.com>
Subject: Re: brcmsmac still woes, possible regression?
Date: Fri, 11 May 2012 11:32:52 +0200	[thread overview]
Message-ID: <1336728772.4310.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20120510163525.GB32040@ubuntu-mba>

On Thu, 2012-05-10 at 09:35 -0700, Seth Forshee wrote:

> > On passive channels, when scanning, mac80211 will send a probe only
> > after receiving a frame on that channel. When associating, it has no
> > such behaviour, at least not directly, but I suppose it could be
> > implemented (waiting for the beacon)
> 
> The background is that brcmsmac contains a bunch of code for regulatory
> support that is either duplicated (and in conflict) with the
> protocol-level support or else it would better be handled there. This is
> causing problems on pretty much any channel that isn't part of the
> default world regulatory domain.
> 
> I've sent RFC patches that strip out the vast majority of this code in
> favor of better integration with the protocol-level regulatory support.
> The piece that's under discussion here is a behavior I maintained in my
> changes, which mutes tx on passive scan channels until data is received
> on a given channel. But in my opinion, if this sort of behavior is
> desired it ought to be implemented at the protocol level instead of in
> the driver, so I'd really prefer to see it removed from brcmsmac.

This isn't implemented in mac80211, and since some HW (e.g. ours)
implements it in lower levels, I don't think you can just generally say
it has to be in mac80211 now.

johannes


  reply	other threads:[~2012-05-11  9:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24  8:55 brcmsmac still woes, possible regression? Camaleón
2012-03-24  9:27 ` Arend van Spriel
2012-03-24 10:04   ` Camaleón
2012-03-24 11:21     ` Camaleón
2012-03-26  9:23       ` Arend van Spriel
2012-03-26  9:43         ` Camaleón
2012-03-26 10:10           ` Arend van Spriel
2012-03-26 21:28             ` Camaleón
2012-03-27  8:47               ` Arend van Spriel
2012-03-28 11:19                 ` Arend van Spriel
2012-03-28 11:26                   ` Camaleón
2012-03-28 12:23                     ` Arend van Spriel
2012-03-28 21:59                       ` Camaleón
2012-03-29 11:56                         ` Arend van Spriel
2012-03-29 13:38                           ` Camaleón
2012-04-02 13:29                             ` Camaleón
2012-04-02 21:50                               ` Jonathan Nieder
2012-04-03  6:25                                 ` Camaleón
2012-04-03 15:30                                 ` Arend van Spriel
2012-05-09  9:41                                   ` Jonathan Nieder
2012-05-09 10:23                                     ` Arend van Spriel
2012-05-09 10:29                                       ` Jonathan Nieder
2012-05-09 10:32                                         ` Arend van Spriel
2012-05-09 17:41                                       ` Seth Forshee
2012-05-09 18:01                                         ` Arend van Spriel
2012-05-09 18:10                                           ` Johannes Berg
2012-05-10 16:35                                             ` Seth Forshee
2012-05-11  9:32                                               ` Johannes Berg [this message]
2012-05-11 17:31                                                 ` Seth Forshee
2012-05-16 20:15                                                   ` Seth Forshee
2012-05-29  7:16                                                     ` Johannes Berg
2012-03-26 14:32         ` Seth Forshee
2012-03-26 16:54           ` Arend van Spriel
2012-03-26 17:13             ` Seth Forshee
2012-03-26 17:15               ` Arend van Spriel

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=1336728772.4310.6.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend@broadcom.com \
    --cc=jrnieder@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=noelamac@gmail.com \
    --cc=seth.forshee@canonical.com \
    --cc=sgruszka@redhat.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).