All of lore.kernel.org
 help / color / mirror / Atom feed
From: Camaleón <noelamac@gmail.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	664767@bugs.debian.org, linux-wireless@vger.kernel.org
Subject: Re: Brcmsmac driver woes, possible regression?
Date: Mon, 18 Mar 2013 22:14:28 +0100	[thread overview]
Message-ID: <20130318211428.GA9136@stt008.linux.site> (raw)
In-Reply-To: <51476D25.6030609@broadcom.com>

El 2013-03-18 a las 20:38 +0100, Arend van Spriel escribió:

> On 03/18/2013 09:37 AM, Jonathan Nieder wrote:
>> Camaleón wrote[1]:
>>
>>> vermagic:       3.9.0-rc2 SMP mod_unload modversions 686
>>>
>>> As soon as I load the brcmsmac module, N-M pop-ups and asks for the
>>> secrets... constantly until it quits, that is, I cannot even connect
>>> to the wifi AP with the Broadcom card, it's a bit frustrating :-(
>
> Sorry to hear. Reading back the bug report I noticed you are having a  
> bcm4313 and we recently had a regression on it. Could you provide  
> debugfs information from <debugfs_mount>/brcmsmac/bcma0:0/hardware

I see. My "/sys/kernel/debug/*" directory is empty so now that I'm going 
to recompile the whole kernel again to revert the patch, is there any 
flag I need to turn on at the ".config" file to enable the debug for 
brcmsmac or any additional flag it could be interesting for this?

> The regression was caused by following commit:
>
> "brcmsmac: support 4313iPA" b6fc28a158076ca2764edc9a6d1e1402f56e1c0c
>
> If possible you can revert that and see how that goes.

It will cost me a bunch of dislikes ;-) but sure, I'll try and report 
back.

Greetings,

-- 
Camaleón 

  reply	other threads:[~2013-03-18 21:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130317144603.GA4850@stt008.linux.site>
     [not found] ` <1363532310.3937.266.camel@deadeye.wl.decadent.org.uk>
     [not found]   ` <20130317152428.GA4940@stt008.linux.site>
     [not found]     ` <1363544257.3937.278.camel@deadeye.wl.decadent.org.uk>
2013-03-17 21:43       ` Bug#703142: compatibility with alx ? Ben Hutchings
2013-03-20  9:07         ` Luis R. Rodriguez
2013-03-20 14:41           ` Ben Hutchings
2013-03-20 15:50             ` Luis R. Rodriguez
2013-03-20 17:45               ` Ben Hutchings
2013-03-26 15:07                 ` Camaleón
     [not found]     ` <20130317175658.GA8181@elie.Belkin>
     [not found]       ` <20130317182725.GA5811@stt008.linux.site>
     [not found]         ` <20130317183344.GA8786@elie.Belkin>
     [not found]           ` <CAKprTDFhNnGOPHUqg8Wn6Cd170KaeXj7-w-D6wS2Cc38vstt5A@mail.gmail.com>
2013-03-18  8:37             ` Brcmsmac driver woes, possible regression? Jonathan Nieder
2013-03-18 19:38               ` Arend van Spriel
2013-03-18 21:14                 ` Camaleón [this message]
2013-03-18 21:25                   ` Jonathan Nieder
2013-03-19  9:43                     ` Camaleón
2013-03-19 16:21                       ` Camaleón
2013-03-19 16:53                         ` Dan Williams
2013-03-19 17:30                           ` Camaleón
2013-03-19 17:59                             ` Dan Williams
2013-03-19 18:11                               ` Camaleón
2013-03-19 18:16                                 ` Dan Williams
2013-03-19 18:30                                   ` Camaleón
2013-03-19 21:55                         ` Arend van Spriel
2013-03-19 22:11                           ` Dan Williams
2013-03-23 15:28                         ` Camaleón
2013-03-24 10:10                           ` Arend van Spriel
2013-03-24 10:37                             ` Camaleón

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=20130318211428.GA9136@stt008.linux.site \
    --to=noelamac@gmail.com \
    --cc=664767@bugs.debian.org \
    --cc=arend@broadcom.com \
    --cc=jrnieder@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /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.