All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: BCM4356 does not initalize after firmware update
Date: Tue, 19 Dec 2017 12:36:36 +0100	[thread overview]
Message-ID: <5A38F9C4.3050202@broadcom.com> (raw)
In-Reply-To: <20171215122045.GB2742@redhat.com>

On 12/15/2017 1:20 PM, Stanislaw Gruszka wrote:
> On Fri, Dec 15, 2017 at 12:10:34PM +0100, Arend van Spriel wrote:
>> # cat /sys/kernel/debug/brcmfmac/0000:03:00.0/revinfo
>
> vendorid: 0x14e4
> deviceid: 0x43ec
> radiorev: 0.41.32.105
> chipnum: 17238 (4356)
> chiprev: 2
> chippkg: 2
> corerev: 48
> boardid: 0x0777
> boardvendor: 0x14e4
> boardrev: P103
> driverrev: 7.35.180.119
> ucoderev: 0
> bus: 0
> phytype: 11
> phyrev: 17
> anarev: 0
> nvramrev: 00000000

Thanks for the info. I was looking for the board info. It seems we do 
not have an nvram file for that specific board.

For SDIO devices I would suggest to use the module parameter 
'ignore_probe_fail' so we could do post-mortem stuff with the driver 
bound to the device, but for PCIe there are not much debug options. Let 
me work on that. May take a bit longer though.

Regards,
Arend

  reply	other threads:[~2017-12-19 11:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 16:12 BCM4356 does not initalize after firmware update Stanislaw Gruszka
2017-12-14  9:13 ` Arend van Spriel
2017-12-14 14:22   ` Stanislaw Gruszka
2017-12-15  9:58     ` Arend van Spriel
2017-12-15 10:32       ` Stanislaw Gruszka
2017-12-15 11:10         ` Arend van Spriel
2017-12-15 12:20           ` Stanislaw Gruszka
2017-12-19 11:36             ` Arend van Spriel [this message]
2017-12-19 12:23               ` Stanislaw Gruszka
2017-12-20  8:46                 ` Arend van Spriel
2017-12-20 10:15                   ` Stanislaw Gruszka

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=5A38F9C4.3050202@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.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.