Hi Brent, On 08/04/2011 03:55 PM, Brent Taylor wrote: > Kalle Valo <kvalo@...> writes: > >> >> Brent Taylor <btaylor1@...> writes: >> >>> Fixed ... realized that I was using the wrong firmware images. I was >>> using an older image from AR6K_FW.3.0_RC.233. >> >> Good that your issue was solved and thanks for letting us now. But >> nevertheless the driver should not lockup in there's a problem with >> firmware, ath6kl is definitely buggy here. > > My lockup (due to wrong firmware) was caused by the function > ath6kl_bmi_get_lkahd in bmi.c. The function was called with the parameter > "need_timeout = false". This causes the while loop to wait for a response from > the chip. Since the wrong firmware image was used, the chip will never respond. Thanks for the analysis. Yesterday I submitted a patch for review which will fix this. > Is it possible for the ath6kl driver to somehow read the firmware version from > the firmware file before sending it to the chip? Not right now. But in the new firmware image format (for which I also sent patches yesterday) we can do that. You can even check the firmware just with the strings command. Thank you for the feedback, I appreciate it. Kalle -- 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
