From: Arend van Spriel <arend@broadcom.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-wireless Mailing List <linux-wireless@vger.kernel.org>,
Franky Lin <frankyl@broadcom.com>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: brcmfmac not working on ECS LIVA
Date: Tue, 11 Nov 2014 12:08:43 +0100 [thread overview]
Message-ID: <5461EE3B.8040301@broadcom.com> (raw)
In-Reply-To: <CAMP44s1NiYrFkN=DQcyGiJyW+JvCGvRVzcEBGLtvGyhfWs17kQ@mail.gmail.com>
On 10-11-14 21:48, Felipe Contreras wrote:
> Hi,
>
> On Sun, Nov 9, 2014 at 4:46 AM, Arend van Spriel <arend@broadcom.com> wrote:
>
>> The ideas may come to us with a bit more trace information. The logging
>> above is the usual stuff so no problem indication there.
>>
>> I looked at the nvram file from [1]. At the end there are some entries about
>> OOB wakeup, ie. starting with 'sd_'. You may remove those, but giving the
>> logging it would not be the first thing to do.
>
> I removed the sd_ lines, it didn't help.
>
>> Could you share the nvram obtained from EFI? Also please create a kernel log
>> with debug=0xd416.
>
> Sure, the nvram file is here:
>
> http://pastie.org/9710358
>
> I tried adding this file:
>
> /etc/modprobe.d/brcmfmac.conf
> options brcmfmac debug=0xd416
>
> I see nothing extra in the debug log... Am I doing something wrong?
Not sure. You can verify and set the log level through sysfs, ie.:
$ cat /sys/module/brcmfmac/parameters/debug
To set it:
$ echo 0xd416 > /sys/module/brcmfmac/parameters/debug
Regards,
Arend
next prev parent reply other threads:[~2014-11-11 11:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 20:39 brcmfmac not working on ECS LIVA Felipe Contreras
2014-11-09 10:46 ` Arend van Spriel
2014-11-10 20:48 ` Felipe Contreras
2014-11-11 11:08 ` Arend van Spriel [this message]
2014-11-11 18:32 ` Felipe Contreras
2014-11-11 18:35 ` Arend van Spriel
2014-11-11 18:49 ` Felipe Contreras
2014-11-11 19:10 ` Arend van Spriel
2014-11-11 19:13 ` Felipe Contreras
2014-11-11 22:32 ` Felipe Contreras
2014-11-12 10:40 ` Arend van Spriel
2014-11-12 15:23 ` Felipe Contreras
2014-11-13 10:47 ` Arend van Spriel
2014-11-14 17:03 ` Felipe Contreras
2014-11-14 19:30 ` 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=5461EE3B.8040301@broadcom.com \
--to=arend@broadcom.com \
--cc=felipe.contreras@gmail.com \
--cc=frankyl@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@linux.intel.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.