From: "Arend van Spriel" <arend@broadcom.com>
To: "Seth Forshee" <seth.forshee@canonical.com>
Cc: "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>,
"Johannes Berg" <johannes@sipsolutions.net>
Subject: Re: brcmsmac still woes, possible regression?
Date: Wed, 9 May 2012 20:01:34 +0200 [thread overview]
Message-ID: <4FAAB0FE.601@broadcom.com> (raw)
In-Reply-To: <20120509174106.GA7189@ubuntu-mba>
On 05/09/2012 07:41 PM, Seth Forshee wrote:
> On Wed, May 09, 2012 at 12:23:43PM +0200, Arend van Spriel wrote:
>> On 05/09/2012 11:41 AM, Jonathan Nieder wrote:
>>> Hi Arend,
>>>
>>> Arend van Spriel wrote, about a month ago[1]:
>>>
>>>> I sent the patch to Camaleón to test it before sending out the
>>>> patch. So the answer it definitely no. I wanted to get it into rc1,
>>>> but we missed that.
>>>
>>> Any news? If there's a patch that goes in the right direction with
>>> known problems I'd still be interested in it, among other reasons
>>> because it would make the bug more concrete and make it easier to
>>> think about possible fixes.
>>
>> Well, there is the short term fix, which is already upstream and moved
>> to stable. The long term fix for which Seth Forshee (Canonical) did a
>> great job is reviewed over here, but it involves regulatory related code
>> so it needs discussions with our compliance team and supervisor. So that
>> causes some lag time.
>
> The patches I sent still relies on the transmit-after-beacon fix, as I
> preserved the behavior of muting tx if the channel is passive scan. I
> *think* this isn't actually necessary, but I'd have to investigate a
> little further to be certain.
>
> Seth
>
As part of the discussion over here I am proposing to get rid of the tx
muting in brcmsmac as mac80211 already has that behaviour for passive
channels if I am not mistaken (is this true, Johannes?).
Gr. AvS
next prev parent reply other threads:[~2012-05-09 18:01 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 [this message]
2012-05-09 18:10 ` Johannes Berg
2012-05-10 16:35 ` Seth Forshee
2012-05-11 9:32 ` Johannes Berg
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=4FAAB0FE.601@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.