On Thu, Apr 16, 2015 at 11:10:02AM +0200, Florian Achleitner wrote: > Is the necessity of frequent hardware resets a commonly known issue > with this chip/firmware? Anybody else experiencing these? Yes, but how frequent? > Currently, we see three different scenarios. One of them is > currently not answered by reset. Refer to the upcoming patch. > > (1) mwifiex_cmd_timeout_func: Timeout cmd .. Ok, after reset. See this a lot during heavy testing. > (2) Firmware wakeup failed.. Ok, after reset. Never see this. > (3) DNLD_CMD: host to card failed. No reset triggered. See patch. Very rarely see this. However, our experience may not be comparable; we are using 8787 with a 3.5 kernel, because we haven't the resources to use a later kernel or get backports working. Also, we use WOL (wake on lan) heavily; frequent automatic suspends, with a GPIO wakeup in addition to the SDHCI. -- James Cameron http://quozl.linux.org.au/ -- 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
