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 while the others ESSID from the second AP are available only sometime. That's very strange. Do you think we are facing calibration problems ? 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 ? Thanks Alberto -----Original Message----- From: Luciano Coelho [mailto:coelho@xxxxxx] Sent: mercoledì 12 dicembre 2012 09:45 To: Alberto Garau Cc: linux-wireless@xxxxxxxxxxxxxxx; Ido Yariv; Arik Nemtsov; Adriano Melis; Luca Fresi Subject: Re: wl12xx over spi with no scan results On Wed, 2012-12-12 at 08:18 +0000, Alberto Garau wrote: > Hi Luca, > > yes that's a great news for us. > > Yesterday afternoon with "iwlist wlan0 scan" (not "iw" yet) I saw also > other two networks essids (for a small amount of seconds only) which I'm interested in. > > This seems to say that the networks I would like to connect to are available to the wl1271. > > In the meantime that I'm cross building "iw", I would like to connect to an unprotected network called "Inpeco-test"(no WEP, no WPA). > > Would you be so kind to suggest me the serie of commands I have to > launch to connect to this network ? I would like then to ping outside of course. ifconfig wlan0 up iw wlan0 connect -w Inpeco-test Then, to ping, you need to set your IP address, either with a DHCP client or statically. > I have got also one technical question. In the source code of the > driver I have found for wl1271_spi.c in kernel > 2.6.37 I have interrupts set in RISING_EDGE while the datasheet (in attachment: 4.1.18 at pag 19) talks about FALLING_EDGE. > Which is the right setting to be applied and why ? We currently use level and high with one shot as default. There are some platforms that use rising, though, so we have a platform_quirk value that enables us to toggle that. You could be missing some interrupts by using rising and this could be the reason why you don't see the SSIDs consistently. -- Luca. ��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
