On Tue, 2014-03-25 at 09:48 +0800, Jaya Kumar wrote: > On Tue, Mar 25, 2014 at 2:32 AM, Luca Coelho <luca@xxxxxxxxx> wrote: > >> The good news is that > >>the chip is detected and wl12xx/wl12xx_sdio loads. However, I haven't > >>been able to get it to get any scan results and can't associate with > >>any AP (even open). > > > > Usually this happens because you're not getting any interrupts. Are you sure the WLAN IRQ GPIO is correctly configured? > > > > There's nothing very useful in those kids > > It just shows that the scan command was issued but you never got the scan complete interrupt. > > > > Hi Luca, > > Thanks for your reply. I think the wlan irq gpio is configured. When I > look at /proc/interrupts, I see it increasing each time I try to scan. Interesting. Try to take more logs, use 6625 for instance. This will produce a lot of messages. Another common cause for failed scan (and RX in general) is a wrong clock frequency for the WiLink chip. Make sure you're using the correct values in your board file. HTH. -- Luca. -- 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
