linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless@vger.kernel.org, Camaleón <noelamac@gmail.com>,
	"Stanislaw Gruszka" <sgruszka@redhat.com>,
	"Seth Forshee" <seth.forshee@canonical.com>,
	"Roland Vossen" <rvossen@broadcom.com>
Subject: Re: [3.2.y] Re: Brcmsmac driver woes, possible regression?
Date: Mon, 16 Jul 2012 16:31:22 -0500	[thread overview]
Message-ID: <20120716213122.GA3078@burratino> (raw)
In-Reply-To: <4FE0CA49.3030909@broadcom.com>

Hi again,

Quick update.

Arend van Spriel wrote:
> On 06/11/2012 05:15 AM, Jonathan Nieder wrote:

>> Newer kernels seemed to work better than old, so I asked her to apply
>> the following patches agains the 3.2.y tree (the exact patches used
>> are at [2]):
>> 
>>   6b1a89afbf97 brcm80211: smac: drop "40MHz intolerant" flag from HT
>>                capability info
>>   c261bdf8acad brcm80211: smac: indicate severe problems to Mac80211
>>   0bf1f883fd0a brcm80211: smac: removed MPC related code
>>   4412953061de brcm80211: smac: removed MPC related variables
>>   28237002e726 brcm80211: smac: removed down-on-watchdog MPC functionality
>>   43ac09722f8e brcm80211: smac: removed down-on-rf-kill functionality
>>   a8bc4917ed6b brcm80211: smac: bugfix for tx mute in brcms_b_init()
>>   c6c44893c864 brcm80211: smac: fixed inconsistency in transmit mute
>>   2646c46d5679 brcm80211: smac: modified Mac80211 callback interface
>>   dc460127898c brcm80211: smac: mute transmit on ops_start
>>   1525662ac280 brcm80211: smac: changed check to confirm STA only support
>>   b7eec4233c34 brcm80211: smac: replace own access category definitions with
>>                mac80211 enum
>>   e9ca530a7b18 brcm80211: smac: don't modify sta parameters when adding sta
>>   8906c43cb160 brcm80211: smac: fix channel frequency
>>   02a588a2e3b9 brcm80211: smac: combine promiscuous mode functionality
>>   be667669ec01 brcm80211: smac: added support for mac80211 filter flags
>>  [d3f311349add brcm80211: fix usage of set tx power] --- unrelated, my mistake
>>   aa1f2f0a3218 brcm80211: smac: precendence bug in wlc_phy_attach()
>>   1570e53c14ff brcm80211: smac: fix unintended fallthru in
>>                wlc_phy_radio_init_2057()

With all the above patches applied on top of 3.2.21, Camaleón quickly
gets the reconnects and gnome-shell segfaults if she does not supply
the password to network-manager in time[1].  That means the patch that
prevents trouble is presumably one of the four listed below.

>>   137dabed34a1 brcm80211: smac: remove smatch warnings from brcmsmac code
>>   2b0a53d51b5f brcm80211: smac: only print block-ack timeout message at
>>                trace level
>>   6b8da423315b brcm80211: smac: do not use US as fallback regulatory hint
>>   94a2ca311cf4 brcm80211: smac: only provide valid regulatory hint

Thanks,
Jonathan

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=295;bug=664767

  parent reply	other threads:[~2012-07-16 21:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKprTDFHmBuOorCo4evrYrNEi2-gJov0mQXQpEjoRJicfhWg=A@mail.gmail.com>
     [not found] ` <20120530172713.GH3908@burratino>
     [not found]   ` <CAKprTDGtvUFSBb_XK01bi6bJa3dynu73Lq-jTs=E78E3QwSqpA@mail.gmail.com>
     [not found]     ` <20120601174237.GA31781@burratino>
     [not found]       ` <CAKprTDHepfbCKquvnG8CQ2=-tSNbgOSkT6R0GQmEx9UyuiZyMQ@mail.gmail.com>
     [not found]         ` <CAKprTDHQT8Oodh_YD5CWffSGJXAg-HgFMjR0STVgEZRxH4FaSQ@mail.gmail.com>
     [not found]           ` <20120604084200.GA30645@tiikeri.vuoristo.local>
     [not found]             ` <20120604173121.GA9238@stt008.linux.site>
     [not found]               ` <20120605050620.GC3118@burratino>
     [not found]                 ` <CAKprTDHGqDpdZY4ErZmPEc7Ur81GeQoH8tiAL5hrfhAE0RtbvQ@mail.gmail.com>
2012-06-11  3:15                   ` [3.2.y] Re: Brcmsmac driver woes, possible regression? Jonathan Nieder
2012-06-19 18:15                     ` Jonathan Nieder
2012-06-19 19:15                       ` Arend van Spriel
2012-06-19 19:28                         ` Jonathan Nieder
2012-06-20  7:11                           ` Arend van Spriel
2012-06-20 10:02                             ` Jonathan Nieder
2012-06-20 12:13                               ` Arend van Spriel
2012-06-19 18:51                     ` Arend van Spriel
2012-07-07  4:56                       ` Jonathan Nieder
2012-07-16 21:31                       ` Jonathan Nieder [this message]
2012-07-17  7:54                         ` Arend van Spriel
2012-07-23  0:28                           ` Jonathan Nieder
2012-07-29 22:48                             ` Jonathan Nieder
     [not found]                   ` <20120610224902.GB3419@burratino>
     [not found]                     ` <20120611063014.GA4579@stt008.linux.site>
     [not found]                       ` <CAKprTDHYMyDwvxA52Z9zxP75ZUY5=FfCGPTZZg9ZxTxReFj7pQ@mail.gmail.com>
     [not found]                         ` <20120619180335.GA19354@burratino>
     [not found]                           ` <CAKprTDGM8TJC51Bqideeg447+qR5YnfihgORUFdJL_hW9YHiTw@mail.gmail.com>
2012-06-23 17:50                             ` [3.2.y] " Jonathan Nieder
2012-06-24  9:41                               ` 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=20120716213122.GA3078@burratino \
    --to=jrnieder@gmail.com \
    --cc=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=noelamac@gmail.com \
    --cc=rvossen@broadcom.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).