archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <>
To: Ian Molton <>,
	"" <>
Cc: Franky Lin <>,
	Hante Meuleman <>
Subject: Re: BUG: brcmfmac: add firmware feature detection for gscan feature breaks 43430a1
Date: Mon, 17 Jul 2017 22:36:37 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 17-07-17 22:13, Ian Molton wrote:
> On 17/07/17 20:53, Arend van Spriel wrote:
>>> 2) The firmware is failing when asked to handle the new requiests, and
>>>    is going to la-la land.
>> taken a wrong turn straight into la-la land.
> Doh!
>>> I have version wl0: Aug 29 2016 20:48:16 version (r640327)
>>> FWID 01-4527cfab
>> Not so much newer firmware, but I used a different chip when
>> implementing the multi-scheduled scan patches. I tried some other
>> devices, but not the bcm4343{0,8}. Now as far as I can see over here the
>> brcmfmac43430-sdio.bin is not built with gscan support so it should just
>> return firmware errorcode, ie. -23. So it would be interesting to see
>> what firmware has to say. Can you load the driver with
>> ignore_probe_fail=1 and dump the forensics file in debugfs.
> I don't appear to get anything useful in debugfs. Where should I be looking?

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.

  reply	other threads:[~2017-07-17 20:36 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 [this message]
2017-07-17 20:41         ` Ian Molton
2017-07-17 21:31           ` Arend van Spriel
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).