linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Ian Molton <ian@mnementh.co.uk>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Franky Lin <franky.lin@broadcom.com>,
	Hante Meuleman <hante.meuleman@broadcom.com>
Subject: Re: BUG: brcmfmac: add firmware feature detection for gscan feature breaks 43430a1
Date: Mon, 17 Jul 2017 23:31:41 +0200	[thread overview]
Message-ID: <0271ee86-ba99-fc50-46cd-b796f614fa19@broadcom.com> (raw)
In-Reply-To: <246dc2f3-5cfd-7e89-6244-50fa2f546306@mnementh.co.uk>



On 17-07-17 22:41, Ian Molton wrote:
> On 17/07/17 21:36, Arend van Spriel wrote:
> 
>> In <debugfs_mountpoint>/brcmfmac/*/forensics, but you have to load the
>> driver with modules parameter 'ignore_probe_fail=1' to avoid the driver
>> remove tearing down all debugfs stuff.
> 
> modinfo shows:
> 
> parm:           txglomsz:Maximum tx packet chain size [SDIO] (int)
> parm:           debug:Level of debug output (int)
> parm:           p2pon:Enable legacy p2p management functionality (int)
> parm:           feature_disable:Disable features (int)
> parm:           alternative_fw_path:Alternative firmware path (string)
> parm:           fcmode:Mode of firmware signalled flow control (int)
> parm:           roamoff:Do not use internal roaming engine (int)
> 

Seems you did not build with CONFIG_BRCMDBG?

common.c:

#ifdef DEBUG
/* always succeed brcmf_bus_started() */
static int brcmf_ignore_probe_fail;
module_param_named(ignore_probe_fail, brcmf_ignore_probe_fail, int, 0);
MODULE_PARM_DESC(ignore_probe_fail, "always succeed probe for debugging");
#endif

Regards,
Arend

  reply	other threads:[~2017-07-17 21:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 17:50 BUG: brcmfmac: add firmware feature detection for gscan feature breaks 43430a1 Ian Molton
2017-07-17 18:31 ` Ian Molton
2017-07-17 19:53   ` Arend van Spriel
2017-07-17 20:13     ` Ian Molton
2017-07-17 20:36       ` Arend van Spriel
2017-07-17 20:41         ` Ian Molton
2017-07-17 21:31           ` Arend van Spriel [this message]
2017-07-17 22:02             ` Ian Molton
2017-07-17 22:10             ` Ian Molton
2017-07-18 19:49               ` 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=0271ee86-ba99-fc50-46cd-b796f614fa19@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=franky.lin@broadcom.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=ian@mnementh.co.uk \
    --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 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).