The kernel patch (0001-Update-for-IGEPv2-Wifi-support.patch) already adds the basic SIOCSIWPRIV stuff to the libertas wireless driver. In eclair it is good enough to get wireless running.
Hedwin On Wed, Oct 13, 2010 at 10:58 PM, manish shakya <msha...@oakland.edu> wrote: > > I came to know SIOCSIWPRIV is required in froyo also. Do you have any idea > how it should be implement SIOCSIWPRIV? > > > On Wed, Oct 13, 2010 at 11:57 PM, hedwin <hedwin.kon...@gmail.com> wrote: >> >> Hmm, interesting. Thnx for the feedback. >> >> The vold change was needed in eclair to ignore no SD-card readers >> connected to an mmc interface but vold has changed in froyo so a >> different setup in vold >> could that be the reason that it is not needed anymore. >> Same for SIOCSIWPRIV it is required in by the eclair Wifi layer >> without it doesn't work >> >> The error your seeing is also socket related, it is the connection >> between Wifi and wpa_supplicant. Since creating sockets this way gave >> me >> quite a headache I switched to using the sockets in the android namespace. >> >> Hedwin >> >> >> On Wed, Oct 13, 2010 at 8:34 PM, manish shakya <msha...@oakland.edu> >> wrote: >> > Hi Hedwin, >> > >> > I have solved Timeout problem as you have said in your post.I could not >> > see >> > the need of SIOCSIWPRIV and vold. In my case, permission for sockets are >> > fine. I tried both unix socket and android socket but both of them >> > didn't >> > work. >> > >> > After solving timeout problem,I think ,WPA Supplicant is working fine. >> > It >> > can scan AP and tries to connect with one one AP but it fails. Here is a >> > log >> > I get: >> > >> > D/wpa_supplicant( 1349): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 >> > ([UP]) >> > D/wpa_supplicant( 1349): RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' >> > added >> > D/wpa_supplicant( 1349): Received 731 bytes of scan results (4 BSSes) >> > D/wpa_supplicant( 1349): Scan results: 4 >> > I/wpa_supplicant( 1349): CTRL-EVENT-SCAN-RESULTS Ready >> > D/wpa_supplicant( 1349): Selecting BSS from priority group 0 >> > D/wpa_supplicant( 1349): Try to find WPA-enabled AP >> > D/wpa_supplicant( 1349): 0: 00:12:17:65:c9:f6 ssid='Connect01' >> > wpa_ie_len=26 >> > rsn_ie_len=0 caps=0x11 >> > D/wpa_supplicant( 1349): skip - SSID mismatch >> > D/wpa_supplicant( 1349): 1: 00:1f:ca:5f:c3:f0 ssid='NEDSCHROEF' >> > wpa_ie_len=0 >> > rsn_ie_len=0 caps=0x11 >> > D/wpa_supplicant( 1349): skip - no WPA/RSN IE >> > D/wpa_supplicant( 1349): 2: 94:44:52:62:94:31 ssid='Belkin.3431' >> > wpa_ie_len=0 rsn_ie_len=0 caps=0x1 >> > D/wpa_supplicant( 1349): skip - no WPA/RSN IE >> > D/wpa_supplicant( 1349): 3: 00:12:17:65:d9:4e ssid='Seminar ' >> > wpa_ie_len=0 >> > rsn_ie_len=0 caps=0x1 >> > D/wpa_supplicant( 1349): skip - no WPA/RSN IE >> > D/wpa_supplicant( 1349): Try to find non-WPA AP >> > D/wpa_supplicant( 1349): 0: 00:12:17:65:c9:f6 ssid='Connect01' >> > wpa_ie_len=26 >> > rsn_ie_len=0 caps=0x11 >> > D/wpa_supplicant( 1349): skip - privacy mismatch >> > D/wpa_supplicant( 1349): 1: 00:1f:ca:5f:c3:f0 ssid='NEDSCHROEF' >> > wpa_ie_len=0 >> > rsn_ie_len=0 caps=0x11 >> > D/wpa_supplicant( 1349): skip - privacy mismatch >> > D/wpa_supplicant( 1349): 2: 94:44:52:62:94:31 ssid='Belkin.3431' >> > wpa_ie_len=0 rsn_ie_len=0 caps=0x1 >> > D/wpa_supplicant( 1349): selected non-WPA AP 94:44:52:62:94:31 >> > ssid='Belkin.3431' >> > I/wpa_supplicant( 1349): Trying to associate with 94:44:52:62:94:31 >> > (SSID='Belkin.3431' freq=2412 MHz) >> > D/wpa_supplicant( 1349): Cancelling scan request >> > D/wpa_supplicant( 1349): WPA: clearing own WPA/RSN IE >> > D/wpa_supplicant( 1349): Automatic auth_alg selection: 0x1 >> > D/wpa_supplicant( 1349): WPA: clearing AP WPA IE >> > D/wpa_supplicant( 1349): WPA: clearing AP RSN IE >> > D/wpa_supplicant( 1349): WPA: clearing own WPA/RSN IE >> > D/wpa_supplicant( 1349): No keys have been configured - skip key >> > clearing >> > D/wpa_supplicant( 1349): wpa_driver_wext_set_drop_unencrypted >> > D/wpa_supplicant( 1349): State: SCANNING -> ASSOCIATING >> > I/wpa_supplicant( 1349): CTRL-EVENT-STATE-CHANGE id=-1 state=3 >> > D/wpa_supplicant( 1349): wpa_driver_wext_set_operstate: operstate 0->0 >> > (DORMANT) >> > D/wpa_supplicant( 1349): WEXT: Operstate: linkmode=-1, operstate=5 >> > D/wpa_supplicant( 1349): wpa_driver_wext_associate >> > D/wpa_supplicant( 1349): Setting authentication timeout: 10 sec 0 usec >> > D/wpa_supplicant( 1349): EAPOL: External notification - >> > portControl=ForceAuthorized >> > D/wpa_supplicant( 1349): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 >> > ([UP]) >> > D/wpa_supplicant( 1349): RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' >> > added >> > D/wpa_supplicant( 1349): Wireless event: cmd=0x8b06 len=8 >> > D/wpa_supplicant( 1349): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 >> > ([UP]) >> > D/wpa_supplicant( 1349): RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' >> > added >> > D/wpa_supplicant( 1349): Wireless event: cmd=0x8b04 len=12 >> > D/wpa_supplicant( 1349): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 >> > ([UP]) >> > D/wpa_supplicant( 1349): RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' >> > added >> > D/wpa_supplicant( 1349): Wireless event: cmd=0x8b1a len=19 >> > >> > >> > Interface wlan0 is added a lot of times.why?? >> > >> > >> > I also get following error. >> > E/WifiHW ( 1178): Unable to open connection to supplicant on >> > "/data/system/wpa_supplicant/wlan0": No such file or directory >> > >> > >> > With Regards, >> > Manish Shakya >> > >> > On Wed, Oct 13, 2010 at 10:23 AM, hedwin <hedwin.kon...@gmail.com> >> > wrote: >> >> >> >> kernel version is 2.6.32 but it is done in eclair. But what I've seen >> >> sofar is that there is not that much difference compared to froyo. >> >> >> >> ok, let me know if you run into issues. >> >> >> >> Cheers, >> >> Hedwin >> >> >> >> >> >> On Wed, Oct 13, 2010 at 4:07 PM, manish shakya >> >> <manishshakya...@gmail.com> wrote: >> >> > Hi Hedwin, >> >> > >> >> > Thanks. Good to know you made wifi working. Which version of kernel >> >> > are >> >> > you using ? I am using kernel 2.6.32 and Android 2.2 . >> >> > >> >> > I am going through you posts in rowboat mailing list. I will update >> >> > my >> >> > findings. >> >> > >> >> > >> >> > On Wed, Oct 13, 2010 at 5:49 AM, hedwin <hedwin.kon...@gmail.com> >> >> > wrote: >> >> >> >> >> >> Hi >> >> >> >> >> >> Made android wifi work on a IGEPv2 board. This board also uses a >> >> >> Marvell >> >> >> chip. >> >> >> You can find my patches in the android rowboat mailing list. >> >> >> >> >> >> Btw the problem you encounter is due to the fact that the mmc gets >> >> >> disabled while wifi is still operational. >> >> >> >> >> >> Hedwin. >> >> >> >> >> >> On Tue, Oct 12, 2010 at 4:56 PM, Manish <manishshakya...@gmail.com> >> >> >> wrote: >> >> >> > Hi , >> >> >> > >> >> >> > There is no place to generate those bin files. >> >> >> > >> >> >> > On Oct 12, 8:01 am, manish shakya <manishshakya...@gmail.com> >> >> >> > wrote: >> >> >> >> Hi Hairui >> >> >> >> >> >> >> >> Thanks for your response. >> >> >> >> >> >> >> >> Let me try to re-compiling the modules and generate sd8686.bin >> >> >> >> and >> >> >> >> sd8686_helper.bin files. >> >> >> >> BTW, what are those bin files for? >> >> >> >> >> >> >> >> ManishOn Mon, Oct 11, 2010 at 11:11 PM, hairui >> >> >> >> <szhai...@gmail.com> >> >> >> >> wrote: >> >> >> >> > Maybe you should re-compile the modules for yourself arch which >> >> >> >> > you >> >> >> >> > chose to use the prebuild one. >> >> >> >> >> >> >> >> > On 10月12日, 上午2时50分, manish shakya <manishshakya...@gmail.com> >> >> >> >> > wrote: >> >> >> >> > > Hi everyone, >> >> >> >> >> >> >> >> > > I am trying to make Marvell Wifi to work on overo board >> >> >> >> > > running >> >> >> >> > > Android. >> >> >> >> > I >> >> >> >> > > am using 2.6.32 linux kernel and Android 2.2. I have put all >> >> >> >> > > files( >> >> >> >> > > libertas_sdio.ko, sd8686.bin,sd8686_helper.bin etc) in >> >> >> >> > > required >> >> >> >> > > place. >> >> >> >> > > I am using d8686.bin,sd8686_helper.bin from console prebuilt >> >> >> >> > > image >> >> >> >> > (2.6.34 >> >> >> >> > > linux ) from gumstix.It seems that libertas driver is loaded >> >> >> >> > > and >> >> >> >> > > driver >> >> >> >> > is >> >> >> >> > > able to find MAC address of the chip. But the problem is >> >> >> >> > > there >> >> >> >> > > are >> >> >> >> > > a lot >> >> >> >> > of >> >> >> >> > > time out after that. It seems chip is not getting >> >> >> >> > > command send by the processor. Below is log that I get: >> >> >> >> >> >> >> >> > > libertas_sdio: Libertas SDIO driver >> >> >> >> > > libertas_sdio: Copyright Pierre Ossman >> >> >> >> > > libertas_sdio mmc1:0001:1: firmware: requesting >> >> >> >> > > sd8686_helper.bin >> >> >> >> > > init: untracked pid 1221 exited >> >> >> >> > > libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin >> >> >> >> > > init: untracked pid 1224 exited >> >> >> >> > > libertas: 00:19:88:37:0e:dd, fw 9.70.7p0, cap 0x00000303 >> >> >> >> > > libertas: wlan0: Marvell WLAN 802.11 adapter >> >> >> >> > > libertas: command 0x0006 timed out >> >> >> >> > > libertas: requeueing command 0x0006 due to timeout (#1) >> >> >> >> > > libertas: Received result 0 to command 6 after 1 retries >> >> >> >> > > libertas: command 0x0013 timed out >> >> >> >> > > libertas: requeueing command 0x0013 due to timeout (#1) >> >> >> >> > > libertas: command 0x0013 timed out >> >> >> >> > > libertas: requeueing command 0x0013 due to timeout (#2) >> >> >> >> > > libertas: command 0x0013 timed out >> >> >> >> > > libertas: requeueing command 0x0013 due to timeout (#3) >> >> >> >> > > libertas: command 0x0013 timed out >> >> >> >> > > libertas: Excessive timeouts submitting command 0x0013 >> >> >> >> > > libertas: PREP_CMD: command 0x0013 failed: -110 >> >> >> >> > > libertas: command 0x0010 timed out >> >> >> >> > > libertas: requeueing command 0x0010 due to timeout (#1) >> >> >> >> > > libertas: command 0x0010 timed out >> >> >> >> > > libertas: requeueing command 0x0010 due to timeout (#2) >> >> >> >> > > libertas: command 0x0010 timed out >> >> >> >> > > libertas: requeueing command 0x0010 due to timeout (#3) >> >> >> >> > > libertas: command 0x0010 timed out >> >> >> >> > > libertas: Excessive timeouts submitting command 0x0010 >> >> >> >> > > libertas: command 0x0010 timed out >> >> >> >> > > libertas: requeueing command 0x0010 due to timeout (#1) >> >> >> >> > > libertas: command 0x0010 timed out >> >> >> >> > > libertas: requeueing command 0x0010 due to timeout (#2) >> >> >> >> > > libertas: command 0x0010 timed out >> >> >> >> > > libertas: requeueing command 0x0010 due to timeout (#3) >> >> >> >> > > libertas: command 0x0010 timed out >> >> >> >> > > libertas: Excessive timeouts submitting command 0x0010 >> >> >> >> > > libertas: command 0x0006 timed out >> >> >> >> > > libertas: requeueing command 0x0006 due to timeout (#1) >> >> >> >> > > libertas: command 0x0006 timed out >> >> >> >> > > libertas: requeueing command 0x0006 due to timeout (#2) >> >> >> >> > > libertas: command 0x0006 timed out >> >> >> >> > > libertas: requeueing command 0x0006 due to timeout (#3) >> >> >> >> > > libertas: command 0x0006 timed out >> >> >> >> > > libertas: Excessive timeouts submitting command 0x0006 >> >> >> >> > > libertas: PREP_CMD: command 0x0006 failed: -110 >> >> >> >> > > libertas: SCAN_CMD failed >> >> >> >> > > libertas: command 0x0028 timed out >> >> >> >> > > libertas: requeueing command 0x0028 due to timeout (#1) >> >> >> >> > > libertas: command 0x0028 timed out >> >> >> >> > > libertas: requeueing command 0x0028 due to timeout (#2) >> >> >> >> > > libertas: command 0x0028 timed out >> >> >> >> > > libertas: requeueing command 0x0028 due to timeout (#3) >> >> >> >> > > libertas: command 0x0028 timed out >> >> >> >> > > libertas: Excessive timeouts submitting command 0x0028 >> >> >> >> > > libertas: command 0x002f timed out >> >> >> >> > > libertas: requeueing command 0x002f due to timeout (#1) >> >> >> >> > > libertas: command 0x002f timed out >> >> >> >> > > libertas: requeueing command 0x002f due to timeout (#2) >> >> >> >> > > libertas: command 0x002f timed out >> >> >> >> > > libertas: requeueing command 0x002f due to timeout (#3) >> >> >> >> > > libertas: command 0x002f timed out >> >> >> >> > > libertas: Excessive timeouts submitting command 0x002f >> >> >> >> > > libertas: PREP_CMD: command 0x002f failed: -110 >> >> >> >> >> >> >> >> > > Any ideas would be really appreciated. >> >> >> >> >> >> >> >> > > Manish Shakya >> >> >> >> >> >> >> >> > -- >> >> >> >> > unsubscribe: >> >> >> >> > >> >> >> >> > >> >> >> >> > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> >> >> >> >> > website:http://groups.google.com/group/android-porting >> >> >> >> >> >> >> >> >> >> >> > >> >> >> > -- >> >> >> > unsubscribe: android-porting+unsubscr...@googlegroups.com >> >> >> > website: http://groups.google.com/group/android-porting >> >> >> > >> >> > >> >> > >> >> > >> >> > -- >> >> > Manish Shakya >> >> > http://www.manishshakya.com.np >> >> > http://secs.oakland.edu/~ganesan/iMX/ >> >> > >> > >> > >> > >> > -- >> > Manish Shakya >> > http://www.manishshakya.com.np >> > http://secs.oakland.edu/~ganesan/iMX/ >> > > > > > -- > Manish Shakya > http://www.manishshakya.com.np > http://secs.oakland.edu/~ganesan/iMX/ > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
