From: James Cameron <quozl@laptop.org>
To: WebAV <webav@free.fr>
Cc: Avinash Patil <avinashapatil@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Mwifiex driver on Globalscale Mirabox
Date: Thu, 15 May 2014 07:51:26 +1000 [thread overview]
Message-ID: <20140514215126.GA15419@us.netrek.org> (raw)
In-Reply-To: <53733AB4.7010500@free.fr>
On Wed, May 14, 2014 at 11:43:16AM +0200, WebAV wrote:
> The FW is mwifiex 1.0 (14.66.9.p96) which I think is the last one.
> [...]
> mwifiex_sdio mmc0:0001:1: cmd: DNLD_CMD: (1397151023.654452): 0x107,
> [...]
> mwifiex_sdio mmc0:0001:1: mwifiex_cmd_timeout_func: Timeout cmd id (1397151033.670677) = 0x107, act = 0x0
My guess is that the driver has sent an extended scan command to
firmware which does not support it, the result is a timeout. If I'm
right, what we're missing is a patch that uses the new fw_api_ver
before scan.
The inability to recover afterwards is a different problem.
--
James Cameron
http://quozl.linux.org.au/
next prev parent reply other threads:[~2014-05-14 21:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 18:11 Mwifiex driver on Globascal Mirabox WebAV
2014-04-11 6:54 ` Avinash Patil
2014-04-11 14:50 ` Mwifiex driver on Globalscale Mirabox WebAV
2014-05-14 9:43 ` WebAV
2014-05-14 21:51 ` James Cameron [this message]
2014-05-15 14:06 ` Avinash Patil
2014-05-15 17:15 ` Michael Howard
2014-05-16 4:09 ` Avinash Patil
[not found] ` <CAJwzM1mg5KVZFev4Gs9Qw43H5OwiLF3fmhwv8-3y9mEvWM6b6g@mail.gmail.com>
2014-05-17 14:39 ` Michael Howard
2014-05-22 4:59 ` Bing Zhao
2014-05-21 11:04 ` Michael Howard
2014-05-15 21:41 ` James Cameron
2014-05-16 4:21 ` Avinash Patil
2014-05-15 22:03 ` WebAV
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=20140514215126.GA15419@us.netrek.org \
--to=quozl@laptop.org \
--cc=avinashapatil@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=webav@free.fr \
/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).