<div dir="ltr">Hello Werner/Openmoko Team,<br><br>I have good experience of WAP/SMS/MMS for (LG, Samsung) handsets.<br>I have worked with both LG and Samsung for around 3 years in above technologies for mobiles.<br><br>Openmoko being an opensource, i am keen to contribute into applications like WAP/SMS, WAP browser, WAP protocol stack (1.X,2.X) and more into mobile software platform development and mobile applications.<br>
<br>I can also contribute into Layer1, device drivers etc.<br><br>I have special interest into openmoko because currently I am Lead Developer in design of an serverless instant messenger retromessenger (<a href="http://retromessenger.sourceforge.net/">http://retromessenger.sourceforge.net/</a>) and i am planning to make a Mobile port for this and then retromessenger application can be run on openmoko as well.<br>
<br>But here i Need a starting point to Set up openmoko-development environment.<br>and to understand the openmoko platform.<br><br>Can some one guide me for setting up openmoko environment on my system.<br><br>Thanks & Regards,<br>
Mahendra<br><br><br><div class="gmail_quote">On Tue, Oct 7, 2008 at 12:02 PM, Werner Almesberger <span dir="ltr"><<a href="mailto:werner@openmoko.org">werner@openmoko.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">mahendra panpalia wrote:<br>
> >> Using FDOM, ASU 2008.8 and ASU 2008.9, it is impossible to join my home<br>
> >> and work WEP enabled network using the "Settings" application.<br>
<br>
</div>Does it work if running iwconfig from a shell ? We know that there<br>
are a number of issues with the GUI way of doing things, and it seems<br>
they're hard to solve.<br>
<br>
While our GUI people are working on that problem, I'm interested in<br>
any showstoppers we may have at the layers below, i.e., in the<br>
various wireless tools, kernel, or (let's hope not) firmware.<br>
<br>
The canonical way of running iwconfig for WEP would be something like<br>
this:<br>
<br>
# iwconfig eth0 key A4BEB3B8EC essid xyz<br>
<br>
Two things are important here:<br>
<br>
- the key must be in hex. iwconfig will not do anything useful if<br>
the key is given as a string.<br>
<br>
- the ESSID must follow the key.<br>
<br>
If an incorrect key was set, please stop all activity on the interface<br>
for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down),<br>
then issue the correct iwconfig command and retry.<br>
<br>
Thanks,<br>
<font color="#888888">- Werner<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Thanks & kind regards,<br>Mahendra P.<br>Mob: +44 78260 46167<br>
</div>