All of lore.kernel.org
 help / color / mirror / Atom feed
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 19:35:15 +0100	[thread overview]
Message-ID: <546256E3.1080606@broadcom.com> (raw)
In-Reply-To: <CAMP44s10T_mxqLigrPf_Ox4jej--87QmjG7cNjT8o_qyU2HXjg@mail.gmail.com>

On 11-11-14 19:32, Felipe Contreras wrote:
> On Tue, Nov 11, 2014 at 5:08 AM, Arend van Spriel <arend@broadcom.com> wrote:
>> On 10-11-14 21:48, Felipe Contreras wrote:
> 
>>> /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
> 
> 54294
> 
> I guess ArchLinux's kernel is missing some configuration option needed
> for the debugging.

Can you boot the kernel with 'debug ignore_loglevel' on the kernel
command line.

Regards,
Arend


  reply	other threads:[~2014-11-11 18:35 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
2014-11-11 18:32       ` Felipe Contreras
2014-11-11 18:35         ` Arend van Spriel [this message]
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=546256E3.1080606@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.