On Wed, 2012-12-12 at 10:13 +0000, Alberto Garau wrote: > Thanks Luca, > > we tried with FALLING_EDGE for the interrupt but the driver got stucked so I had to put again RISING_EDGE. > > We successfully cross compiled iw but also with that tool we always see only on ESSID from one specific AP I didn't expect the scan to improve with iw, but at least now you're using the right tool. :) > while the others ESSID from the second AP are available only sometime. > > That's very strange. > > Do you think we are facing calibration problems ? Yes, I guess calibration is the most likely cause now. > In our CMD0 we have > > bit 13 = 1 IB interrupt is active high > > bit 14 = 1 IB interrupt is open drain > > Do you think is right according do RISING_EDGE interrupt ? I think this is okay. I don't think the problem is the interrupt now. You should try to calibrate your device and generate a proper NVS file. -- 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
