Re: QtGps for Trolltechs Qtopia

2008-09-14 Thread Abdelrazak Younes
Radek Bartoň wrote:
 Dne Saturday 13 of September 2008 22:47:38 Abdelrazak Younes napsal(a):

 I was thinking of kml support too so that your track and way points can
 be loaded in Google Earth. KML files are pretty easy to generate. But I
 don't think this kind of format conversion have a place in a GUI app.
 The GUI app could OTOH call some external process to do the conversion.

 There are plans to add more features to this app, either by me or another
 person who has cloned the tree, he will be working on it in a few weeks I
 think.

 Concerning tracking format I thought that basic file format shoud be storage
 effective binary format. I would prefer standardized one but I don't know
 which one yet.

I'd propose to keep ublox binary format. This format is quite clear and 
already documented. Ideally I'd like a simple daemon (that could be an 
extension of gypsy) that will write hourly logs of the gps chip in an 
organized directory structure. The types of ublox messages logged as 
well as the accumulated size on disk would be configurable. This logger 
would be started as soon as the GPS is turned on. We could potentially 
dissociate the AID messages (ephemerises, almanacs, SBAS masks) from the 
raw and navigation data.
Then for example, when started, QtopiaGps would be able to read the 
track and display the GPS track since the ublox was started. Another 
program could do something else with the raw data (statistics, 
conversion to another format, tomography, experimental navigation 
algorithm, etc).

 Then conversion scripts to any other format can be easily
 written or gpsbable can be utilized. There could be designed even abstact
 inteface for loggers/output devices now but it can be implemented by
 different file format handlers lately.

Agreed.


 If you talk about me I will certainly do but I don't have the time right
 now...

 I'm quite sure that that person is me because I post Moris my proposals
 recently.

Good, that makes the three of us then :-)

 Adding tracks is definitely something he is planning to do.

 That's true. I've been on a trip with my Neo recently and I reveal many
 usefull features which can be implemented and which no available GPS
 application for Neo has for now. I'll sumarize them somewhere soon and then
 I'll start to implement them sequentially.

 I stumbled across this:
 http://www.medieninf.de/qmapcontrol/

 It could be a good idea to just use that instead of borowing TangoGPS
 code for openstreetmap support.


 I'll investigate that possibility closely too but I'm quite sceptic about this
 project clearness and design effectivness.

I didn't look at the source code yet.

 SlippyMap tile download and
 display is quite easy to implement so I think it can be done from scratch (or
 extracted from TangoGPS). Only difficulties would be dealing with multiple
 threads. I've already written Python script for maps pre-download for
 TangoGPS similar to gpsfetchmap.pl (it is not publicly available yet) and
 there is nothing complicated about that.

Very good.

Abdel.



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


Re: update-alternatives question

2008-09-14 Thread Rod Whitby
Charles-Henri Gros wrote:
 Joel Newkirk wrote:
 Quick question, hopefully someone can instantly see my error:

 I've built the full iproute2 toolset, and am working on an ipk/opk for ip
 and tc.  

 The default om2008 at least, has /bin/ip linked to /bin/busybox.  So that
 should be changed.  For inspiration, I looked at the postinst script for
 grep, since it must perform the same changes.  (point at full bin instead
 of busybox in postinst, restore in prerm)  So I took the
 update-alternatives line from grep's postinst and simply replaced 'grep'
 with 'ip' everywhere.

 [EMAIL PROTECTED]:~# update-alternatives --install /usr/bin/ip ip ip.ip 100
 update-alternatives: Error: cannot register alternative ip to /usr/bin/ip
 since it is already registered to /bin/ip

 Isn't this the point of update-alternatives - to allow multiple possible
 binaries, and 'register' the one with highest priority?  What have I done
 wrong?  And why is the path component grep.grep (or in my case ip.ip)??
 
 grep.grep is the binary that contains what the grep package installs.
 You should probably install your ip as ip.ip, or use /usr/bin/ip (if
 that's where you install it)
 
 So the command would look like (I think):
 update-alternatives --install /bin/ip ip /usr/bin/ip 100

I would not recommend that command.

For update-alternatives to work, all the packages which install that binary
have to agree on the final path of the binary.  You can't have one package
wanting to install it in /bin and the other wanting to install it in /usr/bin.

So first you need to modify all the packages so they install into the same
directory.

Then you go and put the update-alternatives stuff in, and you make each
package install the binary in /path/binary-name.package-name (e.g.
/bin/ip.ip and /bin/ip.busybox).  Then you get update-alternatives to
symlink one of those to the final binary filename in the postinst.

-- Rod


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


Re: happy with debian

2008-09-14 Thread arne anka
 device to /dev/ttySAC1 and it works. I don't know for what reason i
 should install fso-gpsd.

so that you don't need gpsd.
fso handles gps by itself -- thus having gpsd trying to handle gps too,  
might end up in confusion.
fso-gpsd is a compatibility layer between fso and applications requiring  
gpsd.


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


Predictive keyboard not actually predictive?

2008-09-14 Thread Neil Jerram
Hello everyone, this is my first openmoko email, so please be gentle!

It seems clear to me that the so-called predictive keyboard is not
actually predictive at all; it is actually fuzzy, in terms of how it
maps your stylus or finger position to a set of possible intended
letters.

In particular, surely this text in the wiki -

The word recognition will try to guess the next inputs and displays
the word it thinks you want to write.

- is just nonsense, isn't it?  I've never seen it guess at any letters
beyond those that I've already pressed.

I'm ready to register and update the wiki to say something closer to
reality - but I just want to check first that I'm not missing or
misunderstanding something.

Thanks!
  Neil

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


Re: Predictive keyboard not actually predictive?

2008-09-14 Thread Rui Miguel Silva Seabra
On Sun, Sep 14, 2008 at 12:07:52PM +0200, Neil Jerram wrote:
 Hello everyone, this is my first openmoko email, so please be gentle!
 
 It seems clear to me that the so-called predictive keyboard is not
 actually predictive at all; it is actually fuzzy, in terms of how it
 maps your stylus or finger position to a set of possible intended
 letters.
 
 In particular, surely this text in the wiki -
 
 The word recognition will try to guess the next inputs and displays
 the word it thinks you want to write.
 
 - is just nonsense, isn't it?  I've never seen it guess at any letters
 beyond those that I've already pressed.
 
 I'm ready to register and update the wiki to say something closer to
 reality - but I just want to check first that I'm not missing or
 misunderstanding something.

I actually think of it as restrictive instead of predictive because
it only allows me to write what it thinks I want, and should give up as
soon as it couldn't match a word.

Having to wait 2s per letter for it to write what I want instead of what
it thinks I want sucks :)

Rui

-- 
Pzat!
Today is Boomtime, the 38th day of Bureaucracy in the YOLD 3174
+ No matter how much you do, you never do enough -- unknown
+ Whatever you do will be insignificant,
| but it is very important that you do it -- Gandhi
+ So let's do it...?

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


Re: Predictive keyboard not actually predictive?

2008-09-14 Thread Shawn prjktdtnt Thompson
Rui Miguel Silva Seabra wrote:
 On Sun, Sep 14, 2008 at 12:07:52PM +0200, Neil Jerram wrote:
   
 Hello everyone, this is my first openmoko email, so please be gentle!

 It seems clear to me that the so-called predictive keyboard is not
 actually predictive at all; it is actually fuzzy, in terms of how it
 maps your stylus or finger position to a set of possible intended
 letters.

 In particular, surely this text in the wiki -

 The word recognition will try to guess the next inputs and displays
 the word it thinks you want to write.

 - is just nonsense, isn't it?  I've never seen it guess at any letters
 beyond those that I've already pressed.

 I'm ready to register and update the wiki to say something closer to
 reality - but I just want to check first that I'm not missing or
 misunderstanding something.
 

 I actually think of it as restrictive instead of predictive because
 it only allows me to write what it thinks I want, and should give up as
 soon as it couldn't match a word.

 Having to wait 2s per letter for it to write what I want instead of what
 it thinks I want sucks :)

 Rui

   
I'd have to agree with Rui, I've installed FDOM which has raster's 
terminal keyboard so I just don't worry about it anymore

-Shawn

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


Re: Predictive keyboard not actually predictive?

2008-09-14 Thread Neil Jerram
2008/9/14 Shawn prjktdtnt Thompson [EMAIL PROTECTED]:
 Rui Miguel Silva Seabra wrote:

 I actually think of it as restrictive instead of predictive because
 it only allows me to write what it thinks I want, and should give up as
 soon as it couldn't match a word.

 Having to wait 2s per letter for it to write what I want instead of what
 it thinks I want sucks :)

 I'd have to agree with Rui, I've installed FDOM which has raster's
 terminal keyboard so I just don't worry about it anymore

I agree with that too - but that's not what my post was about!  Please
don't hijack my thread with other random keyboard gripes!

Can I take it that you both agree with what I was writing about?

Thanks,
 Neil

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


Qtopia opkg sources

2008-09-14 Thread Alexander Frøyseth
Hello
I use Qtopia 4.3.3 snapshot (it is stable and fast), but for about a 
week ago the sources to opkg was removed, or buildhost.openmoko.org 
was removed.
Does anyone know where the Qtopia sources are?

Alexander Frøyseth

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


FDOM tar.gz wrong root path

2008-09-14 Thread David Samblas
Beware, the last tar.gz has a wrong path , and whas under /var/tmp/root
instead of / 
you boot on any distro you can access to the sd card partition and fix
it manually  

mv /media/mmcblk0p2/var/tmp/root/* /media/mmcblk0p2/

New fixed tar version uploading now

Sorry
David


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


qtopia, earphone and mediaplayer

2008-09-14 Thread Oscar Casamitjana
ëžv~Ë­­ªvóß7ïnuß^5÷O4ÓHola a todos,probando el qtopia, me he dado cuenta de que si conecto
los auriculares mientras est sonando una cancin se activa
el altavoz del freerunner a la vez que se oye por los auriculares, pero si
los desconecto, se desactiva el altavoz.He echado un vistazo
al driver /etc/input/events0 y obtengo lo siguiente:**
Conectando los auriculares ***[EMAIL PROTECTED]:~# hexdump -C
/dev/input/event0 99 67 cc 48 62 69 0a
00 05 00 02 00 01 00 00 00 |.g.Hbi..|0010 99 67 cc 48 b2 69 0a 00 00 00 00 00 00 00 00
00 |.g.H.i..|*** Desconectando los auriculares
***[EMAIL PROTECTED]:~# hexdump -C /dev/input/event0  da 67 cc 48 3b 64 05 00 05 00 02 00 00 00 00
00 |.g.H;d..|0010 da 67 cc 48 84 64 05
00 00 00 00 00 00 00 00 00 |.g.H.d..|Como
podeis observar, en la posicion 0x0c cambia el valor, si est
conectado es 1 si est desconectado es 0, por lo que parece
est bien.Por lo visto debe ser algo de la apliacin
mediaplayer.Sabeis algo de esto?Gracias.Oscar.Hola a todos,probando el qtopia, me he dado cuenta de que si conecto
los auriculares mientras est sonando una cancin se activa
el altavoz del freerunner a la vez que se oye por los auriculares, pero si
los desconecto, se desactiva el altavoz.He echado un vistazo
al driver /etc/input/events0 y obtengo lo siguiente:**
Conectando los auriculares ***[EMAIL PROTECTED]:~# hexdump -C
/dev/input/event0 99 67 cc 48 62 69 0a
00 05 00 02 00 01 00 00 00 |.g.Hbi..|0010 99 67 cc 48 b2 69 0a 00 00 00 00 00 00 00 00
00 |.g.H.i..|*** Desconectando los auriculares
***[EMAIL PROTECTED]:~# hexdump -C /dev/input/event0  da 67 cc 48 3b 64 05 00 05 00 02 00 00 00 00
00 |.g.H;d..|0010 da 67 cc 48 84 64 05
00 00 00 00 00 00 00 00 00 |.g.H.d..|Como
podeis observar, en la posicion 0x0c cambia el valor, si est
conectado es 1 si est desconectado es 0, por lo que parece
est bien.Por lo visto debe ser algo de la apliacin
mediaplayer.Sabeis algo de esto?Gracias.Oscar.___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: qtopia, earphone and mediaplayer

2008-09-14 Thread Neil Jerram
English translation added...

2008/9/14 Oscar Casamitjana [EMAIL PROTECTED]:
 Hola a todos,

Hello everyone.

 probando el qtopia 4.3.3, me he dado cuenta de que si conecto los
 auriculares mientras está sonando una canción se activa el altavoz del
 freerunner a la vez que se oye por los auriculares, pero si los desconecto,
 se desactiva el altavoz.

Trying qtopia 4.3.3, I noticed that if I plug in the headphones while
listening to a song, the sound is played through the FR's loudspeaker
at the same time as coming through the headphones.  If I disconnect
the headphones, the loudspeaker deactivates.

 Haciendo un hexdump a /etc/input/events0 obtengo lo siguiente:

Doing a hexdump of /etc/input/events0, I see the following:

 ** Conectando los auriculares ***

(Connecting the headphones)

 [EMAIL PROTECTED]:~# hexdump -C /dev/input/event0

   99 67 cc 48 62 69 0a 00  05 00 02 00 01 00 00 00
 |.g.Hbi..|
 0010  99 67 cc 48 b2 69 0a 00  00 00 00 00 00 00 00 00
 |.g.H.i..|

 *** Desconectando los auriculares ***

(Disconnecting the headphones)

 [EMAIL PROTECTED]:~# hexdump -C /dev/input/event0

   da 67 cc 48 3b 64 05 00  05 00 02 00 00 00 00 00
 |.g.H;d..|
 0010  da 67 cc 48 84 64 05 00  00 00 00 00 00 00 00 00
 |.g.H.d..|

 Como podeis observar, en la posicion 0x0c cambia el valor, si está conectado
 es 1 si está desconectado es 0, por lo que parece está bien.
 Por lo visto debe ser algo de la apliación mediaplayer.

As you can see, at position 0x0c the value changes from 1 (if
connected) to 0 (if disconnected) - so that seems good.  Therefore I
think this problem must be something in the media player application.

 ¿Sabeis algo de esto?

Any ideas about this?

 Gracias.
 Oscar.

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


Re: qtopia, earphone and mediaplayer

2008-09-14 Thread arne anka
would you please post in the commonly used language of this list?

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


Re: qtopia, earphone and mediaplayer

2008-09-14 Thread Alexander Frøyseth




Oscar Casamitjana skrev:
Hola a todos,
  
probando el qtopia
4.3.3, me he dado cuenta de que si conecto los auriculares mientras
está sonando una canción se activa el altavoz del freerunner
a la vez que se oye por los auriculares, pero si los desconecto, se
desactiva el altavoz.
  
Haciendo un hexdump a /etc/input/events0
obtengo lo siguiente:
  
** Conectando los auriculares ***
[EMAIL PROTECTED]:~# hexdump -C /dev/input/event0
 
  99 67 cc 48 62 69 0a 00  05 00 02 00 01 00 00
00  |.g.Hbi..|
0010  99 67 cc 48 b2 69 0a
00  00 00 00 00 00 00 00 00  |.g.H.i..|
  
***
Desconectando los auriculares ***
[EMAIL PROTECTED]:~# hexdump -C
/dev/input/event0 
  
  da 67 cc 48 3b 64 05 00 
05 00 02 00 00 00 00 00  |.g.H;d..|
0010  da 67
cc 48 84 64 05 00  00 00 00 00 00 00 00 00 
|.g.H.d..|
  
Como podeis observar, en la posicion 0x0c
cambia el valor, si está conectado es 1 si está desconectado
es 0, por lo que parece está bien.
Por lo visto debe ser algo
de la apliación mediaplayer.
  
¿Sabeis algo de
esto?
  
Gracias.
Oscar. 
  
Hola a todos,
probando el qtopia, me he dado cuenta de que si conecto
los auriculares mientras está sonando una canción se activa
el altavoz del freerunner a la vez que se oye por los auriculares, pero
si
los desconecto, se desactiva el altavoz.
  
He echado un vistazo
al driver /etc/input/events0 y obtengo lo siguiente:
  
**
Conectando los auriculares ***
[EMAIL PROTECTED]:~# hexdump -C
/dev/input/event0
 
  99 67 cc 48 62 69 0a
00  05 00 02 00 01 00 00 00  |.g.Hbi..|
0010  99 67 cc 48 b2 69 0a 00  00 00 00 00 00 00 00
00  |.g.H.i..|
  
*** Desconectando los auriculares
***
[EMAIL PROTECTED]:~# hexdump -C /dev/input/event0 
  
  da 67 cc 48 3b 64 05 00  05 00 02 00 00 00 00
00  |.g.H;d..|
0010  da 67 cc 48 84 64 05
00  00 00 00 00 00 00 00 00  |.g.H.d..|
  
Como
podeis observar, en la posicion 0x0c cambia el valor, si está
conectado es 1 si está desconectado es 0, por lo que parece
está bien.
Por lo visto debe ser algo de la apliación
mediaplayer.
  
¿Sabeis algo de esto?
  
Gracias.
Oscar.
  
Hola a todos,
probando el qtopia, me he dado cuenta de que si conecto
los auriculares mientras está sonando una canción se activa
el altavoz del freerunner a la vez que se oye por los auriculares, pero
si
los desconecto, se desactiva el altavoz.
  
He echado un vistazo
al driver /etc/input/events0 y obtengo lo siguiente:
  
**
Conectando los auriculares ***
[EMAIL PROTECTED]:~# hexdump -C
/dev/input/event0
 
  99 67 cc 48 62 69 0a
00  05 00 02 00 01 00 00 00  |.g.Hbi..|
0010  99 67 cc 48 b2 69 0a 00  00 00 00 00 00 00 00
00  |.g.H.i..|
  
*** Desconectando los auriculares
***
[EMAIL PROTECTED]:~# hexdump -C /dev/input/event0 
  
  da 67 cc 48 3b 64 05 00  05 00 02 00 00 00 00
00  |.g.H;d..|
0010  da 67 cc 48 84 64 05
00  00 00 00 00 00 00 00 00  |.g.H.d..|
  
Como
podeis observar, en la posicion 0x0c cambia el valor, si está
conectado es 1 si está desconectado es 0, por lo que parece
está bien.
Por lo visto debe ser algo de la apliación
mediaplayer.
  
¿Sabeis algo de esto?
  
Gracias.
Oscar.
  

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

English please?



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


Re: *new version* A little zenity-gui for flashing images to the neo

2008-09-14 Thread Dale Maggee
Ilja O. wrote:
 On Fri, Sep 12, 2008 at 5:13 AM, Charles Pax [EMAIL PROTECTED] wrote:

   
 So at some point here I'm guessing Zenity will have to be dropped in favor
 of maybe a Python + Glade combination. Is anyone out there capable and
 willing to do such a thing? It should probably happen sooner rather than
 later.

 

 I have been developing small python wx-based gui that currently can be used
 for flashing, log data obtaining and is able to do some backup (last two via
 ssh).

 I'd be glad to share if you want. (Just will need to do some docstrings).
   
yeah, I'd be really interested in seeing it! I don't really know any 
python yet, but I've looked into it a little bit lately, and I've 
decided I want to learn it, so if you share what you have it will 
probably help my learning and I can probably contribute to it.

Cheers,
-Dale

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


Re: qtopia, earphone and mediaplayer

2008-09-14 Thread Oscar Casamitjana



Uooppsss!!

Sorry about this, I thought I was sending the
message to the Spanish list!!
Too many subscriptions in my mailbox
:(

so thanks for the translation!!

Oscar.

 would you please post in the commonly used language of this
list?

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


Re: qtopia, earphone and mediaplayer

2008-09-14 Thread Oscar Casamitjana


Hello everyone.

Trying qtopia 4.3.3, I noticed that if I
plug in the headphones while
listening to a song, the sound is played
through the FR's loudspeaker
at the same time as coming through the
headphones.  If I disconnect
the headphones, the loudspeaker
deactivates.

Doing a hexdump of /etc/input/events0, I see the
following:

(Connecting the headphones)

[EMAIL PROTECTED]:~# hexdump -C /dev/input/event0

  99 67 cc 48 62 69 0a 00  05 00 02
00 01 00 00 00 |.g.Hbi..|
 0010  99 67 cc 48 b2 69 0a 00  00 00 00
00 00 00 00 00

|.g.H.i..|

 *** Desconectando los auriculares
***

(Disconnecting the headphones)

 [EMAIL PROTECTED]:~# hexdump -C
/dev/input/event0

   da 67 cc 48 3b 64 05 00  05 00 02 00 00 00
00 00
 |.g.H;d..|
 0010  da 67 cc 48 84 64 05 00  00 00 00
00 00 00 00 00

|.g.H.d..|

 Como podeis observar, en la posicion 0x0c
cambia el valor, si est� conectado
 es 1 si est� desconectado es 0, por lo que
parece est� bien.
 Por lo
visto debe ser algo de la apliaci�n mediaplayer.

As you can see, at position 0x0c the value changes from 1 (if
connected) to 0 (if disconnected) - so that seems good.  Therefore I
think this problem must be something in the media player application.

 �Sabeis algo de esto?

Any ideas about this?


Gracias.
 Oscar.

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


Re: Duke Nukem 3D on Openmoko Neo

2008-09-14 Thread Dale Maggee
Risto H. Kurppa wrote:
 try to run it in 2007.2.
 
 I tried killing pulseaudio with no luck, see my other message in this
 thread.

 I changed the config file to turn off audio as suggested, and got a bit
 further, but still no luck:

 output:
 ---
 Checking sound inits.
 Checking music inits.
 RTS Manager Started.
Adding DUKE.RTS.
 Using .RTS file:DUKE.RTS
 Loading palette/lookups.

 ---

 at which point the screen goes black and nothing happens for more than 5
 minutes. I have to open up a new terminal window and kill the duke3d
 process to get anything to happen.

 could this be related to my accelerometer problems mentioned elsewhere
 (hexdump /dev/input/event2 and event3 gives me nothing)?
 

 That's how far I get too, on 2007.2, sounds disabled (got exactly the
 same errors also after killing pulseaudio)

 It might have something to do with he accelerometers: sometimes they
 still seem to fail after waking up from suspend. I'll try at some
 point with a fresh-started phone and see if the accelerometers work
 (with accelgame) and then see if duke works better.

 Here's a .desktop -file for you to add to /usr/share/applications to
 create a menu icon:

 [Desktop Entry]
 Encoding=UTF-8
 Name=Duke Nukem 3D
 Exec=dukenukem3d
 Icon=applications-games
 Terminal=false
 Type=Application
 Categories=Game
 StartupNotify=true
 SingleInstance=true
 Comment=3D shooting

 and create an executable file dukenukem3d in /usr/bin:

 #
 xrandr -s 240x320
 xrandr -o 3
 /media/card/duke3d/duke3d #MODIFY THIS TO SUIT YOUR INSTALL DIR!
 #sorry, no idea if these will anymore fix the screen.. Any suggestions
 and fixes are welcome!
 xrandr -s 480x640
 xrandr -o 3

 


 r

   

Thanks

Yeah it won't start without the accelerometers. as mentioned above, 
hexdump /dev/input/event2 and event3 gives me nothing, even after 
rebooting. I tested it on 2008.8 and it works fine. can I ask what 
kernel are you running on 2007.2 or if you have any idea how I might fix 
my accelerometers in 2007.2?




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


Re: Duke Nukem 3D on Openmoko Neo

2008-09-14 Thread Risto H. Kurppa
On Sun, Sep 14, 2008 at 2:45 PM, Dale Maggee [EMAIL PROTECTED] wrote:
 Yeah it won't start without the accelerometers. as mentioned above,
 hexdump /dev/input/event2 and event3 gives me nothing, even after
 rebooting. I tested it on 2008.8 and it works fine. can I ask what
 kernel are you running on 2007.2 or if you have any idea how I might fix
 my accelerometers in 2007.2?

Using Linux om-gta02 2.6.24 #1 PREEMPT Thu Sep 11 13:25:16 CST 2008
armv4tl unknown

and I was now able to get hexdump from event3 but not event2.. I
suppose both accels are required for the game to run..
Will have to see if they both work later at the same time...

r

-- 
| risto h. kurppa
| risto at kurppa dot fi
| http://risto.kurppa.fi

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


Re: Duke Nukem 3D on Openmoko Neo

2008-09-14 Thread Risto H. Kurppa
On Fri, Sep 12, 2008 at 4:34 PM, Risto H. Kurppa [EMAIL PROTECTED] wrote:
 #
 xrandr -s 240x320
 xrandr -o 3
 /media/card/duke3d/duke3d #MODIFY THIS TO SUIT YOUR INSTALL DIR!
 #sorry, no idea if these will anymore fix the screen.. Any suggestions
 and fixes are welcome!
 xrandr -s 480x640
 xrandr -o 3

 

 oops, the last xrand has to be naturally
xrand -o 0


-- 
| risto h. kurppa
| risto at kurppa dot fi
| http://risto.kurppa.fi

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


Re: FDOM updated

2008-09-14 Thread William Kenworthy
The file was ok, but the qpe error is still generated.  I then tried
deleting and reinstalled FDOM and checked the 89Qtopia file (diffed it
with the bk~ and checked perms) with the same result.

I am running it from the SD card - shouldnt make a difference?  Just
untared it using tar -zxvpf fdom_file.tar.gz.  Turns out I can run it
qpe from a terminal and the qtopoia apps work, but no gsm registration.
Is there something Ive missed?

BillK


On Sat, 2008-09-13 at 18:46 +0200, David Samblas wrote:
 Seems you have been catched by the config issue, please do what
 indicated on the Warning part of the wiki
 
 cp /etc/X11/Xsession /etc/X11/Xsession.d/89qtopia.bk~ 
 /etc/X11/Xsession.d/89qtopia
 
 and reboot the neo
 
 Do that any time qtopia-x11 is updated (or when you have the simptoms
 you have described)
 
 Regards
 David 
 El sáb, 13-09-2008 a las 21:18 +0800, William Kenworthy escribió:
  Tried this for the first time and it looks good, but cant register the
  GSM (been trying for a few hours now) ...  Log extract below - any
  clues? - I normally use 2007.2 updated which works fine.
  
  Also many apps dont start (dialler, calendar, contacts, ...) - is that
  expected?
  
  BillK
  
  Sep 13 20:54:59 om-gta02 user.notice root: ficgta01hardware plugin 
  Sep 13 20:55:00 om-gta02 user.notice root: Modem :  opening serial
  device  /dev/pts/0  at  115200 
  Sep 13 20:55:00 om-gta02 user.notice root: Modem :  Device: /dev/pts/0
  is a tty device: True 
  Sep 13 20:55:00 om-gta02 user.notice root: Modem :  NONBLOCK
  successfully reset 
  Sep 13 20:55:00 om-gta02 user.notice root: Modem :  Opened
  /dev/pts/0 
  Sep 13 20:55:00 om-gta02 user.notice root: Modem :  querying multiplexer
  plugin ficgta01multiplex 
  Sep 13 20:55:01 om-gta02 user.notice root: AtChat :  T : ^Z 
  Sep 13 20:55:01 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1377]:
  gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't
  acked to be open.
  Sep 13 20:55:01 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1377]:
  gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't
  acked to be open.
  Sep 13 20:55:11 om-gta02 user.notice root: Mux :  *** mux setup timed
  out *** 
  Sep 13 20:55:11 om-gta02 user.notice root: AtChat :  T : ^Z 
  Sep 13 20:55:11 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1377]:
  gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't
  acked to be open.
  Sep 13 20:55:21 om-gta02 user.notice root: Mux :  *** mux setup timed
  out *** 
  Sep 13 20:55:21 om-gta02 user.notice root: AtChat :  T : ^Z 
  Sep 13 20:55:21 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1377]:
  gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't
  acked to be open.
  Sep 13 20:55:31 om-gta02 user.notice root: Mux :  *** mux setup timed
  out *** 
  Sep 13 20:55:31 om-gta02 user.notice root: AtChat :  T : ^Z 
  Sep 13 20:55:31 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1377]:
  gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't
  acked to be open.
  Sep 13 20:55:41 om-gta02 user.notice root: Mux :  *** mux setup timed
  out *** 
  Sep 13 20:55:41 om-gta02 user.notice root: AtChat :  T : ^Z 
  Sep 13 20:55:41 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1377]:
  gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't
  acked to be open.
  Sep 13 20:55:51 om-gta02 user.notice root: Mux :  *** mux setup timed
  out *** 
  Sep 13 20:55:51 om-gta02 user.notice root: AtChat :  T : ^Z 
  Sep 13 20:55:51 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1377]:
  gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't
  acked to be open.
  Sep 13 20:56:01 om-gta02 user.notice root: Mux :  *** mux setup timed
  out *** 
  Sep 13 20:56:01 om-gta02 user.notice root: AtChat :  T : ^Z 
  Sep 13 20:56:01 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1377]:
  gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't
  acked to be open.
  Sep 13 20:56:11 om-gta02 user.notice root: Mux :  *** mux setup timed
  out *** 
  Sep 13 20:56:11 om-gta02 user.notice root: AtChat :  T : ^Z 
  Sep 13 20:56:11 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1377]:
  gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't
  acked to be open.
  Sep 13 20:56:21 om-gta02 user.notice root: Mux :  *** mux setup timed
  out *** 
  Sep 13 20:56:21 om-gta02 user.notice root: AtChat :  T : ^Z 
  Sep 13 20:56:21 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1377]:
  gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't
  acked to be open.
  Sep 13 20:56:31 om-gta02 user.notice root: Mux :  *** mux setup timed
  out *** 
  Sep 13 20:56:31 om-gta02 user.notice root: AtChat :  T : ^Z 
  Sep 13 20:56:31 om-gta02 local0.warn /usr/sbin/gsm0710muxd[1377]:
  gsm0710muxd.c:569:pseudo_device_read(): Write to a channel which wasn't
  acked to be open.
  Sep 13 20:56:41 om-gta02 user.notice root: Mux :  *** mux setup timed
  out *** 
  Sep 13 20:56:41 

Re: DFUScript v0.1 - Script to help flashing

2008-09-14 Thread Dale Maggee
Shawn,

I don't have multiple devices which support DFU, but I'd love to add 
support for this in my utility, so can you give me some advice on how 
this might work?
 - is there a way to list attached devices which are DFU-capable?
 - how are these hex codes obtained?
 - since you have them hardcoded, I assume they're an identifier code 
which is the same for all FR's and all 1973s (i.e the code identifies 
the type of device)?
 - is the hex code an argument you always need to pass if you're 
flashing a 1973 (i.e if you only have 1 device attached and it's a 1973, 
do you still need to give it the hex code or does it detect the 1973 and 
flash it without the hex code)?

One thought which might be the easiest method is to implement it as an 
item in the 'setup' menu which allows you to choose between a freerunner 
and a 1973 and provides the appropriate hex code. but it would be nice 
if I could detect that you have 2 devices attached and show an 'which 
device do you want to flash?' screen with a list of detected devices. 
this way if you only have one device attached it doesn't matter whether 
it's a 1973 or a freerunner.

I am planning on adding command line support for my script, which should 
make you happy. I may 'borrow' some of your code to implement this ;)

I will also add a 'flashing u-boot on a 1973 may give you a paperweight' 
warning to my tool.

I should probably also change all references to 'freerunner' in my 
script to say 'neo'.

as for the 'only have 30 seconds' thing, this is why I have the 'now is 
the time to turn on your device and activate the nand/nor menu' screen - 
the idea is that you select your desired flashing option, then get into 
the nand/nor menu on your device, then press OK and it starts. this is 
also why I included the ability to flash multiple images at once - so 
that for example you can flash rootfs and kernel without having the 
thing power off while you're typing the second command [I also type 
quicker than I click, but I don't do either particularly quickly ;) ]



Shawn prjktdtnt Thompson wrote:
 Minh,
 I am aware of Dale's work but if you have multiple devices that 
 support DFU then the gui will error out. I have seen the UI and it does 
 look very promising. I may stop using my script and go back to Dale's 
 gui when it supports the ability to select a specific device. I am kind 
 of a CLI enthusiast because I type much faster than I can click, which 
 is good when you've only got 30 seconds to issue a command.

 Thanks for the suggestion, I will add the link now.

 -Shawn

 Minh Ha Duong wrote:
   
 Shawn: are you aware of Dale's work ?

 May I suggest also a link to the script's page from:
 http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner#A_script_to_do_all_this_from_a_nice_GUI...

 Minh

 ___
 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

   


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


Re: import/export sms from qtopia

2008-09-14 Thread Vikas Saurabh
Ahhbut that seems to be too late for me. I already have information on
my current image.
I was wondering if I could somehow extract the info from the backup and put
it into the current one.

I just did this on my install, and it was as simple as copying my backup
 back to the phone.


BTW, I think all the messages (including sent and received) are stored under
qtmail folder (within the home directory) as different text files. But just
copying those didn't help. I guess qtopia makes some entry in its database.
I think qtopia's db is just a sqlite file.

Does anyone know the schema of their database? It might be helpful.

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


Re: FSO milestone3 my view (ON gta01)

2008-09-14 Thread Dale Maggee
Marco Trevisan (Treviño) wrote:
 Dale Maggee wrote:
   
 the only problem I have with zhone is missing features, such as an 
 internal PIM database - at present it only uses contacts stored in the 
 sim card. Also the fact that you can only send sms's to existing 
 contacts , and can't just type in a phone number. If it wasn't for these 
 couple of things I'd be happy to use FSO3 as my primary distribution. 
 

 When I used FSO for the first time, to workaround this, I simply 
 hardcoded my contacts in the zhone python files. It works well, also if 
 it's not so dynamic :P

   

great Idea! my contacts don't change often, so that would work as an 
interim method! :D

any chance you could tell me what file(s) I need to modify, and how to 
modify it (i.e example code, I don't [yet] speak python)?

Thanks!

-Dale

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


Re: DFUScript v0.1 - Script to help flashing

2008-09-14 Thread Shawn prjktdtnt Thompson
Dale,
I would be honored to see my code used in a project that serves a 
wider audience. I wrote the script mainly for my own use and figured I 
would submit it as a community project for those who wanted to use 
and/or improve upon it.

To find multiple DFU devices I would have to type dfu-util -l then 
pass dfu-util -d hexcode -a alternate -R -D imagefile.bin or some 
similar command to flash my device. Now I type ./dfuscript device 
alternate file.bin which takes me about half of what it did since I no 
longer need to list to grab the hex or type in additional arguments such 
as -R or -D.

The hex codes should be static for all Neo1973 or Neo FreeRunners as 
far as I'm aware. If anyone knows otherwise please correct me.

I think that adding the option to select your device type and then 
what images you would like to update would be great, a setup menu, as 
you suggested, would work for this also.

One feature I would love to see is the option you mentioned of 
updating multiple sections at once. Ex: if I have a new kernel and 
rootfs, instead of doing them separately I would be able to select, via 
a checkbox instead of radio-button, both of them, select each file, 
confirm that is what I want to flash to each section and finally be 
advised that I should power into NAND/NOR and press ok for it to loop 
through each section. My script doesn't have this ability but it was 
something I considered as it would make life quite a bit faster in that 
regard.

If I knew more about coding I would love to contribute additional 
code but for now all I can offer is what I have done so far. If any of 
my code could be useful to your script please use it. The fact that two 
open source fans can build upon each-other's work is why I love and back 
open-source wherever I can.

I'm looking forward to seeing more improvements to the gui and 
hopefully eventually seeing my script being made completely obsolete or 
even integrated into your program in some form.

-Shawn prjktdtnt Thompson

Dale Maggee wrote:
 Shawn,

 I don't have multiple devices which support DFU, but I'd love to add 
 support for this in my utility, so can you give me some advice on how 
 this might work?
  - is there a way to list attached devices which are DFU-capable?
  - how are these hex codes obtained?
  - since you have them hardcoded, I assume they're an identifier code 
 which is the same for all FR's and all 1973s (i.e the code identifies 
 the type of device)?
  - is the hex code an argument you always need to pass if you're 
 flashing a 1973 (i.e if you only have 1 device attached and it's a 1973, 
 do you still need to give it the hex code or does it detect the 1973 and 
 flash it without the hex code)?

 One thought which might be the easiest method is to implement it as an 
 item in the 'setup' menu which allows you to choose between a freerunner 
 and a 1973 and provides the appropriate hex code. but it would be nice 
 if I could detect that you have 2 devices attached and show an 'which 
 device do you want to flash?' screen with a list of detected devices. 
 this way if you only have one device attached it doesn't matter whether 
 it's a 1973 or a freerunner.

 I am planning on adding command line support for my script, which should 
 make you happy. I may 'borrow' some of your code to implement this ;)

 I will also add a 'flashing u-boot on a 1973 may give you a paperweight' 
 warning to my tool.

 I should probably also change all references to 'freerunner' in my 
 script to say 'neo'.

 as for the 'only have 30 seconds' thing, this is why I have the 'now is 
 the time to turn on your device and activate the nand/nor menu' screen - 
 the idea is that you select your desired flashing option, then get into 
 the nand/nor menu on your device, then press OK and it starts. this is 
 also why I included the ability to flash multiple images at once - so 
 that for example you can flash rootfs and kernel without having the 
 thing power off while you're typing the second command [I also type 
 quicker than I click, but I don't do either particularly quickly ;) ]



 Shawn prjktdtnt Thompson wrote:
   
 Minh,
 I am aware of Dale's work but if you have multiple devices that 
 support DFU then the gui will error out. I have seen the UI and it does 
 look very promising. I may stop using my script and go back to Dale's 
 gui when it supports the ability to select a specific device. I am kind 
 of a CLI enthusiast because I type much faster than I can click, which 
 is good when you've only got 30 seconds to issue a command.

 Thanks for the suggestion, I will add the link now.

 -Shawn

 Minh Ha Duong wrote:
   
 
 Shawn: are you aware of Dale's work ?

 May I suggest also a link to the script's page from:
 http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner#A_script_to_do_all_this_from_a_nice_GUI...

 Minh

 ___
 Openmoko community mailing list
 

Re: FSO milestone3 my view (ON gta01)

2008-09-14 Thread Dale Maggee
Fredrik Wendt wrote:
 Hi.

 fre 2008-09-12 klockan 12:24 +0200 skrev Tilman Baumann:
   
 I found the new fso milestone and tried it out on my Neo 1973.
 Here is what i think of it. 
 [...]
 And i would say it is time for some gui guidelines for new world etk, 
 efl apps.
 We have a great looking environment, now let's define how apps should 
 look. And pleas don't make them look like qtopia, Zhone or tichy.
 I have some ideas for that too. But i whink we need some experimenting 
 first...
 

 I hope I'm not the only one that think Zhone looks really nice (apart
 from the default background). Although it's just a temporary UI, put
 there to take advantage of the framework, I'm gonna miss it - it's
 simply beautiful.

 / Fredrik
   
As I said before, I agree that it's gorgeous. Any tips on changing the 
background?

you're gonna miss it? where's it going? :O

-Dale

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


Re: DFUScript v0.1 - Script to help flashing

2008-09-14 Thread Dale Maggee
Bill,
 On my work laptop with an external sun usb keyboard, I get two codes, so
 have to specify the FR when flashing.

 I can get a list (dfu-util -l) from it tomorrow afternoon if you wish.
   
that would be great
 ./dfu-util -d 0x1d50:0x5119 -a kernel -R -D uImage

 BillK
   
Thanks for the info, looking forward to seeing the dfu-util -l output. 
send it off-list if you prefer :)

-Dale

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


wesnoth

2008-09-14 Thread Hans-Martin
got this url from the irc: http://rafb.net/p/ihQ94Z51.html

beware: ~72MB!:

make sure to create a little start-script:

#!/bin/sh
xrandr -o 1  wesnoth -r 640x480
 


after installing all, you can correct the .desktop file 
in /usr/share/applications/wenoth.desktop

Icon=/usr/share/wesnoth/icons/wesnot-icon.png
Exec=*path-to-your-wesnoth-start-script


have fun

hama


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


Re: DFUScript v0.1 - Script to help flashing

2008-09-14 Thread Dale Maggee
Shawn,

replies inline.

Shawn prjktdtnt Thompson wrote:
 Dale,
 I would be honored to see my code used in a project that serves a 
 wider audience. I wrote the script mainly for my own use and figured I 
 would submit it as a community project for those who wanted to use 
 and/or improve upon it.
   
hehe, same here - I modified the original script for my own use, and 
decided to put it out there. fortunately for the 'wider audience' you 
mention, I'm part of that wider audience insofar as I'm have been known 
to make stupid mistakes every now and then, and I like to protect myself 
from them! When I say 'Idiot-proofing', I'm usually talking about myself! ;)
 To find multiple DFU devices I would have to type dfu-util -l then 
 pass dfu-util -d hexcode -a alternate -R -D imagefile.bin or some 
 similar command to flash my device. Now I type ./dfuscript device 
 alternate file.bin which takes me about half of what it did since I no 
 longer need to list to grab the hex or type in additional arguments such 
 as -R or -D.

 The hex codes should be static for all Neo1973 or Neo FreeRunners as 
 far as I'm aware. If anyone knows otherwise please correct me.
   
thanks for the info. Adding this to my utility will be a priority once I 
get the dfu-util -l output from Bill (you could send it too if you like)
 I think that adding the option to select your device type and then 
 what images you would like to update would be great, a setup menu, as 
 you suggested, would work for this also.
   
have you checked out the latest version of my utility? see [1]. The 
current version has a setup menu already, I'm thinking that this would 
be the place to put this option.

but if dfu-util -l gives hex codes I'll make it an option which will 
appear if multiple dfu-capable devices are attached, and it will list 
the devices and allow you to choose which one to flash.
 One feature I would love to see is the option you mentioned of 
 updating multiple sections at once. Ex: if I have a new kernel and 
 rootfs, instead of doing them separately I would be able to select, via 
 a checkbox instead of radio-button, both of them, select each file, 
 confirm that is what I want to flash to each section and finally be 
 advised that I should power into NAND/NOR and press ok for it to loop 
 through each section. My script doesn't have this ability but it was 
 something I considered as it would make life quite a bit faster in that 
 regard.
   
This is exactly what my utility does - it has checkboxes instead of 
radio buttons, you choose what to flash, then the file(s) you want to 
flash, then it shows you a confirmation screen which also advises you to 
go to NAND/NOR, you press OK, and it flashes everything you chose.

my tool is (now very loosely) based on the script by rorschach. This is 
the one which had radio buttons. I suspect that you're thinking of his 
script and not my version. The reason I modified it was to be able to 
flash multiple images at once... Then I kept thinking of other things to 
add ;)

(the original list of things I did to rorschach's script can be found at 
[2])

if you can make it through all my rambling at [1], you'll see that I 
make mention of being able to use my tool via the command-line. This 
would also support flashing multiple files at once I envision something 
like this:

frutil --flash kernel=/path/to/kernelfile.bin 
rootfs=/path/to/rootfsfile.jffs2 splash=/path/to/splashfile.tar.gz
 If I knew more about coding I would love to contribute additional 
 code but for now all I can offer is what I have done so far. If any of 
 my code could be useful to your script please use it. The fact that two 
 open source fans can build upon each-other's work is why I love and back 
 open-source wherever I can.
   
I've become a big open source fan for exactly this reason - the ability 
to collaborate like this is  IMHO vastly superior to the closed source 
model.
 I'm looking forward to seeing more improvements to the gui and 
 hopefully eventually seeing my script being made completely obsolete or 
 even integrated into your program in some form.
   
This is high praise and very encouraging, thanks alot! :)

-Dale

[1] http://lists.openmoko.org/pipermail/community/2008-September/030257.html
[2] http://lists.openmoko.org/pipermail/community/2008-September/029731.html

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


Re: wesnoth

2008-09-14 Thread Martin Šenkeřík
The URL doesn't work :-(


On 9/14/08, Hans-Martin [EMAIL PROTECTED] wrote:
 got this url from the irc: http://rafb.net/p/ihQ94Z51.html

  beware: ~72MB!:

  make sure to create a little start-script:

  #!/bin/sh
  xrandr -o 1  wesnoth -r 640x480



  after installing all, you can correct the .desktop file
  in /usr/share/applications/wenoth.desktop

  Icon=/usr/share/wesnoth/icons/wesnot-icon.png
  Exec=*path-to-your-wesnoth-start-script


  have fun

  hama


  ___
  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: wesnoth

2008-09-14 Thread Hans-Martin
the link is not available anymore and wesnoth can be installed with opkg 
now...



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


Re: wesnoth

2008-09-14 Thread Martin Šenkeřík
and from which repositories?


On 9/14/08, Hans-Martin [EMAIL PROTECTED] wrote:
 the link is not available anymore and wesnoth can be installed with opkg
  now...




  ___
  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


GSM Firmware crash

2008-09-14 Thread Andreas Fischer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all,

Yesterday I experienced a crash of the GSM firmware - my Freerunner
started to vibrate and there was a message on-screen that stated that
the GSM Firmware had crashed and that I would be unable to use phone
functionality. Is this a known bug?
I would open a bug in trac, but I don't have much info about the crash -
it seemed to happen just randomly (I was carrying the phone in my pocket
when it started to vibrate). Unfortunately I fear I've also b0rked the
logs, as I restarted the phone immediately. I needed phone functionality
and wasn't in reach of a computer at that time.
So - anyone else experienced this?

Regards,
Andreas Fischer
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIzSlU5Fl7TYZQYwERArBhAJwOYoob42BF4r+3Xp6kRntzNMrTAQCfaDFY
Bv55wGMLFf2z3saHvUP7j6M=
=MBPA
-END PGP SIGNATURE-

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


Howto make Navit usable for daily use

2008-09-14 Thread zappi

the most anoying thing about navit is, that the speech-dispatcher blocks the
audio when fr wake up  http://docs.openmoko.org/trac/ticket/1599 (bug #1599) 
from suspend. One way to resov it is do disable speech-disptcher at boot
time.

update-rc.d -f speech-dispatcher remove 

but navit makes no real fun without speech-dispatcher running, so i add to
the navit start script at /usr/bin/navit two things. at the top of the file
i'd add.

/etc/init.d/speech-dispatcher start

at the bottom of the file right after navit.real $* i'd add:

 /etc/init.d/speech-dispatcher stop

Here is the complete startscript that i use for starting navit (including
the  http://wiki.openmoko.org/wiki/Navit#Setting_up_Navit LANG  fix)


#! /bin/sh
#
# Copyright Matthias Hentges [EMAIL PROTECTED] (c) 2008
# License: GPL (see http://www.gnu.org/licenses/gpl.txt for a copy of the
license)
#
# Filename: navit.launcher
# Date: 20080105 (YMD)
#
###
##
#
# 20080105 - v0.0.1 - Initial release
/etc/init.d/speech-dispatcher start
export LANG=en_EN.utf8

# On devices with low memory ( 512Mb?) Navit will segfault on start.
# This can be worked around by doing
# echo 1  /proc/sys/vm/overcommit_memory

if test `cat /proc/meminfo | grep ^MemTotal | awk '{print $2}'` -lt
50
then
if test $USER = root
then
echo Enabling low-mem workaround...
echo 1  /proc/sys/vm/overcommit_memory
else
echo I need root-privs to enable the low-mem workaround!
fi
fi

navit.real $*  /etc/init.d/speech-dispatcher stop
--

this one works for me for the last 2 days maybe it help other to have more
fun with the fr. :)

zappi


-- 
View this message in context: 
http://n2.nabble.com/Howto-make-Navit-usable-for-daily-use-tp1088795p1088795.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


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


Re: wesnoth

2008-09-14 Thread Hans-Martin
Am Sonntag, 14. September 2008 17:08:00 schrieb Martin Šenkeřík:
 and from which repositories?

i use latest fdom here. didn't installed it with opkg, but can see it here 
with opkg list.



 On 9/14/08, Hans-Martin [EMAIL PROTECTED] wrote:
  the link is not available anymore and wesnoth can be installed with opkg
   now...


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


qtopia, earphone and mediaplayer

2008-09-14 Thread oscar
Hello everyone.

Trying qtopia 4.3.3, I noticed that if I plug in the headphones while
listening to a song, the sound is played through the FR's loudspeaker
at the same time as coming through the headphones.  If I disconnect
the headphones, the loudspeaker deactivates.


Doing a hexdump of /etc/input/events0, I see the following:

(Connecting the headphones)

[EMAIL PROTECTED]:~# hexdump -C /dev/input/event0

  99 67 cc 48 62 69 0a 00  05 00 02 00 01 00 00 00
0010  99 67 cc 48 b2 69 0a 00  00 00 00 00 00 00 00 00

(Disconnecting the headphones)

[EMAIL PROTECTED]:~# hexdump -C /dev/input/event0

  da 67 cc 48 3b 64 05 00  05 00 02 00 00 00 00 00
0010  da 67 cc 48 84 64 05 00  00 00 00 00 00 00 00 00

As you can see, at position 0x0c the value changes from 1 (if
connected) to 0 (if disconnected) - so that seems good.  Therefore I
think this problem must be something in the media player application.

Any ideas about this?

Thanks.
Oscar.



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


OpenMoko, OS X, address book sync'ing

2008-09-14 Thread Rodney Myers
I'm hoping to receive my OpenMoko phone this week, from the NYC group,  
and was wondering if any OS X user had any luck in getting their  
phones sync'd with AddressBook?


Thanks


PGP.sig
Description: This is a digitally signed message part
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: qtopia, earphone and mediaplayer

2008-09-14 Thread Martin Slouf
just a note -- i have quite simillar problems with 4.3.3-snapshot -- the
alsa state files are not loaded properly while listening to music,
receiveing calls and plug-in/out the headphones.

i always end up with the handset profile instead of headset profile if i
plug-in the headset.  quick fix for me was to replace handset.state with
headset.state; but this is ugly workaround.

martin.

On Sun, Sep 14, 2008 at 06:32:08PM +0200, oscar wrote:
 Hello everyone.
 
 Trying qtopia 4.3.3, I noticed that if I plug in the headphones while
 listening to a song, the sound is played through the FR's loudspeaker
 at the same time as coming through the headphones.  If I disconnect
 the headphones, the loudspeaker deactivates.
 
 
 Doing a hexdump of /etc/input/events0, I see the following:
 
 (Connecting the headphones)
 
 [EMAIL PROTECTED]:~# hexdump -C /dev/input/event0
 
   99 67 cc 48 62 69 0a 00  05 00 02 00 01 00 00 00
 0010  99 67 cc 48 b2 69 0a 00  00 00 00 00 00 00 00 00
 
 (Disconnecting the headphones)
 
 [EMAIL PROTECTED]:~# hexdump -C /dev/input/event0
 
   da 67 cc 48 3b 64 05 00  05 00 02 00 00 00 00 00
 0010  da 67 cc 48 84 64 05 00  00 00 00 00 00 00 00 00
 
 As you can see, at position 0x0c the value changes from 1 (if
 connected) to 0 (if disconnected) - so that seems good.  Therefore I
 think this problem must be something in the media player application.
 
 Any ideas about this?
 
 Thanks.
 Oscar.
 
 
 
 ___
 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


How to see flash video

2008-09-14 Thread Giovanni
How can I see a flash video (*.flv) on the Free Runner ?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: DFUScript v0.1 - Script to help flashing

2008-09-14 Thread Shawn prjktdtnt Thompson
Dale,
After looking at the source I may actually be able to assist in 
adding some of the code. I have work today so it would have to be later 
on. Also a suggestion is instead of telling someone to turn on their 
device and press ok, allow them to also cancel this action (for people 
like me who are only testing the program) ;)

First here is the hex codes to select:
Freerunner: 0x1d50:0x5119
Neo1973: 0x1457:0x5119
   
Flash kernel on freerunner: dfu-util -d 0x1d50:0x5119 -a kernel 
-R -D ./kernel.image.bin

The output of dfu-util -l looks like this (the hardware you see is 
not my phone but my laptop's built in bluetooth).

dfu-util - (C) 2007 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Found Runtime: [0x413c:0x8126] devnum=0, cfg=0, intf=3, alt=0, 
name=UNDEFINED

I'll look through the source of your gui and see what I can add in 
terms of selecting multiple devices and such. Will it add only the 
Neo1973 and Freerunner or allow it to do any listed device but just have 
the freerunner and neo1973 auto recognize? For me the reason I hard 
coded mine is because I am horrible with regex ;)  Hope this info helps.

-Shawn

Dale Maggee wrote:
 Shawn,

 replies inline.

 Shawn prjktdtnt Thompson wrote:
   
 Dale,
 I would be honored to see my code used in a project that serves a 
 wider audience. I wrote the script mainly for my own use and figured I 
 would submit it as a community project for those who wanted to use 
 and/or improve upon it.
   
 
 hehe, same here - I modified the original script for my own use, and 
 decided to put it out there. fortunately for the 'wider audience' you 
 mention, I'm part of that wider audience insofar as I'm have been known 
 to make stupid mistakes every now and then, and I like to protect myself 
 from them! When I say 'Idiot-proofing', I'm usually talking about myself! ;)
   
 To find multiple DFU devices I would have to type dfu-util -l then 
 pass dfu-util -d hexcode -a alternate -R -D imagefile.bin or some 
 similar command to flash my device. Now I type ./dfuscript device 
 alternate file.bin which takes me about half of what it did since I no 
 longer need to list to grab the hex or type in additional arguments such 
 as -R or -D.

 The hex codes should be static for all Neo1973 or Neo FreeRunners as 
 far as I'm aware. If anyone knows otherwise please correct me.
   
 
 thanks for the info. Adding this to my utility will be a priority once I 
 get the dfu-util -l output from Bill (you could send it too if you like)
   
 I think that adding the option to select your device type and then 
 what images you would like to update would be great, a setup menu, as 
 you suggested, would work for this also.
   
 
 have you checked out the latest version of my utility? see [1]. The 
 current version has a setup menu already, I'm thinking that this would 
 be the place to put this option.

 but if dfu-util -l gives hex codes I'll make it an option which will 
 appear if multiple dfu-capable devices are attached, and it will list 
 the devices and allow you to choose which one to flash.
   
 One feature I would love to see is the option you mentioned of 
 updating multiple sections at once. Ex: if I have a new kernel and 
 rootfs, instead of doing them separately I would be able to select, via 
 a checkbox instead of radio-button, both of them, select each file, 
 confirm that is what I want to flash to each section and finally be 
 advised that I should power into NAND/NOR and press ok for it to loop 
 through each section. My script doesn't have this ability but it was 
 something I considered as it would make life quite a bit faster in that 
 regard.
   
 
 This is exactly what my utility does - it has checkboxes instead of 
 radio buttons, you choose what to flash, then the file(s) you want to 
 flash, then it shows you a confirmation screen which also advises you to 
 go to NAND/NOR, you press OK, and it flashes everything you chose.

 my tool is (now very loosely) based on the script by rorschach. This is 
 the one which had radio buttons. I suspect that you're thinking of his 
 script and not my version. The reason I modified it was to be able to 
 flash multiple images at once... Then I kept thinking of other things to 
 add ;)

 (the original list of things I did to rorschach's script can be found at 
 [2])

 if you can make it through all my rambling at [1], you'll see that I 
 make mention of being able to use my tool via the command-line. This 
 would also support flashing multiple files at once I envision something 
 like this:

 frutil --flash kernel=/path/to/kernelfile.bin 
 rootfs=/path/to/rootfsfile.jffs2 splash=/path/to/splashfile.tar.gz
   
 If I knew more about coding I would love to contribute additional 
 code but for now all I can offer is what I have done so far. If any of 
 my code could be useful to your script please use it. The 

Re: Duke Nukem 3D on Openmoko Neo

2008-09-14 Thread Risto H. Kurppa
 #
 xrandr -s 240x320
 xrandr -o 3
 /media/card/duke3d/duke3d #MODIFY THIS TO SUIT YOUR INSTALL DIR!

Now I was able to make it run all the way to the first screen (had
some 'adventure games 3d' or similar text) but got stuck there or
didn't know what to do. I was running it straight from Freerunner so I
wasn't able to see the messages in stdout. Before running I confirmed
that I got hexdump from both accelerometers.

Had to boot by removing battery..


r

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


Re: FDOM updated

2008-09-14 Thread W.Kenworthy
On Mon, 2008-09-15 at 15:17 +1000, [EMAIL PROTECTED] wrote:
 William Kenworthy wrote:
  This has become a saga.  After failing to get FDOM-13092008 working from
  the SD card, I decided to try flashing it.
 
...
 I don't use fdom but it sounds suspiciously broken seeing as noone else 
 has reported it.
 
 Have you tried an updated uboot and kernel?
 
 It just seems strange that only you would receive a corrupt or 
 nonfunctiong userland ... hopefully it's just a mismatch.
 
 Sarton
 

I am using the matching kernel and jffs file and a uboot of almost the
same day.  Going to try some of the other family members sims and see if
they make a difference - shouldnt as this one works fine with 2007.2.

I did see some others say its working for them - so far what seems to be
happening is that the sim cant connect in time, qpe dies and never comes
back.

BillK


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


[debian] frameworkd affecting touch-screen input

2008-09-14 Thread Brock
When playing with some screen-drawing applications, including Xournal,
Gournal, and even Gimp, I noticed that I could draw long complex lines
but that they don't appear until I lift the stylus.

After some tinkering, I see that the lines are immediately drawn, or in
other words the data immediately given to the app, when frameworkd is
stopped.

Anyone know why that is?

Thanks,
--Brock


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


Re: Howto make Navit usable for daily use

2008-09-14 Thread umaxx
Rebutlah peluang emas ini..rm2000 masuk terus ke dalam akaun bank anda..
Usah risau pasal modal yang besar..kami sedia mambantu anda...
Kini modal hanya rm97 permulaan yang kecil tapi anda mampu mendapat pulangan
yang berganda..
IKUTILAH CARA DAN LANGKAH MENJADI FOREX TRADER,
Penerangan bermula dari asas forex,
termasuk step-by-step cara membuka trading account,
deposit modal dan mengeluarkan
wang hasil forex anda masuk ke bank pilihan anda.

Maklumat percuma layari:

http://tinyurl.com/56hy3a

http://tinyurl.com/56hy3a

Semoga usaha kita pasti berhasil...
sekian terima kasih.
Selamat maju jaya..Dari KUASA FOREX!!!

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
JUTAWAN KEBAJIKAN group.
To post to this group, send email to JUTAWAN-KEBAJIKAN@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/JUTAWAN-KEBAJIKAN?hl=en for a copy of
 the license)
 #
 # Filename: navit.launcher
 # Date: 20080105 (YMD)
 #
 ###
 ##
 #
 # 20080105 - v0.0.1   - Initial release
 /etc/init.d/speech-dispatcher start
 export LANG=en_EN.utf8
 
 # On devices with low memory ( 512Mb?) Navit will segfault on start.
 # This can be worked around by doing
 # echo 1  /proc/sys/vm/overcommit_memory
 
 if test `cat /proc/meminfo | grep ^MemTotal | awk '{print $2}'` -lt
 50
 then
   if test $USER = root
   then
   echo Enabling low-mem workaround...
   echo 1  /proc/sys/vm/overcommit_memory
   else
   echo I need root-privs to enable the low-mem
 workaround! fi
 fi
 
 navit.real $*  /etc/init.d/speech-dispatcher stop
 --
 
 this one works for me for the last 2 days maybe it help other to have
 more fun with the fr. :)
 

another solution (which is working at least for me) is to use navit with
flite instead of espeak+speech-dispatcher (here on 2008-asu)


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


unable to read from Sandisk 8Gb SD

2008-09-14 Thread Previdi Roberto
Hello. I have a big problem: i cannot read a new 8Gb SD card from Sandisk.

some details:

- the 512 Mb card works without any problem, i've been able to reformat it,
use ext2 on it, mount /usr in it
- i have partitioned the 8Gb card from my pc card reader and i've put a
kernel and a rootfs inside it as the wiki explain
- my FR card slot have got a little capacitor soldered between 2 pins, like
in this image (
http://makovey.objectis.net/Members/dimon/issues/om/microSD2.jpg/view) , but
with better soldering
- during all the experiments i never suspended-resumed the phone, and i am
sure the partitions in the card are not corrupted (because i checked them
periodically with the card reader)

- the boot loader see the card, and is able to load a kernel from it!
(in NAND menu)
$ cu -l /dev/ttyACM0
Connected.
In:usbtty
Out:   usbtty
Err:   usbtty
Unrecognized hardware revision 0x305. Defaulting to GTA02v6.
PCB rev: 0x305
Power: 0mA
GTA02v6 # mmcinit
Card Type:  SD 2.0 SDHC
Manufacturer:   0x03, OEM SD
Product name:   SU08G, revision 8.0
Serial number:  554005576
Manufacturing date: 8/2008
MMC/SD size:3MiB

All the output that follows is taken after booting from the internal flash,
just with the memory card inserted.
If instead i boot from the sd i noticed a strange behaviour: the first try
it sometimes fail to read the card, but the second try it works good, it
loads the kernel and the kernel output is exactly the same of the one below,
except it ends in a kernel panic not finding his root.

# uname -a
Linux roby-neo 2.6.24 #1 PREEMPT Wed Sep 3 19:01:18 CST 2008 armv4tl unknown

# cat /proc/cmdline
glamo_mci.sd_idleclk=1 glamo_mci.sd_max_clk=500 rootdelay=5
rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 console=tty0
loglevel=8 regular_boot
mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(u-boot),0x0004(u-boot_env),0x0080(kernel),0x000a(splash),0x0004(factory),0x0f6a(rootfs)

- i tried to set just the sd_max_clk to the values
(default,1000,833,500), i tried to set the sd_idleclk to 1 or to
0, with the sd_drive at 3 or 0 (doesn't know what's the effect).. nothing,
always the same errors.
- kernel output: (the relevant part, the complete one is attached)

 [...]
[3.23] *mmc0: new high speed SDHC card at address 8fe4*
[3.27] neo1973-pm-gps neo1973-pm-gps.0: FIC Neo1973 GPS Power
Managerment:starting
 [...]
[3.335000] Bluetooth: HCI USB driver ver 2.9
[3.34] usbcore: registered new interface driver hci_usb
[3.35] mmcblk0: mmc0:8fe4 *SU08G 7761920KiB*
[3.355000]  mmcblk0:6glamo-mci glamo-mci.0:* Error after cmd: 0x8310*
[3.37] mmcblk0:* error -110* sending read/write command
[3.375000] end_request: I/O error, dev mmcblk0, sector 0
[3.375000] Buffer I/O error on device mmcblk0, logical block 0
[3.38] glamo-mci glamo-mci.0:* Error after cmd: 0x20*
[3.385000] glamo-mci glamo-mci.0: *Error after cmd: 0x122*
[3.39] mmcblk0: *error -84* sending read/write command
[3.395000] end_request: I/O error, dev mmcblk0, sector 0
[3.395000] Buffer I/O error on device mmcblk0, logical block 0
[3.40]  *unable to read partition table*
[3.41] S3c2440 SDIO Host controller
[3.515000] pnp: the driver 'sdio_s3c24xx_hcd' has been registered
 [...]

Please, tell me that i can solve this problem! actually i'm sure it can be
solved, because the boot loader is perfectly (nearly) able to read and load
the kernel written in the sd.
Tell me if some other kind output could be useful.. maybe my shoes number?
:)

roby


boot-log-5Mhz.gz
Description: GNU Zip compressed data
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [Talk-de] construction=yes bitte nicht durch highway=construction ersetzen!!!

2008-09-14 Thread Garry
Tordanik schrieb:
 Hallo Garry,

   
 Aus aktuellem Anlass möchte ich eindringlich darum bitten die mit 
 construction=yes nicht durch highway=construction etc. zu ersetzen!!!
 

 gibt es einen speziellen Grund, warum du construction=yes verwendest,
 und nicht etwa life_cycle=construction? Der life_cycle-Ansatz (siehe
 http://wiki.openstreetmap.org/index.php/Proposed_Features/Status) hat
 den Vorzug, dass einer Anwendung nur einmal beigebracht werden muss,
 dass sie life_cycle=*-Features besser nicht zum Routing verwendet, und
 damit dann auch der Mapper, der life_cycle=planned einführt, das Problem
 nicht wieder vom neuen aufwirft. Sie hat auch keine mir bekannten
 Nachteile gegenüber construction/disused/abandoned=yes.

 Bei dieser Gelegenheit will ich auch gleich mal Werbung für meine eben
 angelegte kleine Wiki-Seite
 http://downloads.openmoko.org/framework/milestone3/

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


KLIK IKLAN DAPAT RUPIAH LANGSUNG DI BAYAR KE BANK ANDA

2008-09-14 Thread fatriyanto akase

Di Klikrupiah, anda akan mendapatkan uang setiap klik iklan.
Prosesnya cukup mudah anda cuma klik iklan dan lihat beberapa detik
kemudian uang masuk kesaldo anda. Anda tidak membutuhkan keahlian.
Yang anda butuhkan hanya lihat iklan dan klik yang ada di website
kami. Anda
bisa mengajak teman anda untuk bergabung dengan kami.

Pembayaran bisa kapan saja dan akan kami proses lewat Bank BCA dan
Mandiri. Mimimal pembayaran Rp50.000.

Contoh pendapatan
» Anda klik 10 iklan per hari = Rp 1000
» 20 referrals klik 10 iklan per hari = Rp 1
» Pendapatan harian anda = Rp 11000
» Pendapatan mingguan= Rp 77000
» Pendapatan bulanan= Rp 33
» Pendapatan pertahun= Rp 396


Mau Join Klik di sini

http://klikrupiah.com/register.php?r=fatriyanto

http://indoptc.com/news.php?r=fatriyanto

http://gedebux.info/register.php?r=fatriyanto
l -l looks like this (the hardware you see is 
 not my phone but my laptop's built in bluetooth).

 dfu-util - (C) 2007 by OpenMoko Inc.
 This program is Free Software and has ABSOLUTELY NO WARRANTY

 Found Runtime: [0x413c:0x8126] devnum=0, cfg=0, intf=3, alt=0, 
 name=UNDEFINED

 I'll look through the source of your gui and see what I can add in 
 terms of selecting multiple devices and such. Will it add only the 
 Neo1973 and Freerunner or allow it to do any listed device but just have 
 the freerunner and neo1973 auto recognize? For me the reason I hard 
 coded mine is because I am horrible with regex ;)  Hope this info helps.

 -Shawn

 Dale Maggee wrote:
   
 Shawn,

 replies inline.

 Shawn prjktdtnt Thompson wrote:
   
 
 Dale,
 I would be honored to see my code used in a project that serves a 
 wider audience. I wrote the script mainly for my own use and figured I 
 would submit it as a community project for those who wanted to use 
 and/or improve upon it.
   
 
   
 hehe, same here - I modified the original script for my own use, and 
 decided to put it out there. fortunately for the 'wider audience' you 
 mention, I'm part of that wider audience insofar as I'm have been known 
 to make stupid mistakes every now and then, and I like to protect myself 
 from them! When I say 'Idiot-proofing', I'm usually talking about myself! ;)
   
 
 To find multiple DFU devices I would have to type dfu-util -l then 
 pass dfu-util -d hexcode -a alternate -R -D imagefile.bin or some 
 similar command to flash my device. Now I type ./dfuscript device 
 alternate file.bin which takes me about half of what it did since I no 
 longer need to list to grab the hex or type in additional arguments such 
 as -R or -D.

 The hex codes should be static for all Neo1973 or Neo FreeRunners as 
 far as I'm aware. If anyone knows otherwise please correct me.
   
 
   
 thanks for the info. Adding this to my utility will be a priority once I 
 get the dfu-util -l output from Bill (you could send it too if you like)
   
 
 I think that adding the option to select your device type and then 
 what images you would like to update would be great, a setup menu, as 
 you suggested, would work for this also.
   
 
   
 have you checked out the latest version of my utility? see [1]. The 
 current version has a setup menu already, I'm thinking that this would 
 be the place to put this option.

 but if dfu-util -l gives hex codes I'll make it an option which will 
 appear if multiple dfu-capable devices are attached, and it will list 
 the devices and allow you to choose which one to flash.
   
 
 One feature I would love to see is the option you mentioned of 
 updating multiple sections at once. Ex: if I have a new kernel and 
 rootfs, instead of doing them separately I would be able to select, via 
 a checkbox instead of radio-button, both of them, select each file, 
 confirm that is what I want to flash to each section and finally be 
 advised that I should power into NAND/NOR and press ok for it to loop 
 through each section. My script doesn't have this ability but it was 
 something I considered as it would make life quite a bit faster in that 
 regard.
   
 
   
 This is exactly what my utility does - it has checkboxes instead of 
 radio buttons, you choose what to flash, then the file(s) you want to 
 flash, then it shows you a confirmation screen which also advises you to 
 go to NAND/NOR, you press OK, and it flashes everything you chose.

 my tool is (now very loosely) based on the script by rorschach. This is 
 the one which had radio buttons. I suspect that you're thinking of his 
 script and not my version. The reason I modified it was to be able to 
 flash multiple images at once... Then I kept thinking of other things to 
 add ;)

 (the original list of things I did to rorschach's script can be found at 
 [2])

 if you can make it through all my rambling at [1], you'll see that I 
 make mention of being able to use my tool via the command-line. This 
 would also support flashing multiple files at once I envision something 
 like