linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Stefan Holzmann <stefan.holzmann@gmx.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: brcmfmac: BCM4343A0 P2P mode problem
Date: Sun, 19 Feb 2017 20:37:25 +0100	[thread overview]
Message-ID: <78cfb1db-150d-b2be-9ef7-6076468678d2@broadcom.com> (raw)
In-Reply-To: <zarafa.58a9eb4f.3258.65a3ba3c60add992@homeserver.home>

On 19-2-2017 20:00, Stefan Holzmann wrote:
> Hello,
> 
> I think my problem was just a firmware version issue. When I use the firmware file "fw_bcm4343.bin" from here https://android.googlesource.com/platform/hardware/broadcom/wlan I'am able establish a P2P connection.
> Is this the latest/recommended firmware version for the chipset?
> 
> Firmware version = wl0: Jul  1 2016 18:02:40 version 7.10.1 (A0 Station/P2P feature) FWID 01-bae8afee

I would suggest looking in linux-firmware repo on kernel.org for
upstream firmware instead of using AOSP firmware. However, I am not
entirely sure whether we have the firmware in place for your chipset.

Could you insert the driver module with parameter debug=0x1416 and send
me dmesg output.

Regards,
Arend

  reply	other threads:[~2017-02-19 19:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19 19:00 brcmfmac: BCM4343A0 P2P mode problem Stefan Holzmann
2017-02-19 19:37 ` Arend Van Spriel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-19 19:59 Stefan Holzmann
2017-02-19  8:03 Stefan Holzmann
2017-02-17 21:33 Stefan Holzmann
2017-02-18 19:25 ` 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=78cfb1db-150d-b2be-9ef7-6076468678d2@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stefan.holzmann@gmx.net \
    /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).