From: Michael Howard <mike@dewberryfields.co.uk>
To: linux-wireless@vger.kernel.org
Subject: Re: Mwifiex driver on Globalscale Mirabox
Date: Thu, 15 May 2014 18:15:36 +0100 [thread overview]
Message-ID: <5374F638.6000505@dewberryfields.co.uk> (raw)
In-Reply-To: <CAJwzM1k+75qRJaONyehMNPaOqOHyBhryMGBtZ4NpD6jGHk-cHQ@mail.gmail.com>
On 15/05/2014 15:06, Avinash Patil wrote:
> Hi James/Anthony,
>
> If an unsupported command is downloaded to FW, it results into command
> response not supported - code 0x2.
> It wouldnt result into command timeout.
> According to our internal discussions, this issue is seen only on
> Globalscale mirabox where SDIO controller is mvsdio.
>
> "On Mirabox the SDIO controller is mvsdio. It polls for interrupts but
> polling itself doesn’t seem to be the problem.
> In the log, I got from another person it seems that there is no
> SDIO_INT bit in controller “intr” register after scan command is sent.
> Other commands are fine, only scan commands fail. I don’t why scan
> (0x06 or 0x107) is special in this case."
>
> Hi Anthony,
>
> Could you please enable dynamic debug on mwifiex, mwifiex_sdio &
> mvsdio driver; this will confirm if this is same issue.
>
> Thanks,
> Avinash.
>
Using kernel 3.15.0-rc5, starting hostapd results in;
May 15 17:11:04 mirabox kernel: mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd
0x112 error, result=0x2
hostapd runs but there in no AP.
If I can be of any help testing/debugging just say so.
Cheers,
Mike.
--
next prev parent reply other threads:[~2014-05-15 17:20 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
2014-05-15 14:06 ` Avinash Patil
2014-05-15 17:15 ` Michael Howard [this message]
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=5374F638.6000505@dewberryfields.co.uk \
--to=mike@dewberryfields.co.uk \
--cc=linux-wireless@vger.kernel.org \
/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.