Hi Pavan Savoy,

Got another problem.. Supplicant is returning Null ssid at times.. all
the scan results are shown as null ssids.. and its also showing
IWGENIE overflow error!!.. Have you come across this error before??
Looks like its a parsing error by driver_wext.c..

On Feb 6, 9:31 am, ">> Jith911" <jithuja...@gmail.com> wrote:
> Thanks.. on msm platform now..:) was on pxa, previous time..
>
> On Feb 5, 10:06 pm, pavan savoy <pavan.sa...@gmail.com> wrote:
>
> > Not a problem, happy to help.
> > Are you on OMAP platform ? Just curious ....
>
> > On Thu, Feb 5, 2009 at 6:28 PM, >> Jith911 <jithuja...@gmail.com> wrote:
>
> > > Hi Savoy,
>
> > > Sorry.. as you said, i browsed through the code.. I understood..
> > > Thanks a lot Savoy.. I am so sorry..
>
> > > Thanks,
>
> > > JJ.
>
> > > On Feb 5, 9:25 pm, pavan savoy <pavan.sa...@gmail.com> wrote:
> > > > See, 2 interfaces right,
> > > > the wpa_supplicant daemon has to communicate with the GUI, this happens
> > > over
> > > > the remote socket [it is just what I call, there could be a better name 
> > > > I
> > > > agree..]
> > > > This has to be mentioned in 2 places, wpa_supp...conf & the wifi.c file
> > > in
> > > > hardware/libhardware...
>
> > > > However if you go through the source code of wpa_supplicant you'ld
> > > realise
> > > > that, before doing a connect on that socket on "data/misc/wifi",
> > > supplicant
> > > > creates a local unix domain socket on
> > > > data/misc/wifi/socket & binds to it.
>
> > > > This is what I feel the problem is.. [so create a directory
> > > > /data/misc/wifi/sockets, please..]
>
> > > > Finally,
> > > > If you 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 <jithuja...@gmail.com> wrote:
>
> > > > > Hi Savoy,
>
> > > > > I got a similar error before. but that has to do with file
> > > > > permissions. This time its different. File has all the required
> > > > > permissions.
>
> > > > > In supplicant i have mentioned the control interface as /data/misc/
> > > > > wifi/. And wpa_supplicant creates a socket file eth0 there which has
> > > > > all the required permissions. This i guess is the local socket. Sorry,
> > > > > I didn't get what you meant by remote socket.. In 
> > > > > hardware/libhardware/
> > > > > wifi.c i have mentioned the interface dir as /data/misc/wifi/ so that
> > > > > the app should communicate with supplicant. I have done this few
> > > > > months ago and i had GUI working with this. But now when i do the same
> > > > > thing, i get this error.
>
> > > > > Thanks,
>
> > > > > JJ.
>
> > > > > On Feb 5, 7:46 pm, pavan savoy <pavan.sa...@gmail.com> wrote:
> > > > > > Humn, Didn't you get the same error earlier ....
>
> > > > > > Is the local unix domain sockets being created. Last time I checked
> > > on
> > > > > Wifi,
> > > > > > it checks 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, >> Jith911 <jithuja...@gmail.com>
> > > wrote:
>
> > > > > > > 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/
> > > > > > > wifi/wifi.c . Both are matching. Still I am getting the error. 
> > > > > > > Also
> > > > > > > the interface name is also correct.
>
> > > > > > > Any idea??
>
> > > > > > > Thanks,
>
> > > > > > > JJ.
>
>
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to