From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: Nishant Sarmukadam <nishants@marvell.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Problems with mwifiex_pcie firmware activation
Date: Mon, 14 Nov 2016 11:15:44 +0100 [thread overview]
Message-ID: <20161114101544.GA13943@redhat.com> (raw)
In-Reply-To: <20160825150626.GA9256@redhat.com>
On Thu, Aug 25, 2016 at 05:06:26PM +0200, Stanislaw Gruszka wrote:
> On Fri, Aug 12, 2016 at 10:13:43AM +0200, Stanislaw Gruszka wrote:
> > On Fri, Aug 12, 2016 at 07:17:38AM +0000, Amitkumar Karwar wrote:
> > > The problem looks strange. The patch just splits mwifiex_check_fw_status() and increases poll count. It should not have any side-effects.
> > > Our code used to check winner status before this patch also.
> >
> > Ok, I misread the patch. Anyway checking "winner status" seems
> > does not work well on some condition and prevent loading firmware
> > into device.
>
> I debug this a bit more on latest wireless-testing-next tree + 3 patches
> I just posted and debug_mask=0x700000ff.
>
> On broken system, we do not download FW to device when system is
> rebooted, due to PCI-E is not the winner. However if system is
> powered OFF and then powered ON, we do FW downloading. Hence
> download the new FW into device does not make it work as was
> my theory.
>
> In attachments are full dmesgs of good/bad and reboot/power-off-on
> cases.
>
> The difference is that on broken system FW (or HW) do not create
> new USB Bluetooth device (1286:2046) and do not report
> FIRMWARE_READY_PCIE. Additionally on reboot case there are errors
> from USB xhci.
It was discovered that not working device require pcie8897_uapsta.bin
firmware from ubuntu package to work:
https://launchpad.net/~snappy-dev/+archive/ubuntu/snappy-devices/+sourcepub/5936055/+listing-archive-extra
Device initialize like this then:
[ 15.374630] mwifiex_pcie 0000:02:00.0: info: FW download over, size 689624 bytes
[ 16.101214] mwifiex_pcie 0000:02:00.0: WLAN FW is active
[ 16.242825] mwifiex_pcie 0000:02:00.0: info: MWIFIEX VERSION: mwifiex 1.0 (15.150.13.p21)
[ 16.251231] mwifiex_pcie 0000:02:00.0: driver_version = mwifiex 1.0 (15.150.13.p21)
I'm not sure where ubuntu get this 15.150.13.p21 version of firmware as
it seems it's not present nor in upstream linux-firmware repo not in
http://git.marvell.com/?p=mwifiex-firmware.git;a=summary
Anyway could you modify firmware to support this device or modify
driver to load 15.150.13.p21 if required and push this F/W image
upstream ?
Thanks
Stanislaw
next prev parent reply other threads:[~2016-11-14 10:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 13:50 Problems with mwifiex_pcie firmware activation Stanislaw Gruszka
2016-06-14 14:12 ` Kalle Valo
2016-06-15 7:48 ` Stanislaw Gruszka
2016-06-15 13:47 ` Amitkumar Karwar
2016-06-16 11:53 ` Stanislaw Gruszka
2016-06-23 12:09 ` Stanislaw Gruszka
2016-08-11 9:01 ` Stanislaw Gruszka
2016-08-11 10:21 ` Amitkumar Karwar
2016-08-11 12:29 ` Stanislaw Gruszka
2016-08-12 7:17 ` Amitkumar Karwar
2016-08-12 8:13 ` Stanislaw Gruszka
2016-08-25 15:06 ` Stanislaw Gruszka
2016-11-14 10:15 ` Stanislaw Gruszka [this message]
2016-11-16 6:03 ` Amitkumar Karwar
2016-11-21 12:20 ` 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=20161114101544.GA13943@redhat.com \
--to=sgruszka@redhat.com \
--cc=akarwar@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.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.