By the way,after the modification ,I didn't use make to build the whole system ,but just build it with mm and then copy wpa_cli wpa_supplicant and wpa_client.so to the file system. Does this matter? Thanks --Weber On May 27, 6:08 pm, Nicu Pavel <npa...@ituner.com> wrote: > > Nicu Pavel wrote: > > >> The differences is that driver_wext.c expects thewifikernel driver > >> to implement the SIOCSIWPRIV ioctl and respond toandroidcommands > >> like RSSI, MACADDR etc, while driver_awext.c replies toandroid > >> commands by using standard wireless extensions ioctls and works for > >> mostwifidrivers. > >> Basically driver_awext.c is a wrapper for driver_wext.c and only > >> reimplements function wpa_driver_priv_driver_cmd(). > > >> Direct link to the patch: > > >>http://www.linuxconsulting.ro/android/patches/0001-Added-a-separate-d... > > > I have done somenthing different using your code. Instead of creating a new > > file just emulate the call in wext part > > >http://gitorious.org/flow-g1-5/platform_external_wpa_supplicant/commi... > > > What do you think? (NEED TO BE TEST) > > I didn't want to touch google code, that's why I made a separate file, > if I have a product with a bcm card for example I can build with WEXT > driver if not I'm building with AWEXT driver. > > Nicu Pavel
-- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
