Search Linux Wireless

Re: Mwifiex driver on Globalscale Mirabox

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




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.

--


--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux