From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Amitkumar Karwar <akarwar@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
linux-wireless@vger.kernel.org
Subject: Re: Problems with mwifiex_pcie firmware activation
Date: Wed, 15 Jun 2016 09:48:56 +0200 [thread overview]
Message-ID: <20160615074855.GA2663@redhat.com> (raw)
In-Reply-To: <87r3bzkgf1.fsf@purkki.adurom.net>
On Tue, Jun 14, 2016 at 05:12:50PM +0300, Kalle Valo wrote:
> Stanislaw Gruszka <sgruszka@redhat.com> writes:
>
> > Hence looks like forcing firmware upload somehow changed device, now it
> > is capable to initialize. On my second system device is on pristine state
> > and original problem is still reproducible. Do you have good solution
> > for this problem ?
>
> Did you see this:
>
> mwifiex: fix racing condition when downloading firmware
>
> https://patchwork.kernel.org/patch/9123771/
>
> Though I have no idea if it helps in your case, just saw it on my queue
> of patches to apply.
Patch did not help. No wonder since it fixes SDIO and I have problem
with PCIE device :-)
Stanislaw
next prev parent reply other threads:[~2016-06-15 7:49 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 [this message]
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
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=20160615074855.GA2663@redhat.com \
--to=sgruszka@redhat.com \
--cc=akarwar@marvell.com \
--cc=kvalo@codeaurora.org \
--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.