Re: [ANNOUNCE] eStarDict

2010-03-11 Thread Xiangfu Liu
Vaudano Luca wrote:
 Hi!
 You got an error because this is a bazaar, not a svn repository, repository.
 By the way, all the instructions are here:
 http://www.vaudano.eu/wiki/en/estardictInstallation#Development_in_Ubuntu_Karmic
 I tried eStarDict with chinese charset and it works fine.
 If you need help for making it works on the Ben NanoNote, please ask me.
 If you success please post some screenshots :)
Thanks Vaudano
I am work on port StarDict to NanoNote. the StarDict work fine in NanoNote.
if I have time maybe try to port the eStarDict to NanoNote. will let you know 
then.
:-)


 
 Regards
 Luca
 
 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Applying for GSoC 2010

2010-03-11 Thread Dr. Michael Lauer
Hi folks,

After our successful GSoC in 2007 and 2008 as Openmoko -- and us not being on 
board in 2009,
I decided to try apply again as a mentoring organization this year.
Please toss some ideas to http://wiki.freesmartphone.org/index.php/GSoC_Ideas

I'll keep you posted on the results.

Cheers,

:M:


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Applying for GSoC 2010

2010-03-11 Thread Jeffrey Ratcliffe
On Thu, Mar 11, 2010 at 05:23:15PM +0100, Dr. Michael Lauer wrote:
 After our successful GSoC in 2007 and 2008 as Openmoko -- and us not being on 
 board in 2009,
 I decided to try apply again as a mentoring organization this year.

Isn't tomorrow the closing date for submissions?

Jeff


signature.asc
Description: Digital signature
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Applying for GSoC 2010

2010-03-11 Thread Dr. Michael Lauer

Am 11.03.2010 um 17:28 schrieb Jeffrey Ratcliffe:
 On Thu, Mar 11, 2010 at 05:23:15PM +0100, Dr. Michael Lauer wrote:
 After our successful GSoC in 2007 and 2008 as Openmoko -- and us not being 
 on board in 2009,
 I decided to try apply again as a mentoring organization this year.
 
 Isn't tomorrow the closing date for submissions?

Correct -- for mentoring organizations.

Full timeline is @ 
http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline

:M:


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


NWA Development and Sources?

2010-03-11 Thread D. Gassen
Hi all,

Does anybody know if NWA is still being developed? According to the page on the 
OpenMoko Wiki (http://wiki.openmoko.org/wiki/NWA) it seems that it was more 
like a proof of concept.

Was it replaced by something else?

I really like the concept of it (love it, actually) but not being able to 
connect to WEP secured networks is not that great. I cannot find any sources 
for it. The Subversion host mentioned in the binary package 
(svn://svn.noko.dnsalias.org/;module=nwa;proto=https) seems to be non-existant 
(I don't get a reply from svn.noko.dnsalias.org) and the homepage

 http://sourceforge.net/apps/mediawiki/noko/index.php?title=Main_Page

(if that's the one) doesn't mention nwa at all.

Thanks for any pointers,
Dirk
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: NWA Development and Sources?

2010-03-11 Thread Nicola Mfb
On Thu, Mar 11, 2010 at 10:14 PM, D. Gassen dirk.gas...@web.de wrote:
 Hi all,

 Does anybody know if NWA is still being developed? According to the page on 
 the OpenMoko Wiki (http://wiki.openmoko.org/wiki/NWA) it seems that it was 
 more like a proof of concept.

Yes, it was born to make brainstorming, that's the reason sources were
not released. Anyway I got no partecipation in that nor in wiki
Discussion Board in several months, I guess becouse it's QT based.
Developing was stopped due to lack of interest and kernel problems,
but now Paul Ferster patched ar6000 module, and Ben reported that NWA
now seems to be rock solid.
Please try the patch and report on trac any issues, this should
accelerate the upstream landing.
NWA is now one of the neophysis wifi manager candidate, so I'm going
in the next weeks to improve and clean it and finally release sources,
so please be patient.

 Was it replaced by something else?

 I really like the concept of it (love it, actually) but not being able to 
 connect to WEP secured networks is not that great. I cannot find any 
 sources for it.

Are you able to connect to your WEP network using wpa_supplicant
manually? in that case NWA should work or it needs a trivial fix.

 Niko

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: NWA Development and Sources?

2010-03-11 Thread D. Gassen

On Mar 11, 2010, at 17:11 , Nicola Mfb wrote:

 On Thu, Mar 11, 2010 at 10:14 PM, D. Gassen dirk.gas...@web.de wrote:
 Hi all,
 
 Does anybody know if NWA is still being developed? According to the page on 
 the OpenMoko Wiki (http://wiki.openmoko.org/wiki/NWA) it seems that it was 
 more like a proof of concept.
 
 Yes, it was born to make brainstorming, that's the reason sources were
 not released. Anyway I got no partecipation in that nor in wiki
 Discussion Board in several months, I guess becouse it's QT based.
 Developing was stopped due to lack of interest and kernel problems,
 but now Paul Ferster patched ar6000 module, and Ben reported that NWA
 now seems to be rock solid. Please try the patch and report on trac any 
 issues, this should
 accelerate the upstream landing.

Do you have a URL handy by any chance?

 NWA is now one of the neophysis wifi manager candidate, so I'm going
 in the next weeks to improve and clean it and finally release sources,
 so please be patient.
 
 Was it replaced by something else?
 
 I really like the concept of it (love it, actually) but not being able to 
 connect to WEP secured networks is not that great. I cannot find any 
 sources for it.
 
 Are you able to connect to your WEP network using wpa_supplicant
 manually? in that case NWA should work or it needs a trivial fix.

I do get

 AppletController Cannot set network options
 Did not receive correct message arguments. 
 Unaccepted options: QMap((key_mgmt, QVariant(QString, WEP) ) ( priority 
 ,  QVariant(QString, 0) ) ( ssid ,  QVariant(QString, bishop) ) ( 
 wep_key0 ,  QVariant(QString, **) ) ( wep_key1 
 ,  QVariant(QString, ) ) ( wep_key2 ,  QVariant(QString, ) ) ( 
 wep_key3 ,  QVariant(QString, ) ) ( wep_tx_keyidx ,  QVariant(QString, 
 0) ) )  
 AppletController cannot add network QVariant(QString, GWN) QVariant(, )


for both WEP networks that I have defined in .nwa.conf. However, this might be 
caused by the middleware since today for one time only nwa *was* able to 
associated with bishop.

The WPA-PSK network at home works flawlessly. I have the same networks 
configured in /etc/wpa_supplicant/wpa_supplicant.conf and I can associate with 
the WEP networks without problems:

 r...@freerunner:~# fsoraw -r WiFi -- /usr/sbin/wpa_supplicant  
 -c/etc/wpa_supplicant/wpa_supplicant.conf -ieth0
 ioctl[SIOCSIWENCODEEXT]: Operation not supported
 ioctl[SIOCSIWENCODEEXT]: Operation not supported
 ioctl[SIOCSIWENCODEEXT]: Operation not supported
 ioctl[SIOCSIWENCODEEXT]: Operation not supported
 CTRL-EVENT-SCAN-RESULTS 
 Trying to associate with 00:19:aa:14:d9:60 (SSID='bishop' freq=2452 MHz)
 ioctl[SIOCSIWENCODEEXT]: Operation not supported
 Associated with 00:19:aa:14:d9:60
 CTRL-EVENT-CONNECTED - Connection to 00:19:aa:14:d9:60 completed (auth) [id=3 
 id_str=]



I do actually have problems with the ar6000 driver if I do *not* blacklist it 
(in /etc/modprobe.d/blacklist). I do see kernel panics in the syslog and Wifi 
usually does not work (fsoraw fails to aquire the WiFi resource and I don't get 
the eth0 interface). I *seem* to have less problems if I load the driver later 
manually.

I am running andy-tracking 3db70757d6fabb17 with my own config (DEBUG options 
disabled) but I have the same results with the current kernel from SHR-U. Is 
that aforementioned patch included?

Dirk


 
 Niko
 
 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: NWA Development and Sources?

2010-03-11 Thread Nicola Mfb
On Fri, Mar 12, 2010 at 12:56 AM, D. Gassen dirk.gas...@web.de wrote:
[...]
 now seems to be rock solid. Please try the patch and report on trac any 
 issues, this should
 accelerate the upstream landing.

 Do you have a URL handy by any chance?

It's on openmoko trac:

https://docs.openmoko.org/trac/attachment/ticket/2333/0001-ar6000-minimise-possibility-of-race-in-ar6000_ioctl_.patch

[...]
 I really like the concept of it (love it, actually) but not being able to 
 connect to WEP secured networks is not that great. I cannot find any 
 sources for it.

 Are you able to connect to your WEP network using wpa_supplicant
 manually? in that case NWA should work or it needs a trivial fix.

 I do get

 AppletController Cannot set network options
 Did not receive correct message arguments.
 Unaccepted options: QMap((key_mgmt, QVariant(QString, WEP) ) ( 
 priority ,  QVariant(QString, 0) ) ( ssid ,  QVariant(QString, 
 bishop) ) ( wep_key0 ,  QVariant(QString, **) 
 ) ( wep_key1 ,  QVariant(QString, ) ) ( wep_key2 ,  QVariant(QString, 
 ) ) ( wep_key3 ,  QVariant(QString, ) ) ( wep_tx_keyidx ,  
 QVariant(QString, 0) ) )
 AppletController cannot add network QVariant(QString, GWN) QVariant(, )

Thats a dbus error reply from wpa_supplicant.
Just guessing (I cannot check now) try to remove empty wep keys from
.nwa.conf, or in general remove from it pair values in Unaccepted
options that are not present in your wpa_supplicant.conf.

[...]

 I do actually have problems with the ar6000 driver if I do *not* blacklist it 
 (in /etc/modprobe.d/blacklist). I do see kernel panics in the syslog and Wifi 
 usually does not work (fsoraw fails to aquire the WiFi resource and I don't 
 get the eth0 interface). I *seem* to have less problems if I load the driver 
 later manually.

 I am running andy-tracking 3db70757d6fabb17 with my own config (DEBUG options 
 disabled) but I have the same results with the current kernel from SHR-U. Is 
 that aforementioned patch included?

Not yet.

Niko

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community