[android-porting] Re: Porting a WiFi Driver on a android supported platform

2009-03-17 Thread >;> Jith911
In you supplicant conf file.. try mentioning.. ctrl_interface=DIR=/data/system/wpa_supplicant/ GROUP=system By default the permission of the socket would be root and the service running on behalf of system won't b able to access it. -JJ. On Mar 16, 1:01 pm, SH wrote: > I am getting the foll

[android-porting] Re: Unable to open connection to wpa_supplicant error

2009-02-10 Thread >;> Jith911
Hi Sean McNeil, I had done those changes to driver_wext.c. Thanks, Jithu. On Feb 11, 7:44 am, ">> Jith911" wrote: > Thanks Pavan, I will check it. > > On Feb 10, 3:51 pm, pavan savoy wrote: > > > hi, > > > non-existance of DRIVER START/STOP RSSI

[android-porting] Re: Unable to open connection to wpa_supplicant error

2009-02-10 Thread >;> Jith911
cation git.omapzoom.org. > > Have a look @ the wifi.c and the relevant init.rc file. Particularly in the > zoom2 project. > don't have the source code anymore with me > > regards, > Pavan > > > > On Tue, Feb 10, 2009 at 12:05 PM, >> Jith911 wrote: > &g

[android-porting] Re: Unable to open connection to wpa_supplicant error

2009-02-09 Thread >;> Jith911
.." I also use wext driver. So do we need to implement these?? like the way ti does??? Also dhcp doesn't work for me.. did you do something for that as well?? Kindly help me.. Its quite urgent.. Thanks, Jithu. On Feb 9, 9:14 pm, ">> Jith911" wrote: > Its okay Pava

[android-porting] Re: Unable to open connection to wpa_supplicant error

2009-02-09 Thread >;> Jith911
7;s too did have a problem, as far as I remember > un-fortunately not keeping track of wlan any more > back to bluetooth so, sorry can't help > > regards, > Pavan > > On Sat, Feb 7, 2009 at 4:47 PM, >> Jith911 wrote: > > > Hi Pavan Savoy, >

[android-porting] Re: Unable to open connection to wpa_supplicant error

2009-02-07 Thread >;> Jith911
, ">> Jith911" wrote: > Thanks.. on msm platform now..:) was on pxa, previous time.. > > On Feb 5, 10:06 pm, pavan savoy wrote: > > > Not a problem, happy to help. > > Are you on OMAP platform ? Just curious > > > On Thu, Feb 5, 2009 at 6:28 PM, >&g

[android-porting] Re: Unable to open connection to wpa_supplicant error

2009-02-05 Thread >;> Jith911
Thanks.. on msm platform now..:) was on pxa, previous time.. On Feb 5, 10:06 pm, pavan savoy wrote: > Not a problem, happy to help. > Are you on OMAP platform ? Just curious > > On Thu, Feb 5, 2009 at 6:28 PM, >> Jith911 wrote: > > > Hi Savoy, > > > So

[android-porting] Re: Unable to open connection to wpa_supplicant error

2009-02-05 Thread >;> Jith911
u have any one of these directories or sockets missing, the error is > the same. > > And if you still get an error, then we would have a 3rd problem, with > basically the same error description. > > regards, > Pavan > > On Thu, Feb 5, 2009 at 5:49 PM, >> Jith911 wr

[android-porting] Re: Unable to open connection to wpa_supplicant error

2009-02-05 Thread >;> Jith911
called /data/misc/wifi/sockets directory to create > local sockets & the below mentioned path to the remote socket. > > look in wpa_ctrl_open function, or _unix.c inside wpa_supplicant library. > > regards, > Pavan > > On Thu, Feb 5, 2009 at 4:05 PM, >> Jith911 wrot

[android-porting] Re: Unable to open connection to wpa_supplicant error

2009-02-05 Thread >;> Jith911
for a path called /data/misc/wifi/sockets directory to create > local sockets & the below mentioned path to the remote socket. > > look in wpa_ctrl_open function, or _unix.c inside wpa_supplicant library. > > regards, > Pavan > > On Thu, Feb 5, 2009 at 4:05 PM, >&g

[android-porting] Unable to open connection to wpa_supplicant error

2009-02-05 Thread >;> Jith911
I am getting the following error D/WifiHW ( 63): Unable to open connection to supplicant on "/data/ misc/wifi/e th0": No such file or directory : 2 " But the socket exists at the above said location. And i have given all permissions for that. Also i checked the path in /hardware/libhardware/

[android-porting] Kernel thread priority.

2009-01-11 Thread >;> Jith911
driver. There is nothing much different in the two scenarios. Only difference is the loading of driver before and after Android init. So i am wondering whether it has to do something with process context from which the insmod is instantiated. THanks, Jith911

[android-porting] Re: access to wpa_supplicant

2008-12-31 Thread >;> Jith911
I also faced this problem.. 1. Check the path that you gave in supplicant.conf and the one that is there in hardware/libhardware/wifi/wifi.c. Both should match.. 2. eth1 should have appropriate persmissions. so in the supplicant.conf ctrl_interface_group should be system. On Dec 8, 1:05 pm, "Mik