Thanks Pavan, I will check it.
On Feb 10, 3:51 pm, pavan savoy <[email protected]> wrote:
> hi,
>
> non-existance of DRIVER START/STOP RSSI, LINKSPEED, doesn't really stop
> anyone from using the WLAN chip.
> Our chip required a ifconfig up on the interface, before starting off the
> dhcpcd.
>
> basically add a service
> service ifcfg_mychip ifconfig wlan0 up
> &
> service dhcpcd dhcpcd -d wlan0
>
> & start these from the wifi.c file.....
>
> I suppose most of my changes have made it to the [local]Android tree in
> omapzoom.org, and git location 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 <[email protected]> wrote:
>
> > hello Pavan,
>
> > I am able to browse using UI, but getting message "unable to scan
> > networks". When i googled, i found ur post asking the same. Could you
> > share how you managed to proceed ahead.
>
> > "Since driver uses WEXT it does not have
> > DRIVER START, STOP, RSSi, LINKSPEED, MACADDR etc..."
>
> > 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" <[email protected]> wrote:
> > > Its okay Pavan.. The problem was with unclean termination of sockets..
> > > On supplicant stop, i added lines in init.rc to remove sockets and
> > > there after the problem is not seen.
>
> > > Thanks.
>
> > > Jithu.
>
> > > On Feb 9, 4:16 pm, pavan savoy <[email protected]> wrote:
>
> > > > Secure SSID are never shown.
> > > > I think the open SSID'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 <[email protected]>
> > wrote:
>
> > > > > 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" <[email protected]> wrote:
> > > > > > Thanks.. on msm platform now..:) was on pxa, previous time..
>
> > > > > > On Feb 5, 10:06 pm, pavan savoy <[email protected]> wrote:
>
> > > > > > > Not a problem, happy to help.
> > > > > > > Are you on OMAP platform ? Just curious ....
>
> > > > > > > On Thu, Feb 5, 2009 at 6:28 PM, >> Jith911 <[email protected]
>
> > > > > 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 <[email protected]> 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 <
> > [email protected]>
> > > > > 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 <[email protected]>
> > 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 <
> > > > > [email protected]>
> > > > > > > > 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.- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
