> Nicu Pavel wrote: >> >> The differences is that driver_wext.c expects the wifi kernel driver >> to implement the SIOCSIWPRIV ioctl and respond to android commands >> like RSSI, MACADDR etc, while driver_awext.c replies to android >> commands by using standard wireless extensions ioctls and works for >> most wifi drivers. >> 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-driver-awext-to-emulate-Android-dri.patch >> > > 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/commit/0079ce31faa15d882272891661493ce734e5ab3e > > 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: [email protected] website: http://groups.google.com/group/android-porting
