Re: RFC: FSOSHRCON 2010 kickoff
Hi All, I'm curious if the meeting has been planned? When it's already known where it'll be and which date? Regards, Joop. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QSuunto-Lite
Is/will QSuunto-Lite a KDE program i.e. will it also run on kde4? Is some qSuunto-Lite code already available. (I have a Suunto Cobra). Regards, Joop. On Thu, July 9, 2009 8:31 pm, Christian Rüb wrote: Hi, glad someone is interested in this one as I want to (re)concentrate on it again. You can use divetools-ab to download via USB serial (see my little patch here [1]) - the package is already capable of using /dev/ttyUSB0 You need to switch to host mode and have a special adapter for your regular USB plug to fit into the mini USB (~ â¬1.5 on ebay). Or you download them on your PC with divetools-ab and upload just the file. QSuunto-Lite can only _display_ information from file _not_ download itself. These features are planned for the next dive program which will also not be Suunto specific and hopefully get GPS integration and stuff - but this is still a long way... Next (and probably last) feature for QSuunto-Lite will be to display the dive profile graphically. I am not planning to do it in elmentary as it was my first real program in C++ and QT and thus also meant to learn it. But for the next program maybe it will be possible to seperate GUI and logic enough, so there could be a QT (e.g. for Desktop PCs) and an elementary GUI. My primary target is the above mentioned feature for QSuunto-Lite and then getting the new dive logging application on the way. Concering QSuunto-Lite - make sure you have one of the older Suuntos that are compatible with divetools-ab [2]. Newer Suuntos are also planned to be supported in the new app. [1] http://git.senfdax.de/?p=oe_recipes;a=blob;f=divetools-ab/files/001_usbserial.patch [2] a) http://www.acs.uni-duesseldorf.de/~becka/dive/divetools/index.html b) http://www.sarnau.info/papers:suunto_protocol see Vyper, Spyder, etc. Hope this helps. Cheers, Christian Thanks for this! Questions: * What are the features you're currently working on? * This requires that the FR is in host mode to download from the dive computer, correct? * As asked earlier, any chance of porting to elementary rather than QT? Now I can't wait to get my phone back from buzz fix! Russell Dwiggins ___ 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
NeoTool
All,
I've changed a few things in NeoTool.
1) No need to run it as root any more as long as you are in the uucp group.
2) The config is saved in ~/.neotoolrc
3) The backup directory can be chosen, the default is: ~/openmoko/backups
I couldn't reach the original maintainer yet. So i build version 1.2.1 for
now, in the rpm packages.
Regards,
Joop Boonen.
I couldn't reach the original maintainer yet.
This is the NeoTool.patch:
--- NeoTool-old 2009-02-14 21:07:33.0 +0100
+++ NeoTool 2009-02-15 13:59:36.0 +0100
@@ -1,5 +1,5 @@
#!/bin/bash
-VERSION='1.2'
+VERSION='1.2.1'
#
# NeoTool $VERSION
# By AntiSol, antisol (at) internode (dot) on (dot) net
@@ -41,12 +41,16 @@
# /data/openmoko/backups/{date}/{image}_backup
# and the {date} directory will be created by
NeoTool, assuming /data/openmoko/backups exists
# and you have permission.
+# v1.2.1 - 15/02/2009 - joop_boonen (at) web (dot) de
+# - Can now run as non root the user should be add to group
uucp
+# - The config is now written in ~/.neotoolrc
+# - The backup directory can now be choosen default
~/openmoko/backups
#
#
-settings_file='/etc/frutil'
+settings_file=$HOME/.neotoolrc
tmp_error_log_path='/tmp/flash-error-log'
-tmpfile='/tmp/frutil.tmp'
+tmpfile='/tmp/neotool.tmp'
function find_dfu {
#use 'which'...
@@ -75,7 +79,7 @@
clear
echo 'Downloading dfu-util...'
rm ./dfu-util /dev/null 21
- wget
http://downloads.openmoko.org/daily/dfu-util
+ wget
http://downloads.openmoko.org/distro/releases/Om2008.9/dfu-util
chmod a+x ./dfu-util /dev/null
dfutils_path='./dfu-util'
else
@@ -185,8 +189,8 @@
function flash {
- if [ $user != root ]; then
- zenity --error --text You can only flash your device if
you are root!
+ if [ $group != uucp ]; then
+ zenity --error --text You can only flash your device if
you are root! $group
return
fi
@@ -318,7 +322,7 @@
}
function setup_menu {
- sans=`zenity --title NeoTool Configurification --text Choose an
option --list --height=320 --width=500 --column --column 1 Locate
dfu-util ($dfutils_path) 2 Set your device's IP ($FRIP) 3 Choose
backup filename ($backupfn) 4 Setup date command ($datecmd) 5 Test
settings defined in (3) and (4) 6 Save These Settings 7 Reset to
defaults 8 Back to Main Menu`
+ sans=`zenity --title NeoTool Configurification --text Choose an
option --list --height=320 --width=500 --column --column 1 Locate
dfu-util ($dfutils_path) 2 Set your device's IP ($FRIP) 3 Choose
backup filename ($backupfn) 4 Setup date command ($datecmd) 5 Choose
backup directory ($backupdir) 6 Test settings defined in (3), (4) and
(5) 7 Save These Settings 8 Reset to defaults 9 Back to Main Menu`
}
@@ -355,29 +359,31 @@
fi
;;
5)
- tmp=${backupfn//{date}/`$datecmd`}
+ oldbackupdir=$backupdir
+ backupdir=$(zenity --entry --text `printf Enter
the default directoryname to be used for backups.\nuse '{image}' for the
Image type (kernel, rootfs, etc), \nand '{date}' for the date.\n the file
extension will be added automatically.` --entry-text $backupdir
--title Configure Backup Directoryname)
+ if [ -z $backupdir ]; then
+ backupdir=$oldbackupdir
+ fi
+ ;;
+ 6)
+ tmp=$backupdir/${backupfn//{date}/`$datecmd`}
tmp=${tmp//{image}/rootfs}.jffs2\n${tmp//{image}/kernel}.bin
zenity --info --title Example Backup File --text
Using the rules defined by current settings,
backup filenames will look something like
this:\n\n$tmp
;;
-6)
- if [ $user != root ]; then
- zenity --error --text You are not root, cannot
save settings!
- else
+7)
echo dfutils_path='$dfutils_path' $settings_file
echo FRIP='$FRIP' $settings_file
echo backupfn='$backupfn' $settings_file
echo datecmd='$datecmd' $settings_file
+ echo backupdir='$backupdir' $settings_file
zenity --info --text Settings saved to
$settings_file --title Done.
- fi;;
+ ;;
-7)
- if [ $user != root
Re: NeoTool (Correction!)
On Sun, February 15, 2009 2:35 pm, Joop Boonen wrote:
All,
I've changed a few things in NeoTool.
1) No need to run it as root any more as long as you are in the uucp
group.
2) The config is saved in ~/.neotoolrc
3) The backup directory can be chosen, the default is: ~/openmoko/backups
I couldn't reach the original maintainer yet. So i build version 1.2.1 for
now, in the rpm packages.
Regards,
Joop Boonen.
I couldn't reach the original maintainer yet.
This is the NeoTool.patch:
I accedently added the wrong patch.
THis is the rioght one:
--- NeoTool-old 2009-02-14 21:07:33.0 +0100
+++ NeoTool 2009-02-15 14:38:51.0 +0100
@@ -1,5 +1,5 @@
#!/bin/bash
-VERSION='1.2'
+VERSION='1.2.1'
#
# NeoTool $VERSION
# By AntiSol, antisol (at) internode (dot) on (dot) net
@@ -41,12 +41,16 @@
# /data/openmoko/backups/{date}/{image}_backup
# and the {date} directory will be created by
NeoTool, assuming /data/openmoko/backups exists
# and you have permission.
+# v1.2.1 - 15/02/2009 - joop_boonen (at) web (dot) de
+# - Can now run as non root the user should be add to group
uucp
+# - The config is now written in ~/.neotoolrc
+# - The backup directory can now be choosen default
~/openmoko/backups
#
#
-settings_file='/etc/frutil'
+settings_file=$HOME/.neotoolrc
tmp_error_log_path='/tmp/flash-error-log'
-tmpfile='/tmp/frutil.tmp'
+tmpfile='/tmp/neotool.tmp'
function find_dfu {
#use 'which'...
@@ -75,7 +79,7 @@
clear
echo 'Downloading dfu-util...'
rm ./dfu-util /dev/null 21
- wget
http://downloads.openmoko.org/daily/dfu-util
+ wget
http://downloads.openmoko.org/distro/releases/Om2008.9/dfu-util
chmod a+x ./dfu-util /dev/null
dfutils_path='./dfu-util'
else
@@ -185,8 +189,8 @@
function flash {
- if [ $user != root ]; then
- zenity --error --text You can only flash your device if
you are root!
+ if [ $groups = ${groups/uucp/} ]; then
+ zenity --error --text You can only flash your device if
you are in the uucp group!
return
fi
@@ -318,7 +322,7 @@
}
function setup_menu {
- sans=`zenity --title NeoTool Configurification --text Choose an
option --list --height=320 --width=500 --column --column 1 Locate
dfu-util ($dfutils_path) 2 Set your device's IP ($FRIP) 3 Choose
backup filename ($backupfn) 4 Setup date command ($datecmd) 5 Test
settings defined in (3) and (4) 6 Save These Settings 7 Reset to
defaults 8 Back to Main Menu`
+ sans=`zenity --title NeoTool Configurification --text Choose an
option --list --height=320 --width=500 --column --column 1 Locate
dfu-util ($dfutils_path) 2 Set your device's IP ($FRIP) 3 Choose
backup filename ($backupfn) 4 Setup date command ($datecmd) 5 Choose
backup directory ($backupdir) 6 Test settings defined in (3), (4) and
(5) 7 Save These Settings 8 Reset to defaults 9 Back to Main Menu`
}
@@ -355,29 +359,31 @@
fi
;;
5)
- tmp=${backupfn//{date}/`$datecmd`}
+ oldbackupdir=$backupdir
+ backupdir=$(zenity --entry --text `printf Enter
the default directoryname to be used for backups.\nuse '{image}' for the
Image type (kernel, rootfs, etc), \nand '{date}' for the date.\n the file
extension will be added automatically.` --entry-text $backupdir
--title Configure Backup Directoryname)
+ if [ -z $backupdir ]; then
+ backupdir=$oldbackupdir
+ fi
+ ;;
+ 6)
+ tmp=$backupdir/${backupfn//{date}/`$datecmd`}
tmp=${tmp//{image}/rootfs}.jffs2\n${tmp//{image}/kernel}.bin
zenity --info --title Example Backup File --text
Using the rules defined by current settings,
backup filenames will look something like
this:\n\n$tmp
;;
-6)
- if [ $user != root ]; then
- zenity --error --text You are not root, cannot
save settings!
- else
+7)
echo dfutils_path='$dfutils_path' $settings_file
echo FRIP='$FRIP' $settings_file
echo backupfn='$backupfn' $settings_file
echo datecmd='$datecmd' $settings_file
+ echo backupdir='$backupdir' $settings_file
zenity --info --text Settings saved
RPM packages for dfu-util and NeoTool
All, I've created rpm packages for dfu-util and NeoTool. You can find the links on the web pages for these tools: http://wiki.openmoko.org/wiki/Dfu-util http://wiki.openmoko.org/wiki/NeoTool dfu-util will be updated to a more recent svn version on a regular bases. Regards, Joop. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: kismet on freerunner
On Wed, November 26, 2008 2:26 pm, David Reyes Samblas Martinez wrote: snip FATAL: Failed to set monitor mode: Invalid argument. This usually means your drivers either do not support monitor mode, or use a different mechanism for getting to it. Make sure you have a version of your drivers that support monitor mode, and consult the troubleshooting section of the README. snip Nowadays wifi drivers doesn't support monitor mode, the only way to use freerunner as kismet scaner is attaching an usb wifi dongle. Why don't the drivers support monitor mode? Would it be possible to add it to this driver? To me it's not preferable to add an extra wifi dongle when the device has wifi itself. -- David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions Openmoko, Openpandora, GP2X the Wiz, Letux 400 Hey, watch out!!! There's a linux in your pocket!!! ___ 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
420MP 4-port USB 2.0 Hub (CP-H420MP)
All, I've been looking for this usb hub for quite some time, but I cant find it in Western-Europe mainland (where I can pay by bank transaction). Does anyone know where in Western-Europe i can buy this hub? Regards, Joop. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
qemu patch for gcc 4 doesn't work anymore
All, I have a question about the gcc 4 patch for qemu. If I follow the build instructions for qemu: http://wiki.openmoko.org/wiki/Qemu I cant patch the qemu for gcc4. Regards, Joop Boonen. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
qemu download.sh isn;t ok any more. File names aren't ok
[EMAIL PROTECTED]:~/work/qemu-openmoko/qemu-neo1973 sh -x
openmoko/download.sh
+ . openmoko/env
+++ pwd
++ src_dir=/home/jboonen/work/qemu-openmoko/qemu-neo1973
++ script_dir_relative=openmoko
++ script_dir=/home/jboonen/work/qemu-openmoko/qemu-neo1973/openmoko
++ uboot_symlink=/home/jboonen/work/qemu-openmoko/qemu-neo1973/u-boot.bin
++ qemu_relative='arm-softmmu/qemu-system-arm -M gta01 -m 130'
++
qemu='/home/jboonen/work/qemu-openmoko/qemu-neo1973/arm-softmmu/qemu-system-arm
-M gta01 -m 130'
++ flash_base=openmoko-flash.base
++ flash_image=openmoko-flash.image
++ make=make
++ which gmake
/usr/bin/gmake
++ make=gmake
++ echo=echo
++ which gecho
which: no gecho in
(/home/jboonen/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/kde3/bin:/usr/lib/jvm/jre/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin)
++ export make echo
++ dump_dir=/home/jboonen/work/qemu-openmoko/qemu-neo1973/openmoko/vvfat
++ qemu_monitor=/home/jboonen/.qemu_monitor
++ kernel_addr=0x3010
++ splash_addr=0x3600
++ splash_size=0x5000
++ kernel_wildcard='testing-om-gta01-*.uImage.bin'
++ rootfs_wildcard='testing-om-gta01-*.rootfs.jffs2'
++ uboot_wildcard=gta01bv4-u-boot.bin
++ download_dir=http://downloads.openmoko.org/daily/
++ dev_download_dir=http://downloads.openmoko.org/daily/
++ backup_download_dir=http://buildhost.automated.it/OM2007.2/
+ cd /home/jboonen/work/qemu-openmoko/qemu-neo1973/openmoko
+ echo 'Retrieving' available builds list...
Retrieving available builds list...
++ lynx -dump http://downloads.openmoko.org/daily/
++ grep http
++ sed 's,[0-9
\t\.]*http://downloads.openmoko.org/daily/\([a-zA-Z0-9_\.-]\)[ \t]*,\1,'
+ files=' 1. http://downloads.openmoko.org/daily/?C=N;O=D
2. http://downloads.openmoko.org/daily/?C=M;O=A
3. http://downloads.openmoko.org/daily/?C=S;O=A
4. http://downloads.openmoko.org/daily/?C=D;O=A
5. http://downloads.openmoko.org/
testing/
unstable/'
++ lynx -dump http://downloads.openmoko.org/daily/
++ grep http
++ sed 's,[0-9
\t\.]*http://downloads.openmoko.org/daily/\([a-zA-Z0-9_\.-]\)[ \t]*,\1,'
+ dev_files=' 1. http://downloads.openmoko.org/daily/?C=N;O=D
2. http://downloads.openmoko.org/daily/?C=M;O=A
3. http://downloads.openmoko.org/daily/?C=S;O=A
4. http://downloads.openmoko.org/daily/?C=D;O=A
5. http://downloads.openmoko.org/
testing/
unstable/'
+ [[1. http://downloads.openmoko.org/daily/?C=N;O=D
2. http://downloads.openmoko.org/daily/?C=M;O=A
3. http://downloads.openmoko.org/daily/?C=S;O=A
4. http://downloads.openmoko.org/daily/?C=D;O=A
5. http://downloads.openmoko.org/
testing/
unstable/ == '' ]]
+ echo -n 'Kernel' 'is... '
Kernel is... + most_recent 'testing-om-gta01-*.uImage.bin'
kernel_image ''
+ echo
+ f=files
+ for name in '${!f}'
+ [[ 1. == testing-om-gta01-*.uImage.bin ]]
+ for name in '${!f}'
+ [[ http://downloads.openmoko.org/daily/?C=N;O=D ==
testing-om-gta01-*.uImage.bin ]]
+ for name in '${!f}'
+ [[ 2. == testing-om-gta01-*.uImage.bin ]]
+ for name in '${!f}'
+ [[ http://downloads.openmoko.org/daily/?C=M;O=A ==
testing-om-gta01-*.uImage.bin ]]
+ for name in '${!f}'
+ [[ 3. == testing-om-gta01-*.uImage.bin ]]
+ for name in '${!f}'
+ [[ http://downloads.openmoko.org/daily/?C=S;O=A ==
testing-om-gta01-*.uImage.bin ]]
+ for name in '${!f}'
+ [[ 4. == testing-om-gta01-*.uImage.bin ]]
+ for name in '${!f}'
+ [[ http://downloads.openmoko.org/daily/?C=D;O=A ==
testing-om-gta01-*.uImage.bin ]]
+ for name in '${!f}'
+ [[ 5. == testing-om-gta01-*.uImage.bin ]]
+ for name in '${!f}'
+ [[ http://downloads.openmoko.org/ == testing-om-gta01-*.uImage.bin ]]
+ for name in '${!f}'
+ [[ testing/ == testing-om-gta01-*.uImage.bin ]]
+ for name in '${!f}'
+ [[ unstable/ == testing-om-gta01-*.uImage.bin ]]
++ sort -n .list
++ tail -n 1
+ export kernel_image=
+ kernel_image=
+ rm -rf .list
+ '[' -z '' ']'
+ echo not found
not found
+ exit -1
[EMAIL PROTECTED]:~/work/qemu-openmoko/qemu-neo1973
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: What theme is this?
The grey theme was done by BluesLee on #openmoko-cdevel, for SHR. It'll be packaged as soon as I have some spare time :-) -- Julien Cassignol http://www.ainulindale.net ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community That's great to hear. :) Thanks. Regards, Joop. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: What theme is this?
Tilman Baumann wrote: Leonti Bielski wrote: Hi! I found this image on scap.linuxtogo.org http://scap.linuxtogo.org/files/cb247f8d70308d5fec6a479c329e75f3.png There are also some other themes. Where I can download it? Who is making it? Thanks. Leonti I agree it looks nice. And as we are on this topic. I think this theme http://scap.linuxtogo.org/files/4dc340d6661464ca15a0789011cdd3c6.png is ingenious! I never liked the grey theme. Bright colours on black are the way to go. Of course it's a matter of taste. But I also like the black and white theme much more that the colourful theme. They give me a more professional feeling. I'm also interested in where it can be downloaded. Regards, Joop. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: consider buying Neo Freerunner
The problems mentioned are do they occur in both qtopia as in OM2008? I understood that qtopia is more stable. If this is true why no make it dual boot, as is possible. Boot up in Qtopia when the phone has to be stable and when a problem is ok, boot up in OM2008? I'm going to order my Freerunner soon. I think in spite of it's problem it's the best embedded product, with total freedom, around right now. Regards, Joop. xaos wrote: Qtextended is probably the most stable at this point, and that has it's caveats. Incoming calls are always registered as missed calls. Incoming calls are always answered as speakerphone, instead of handset. I'm not sure if there is a setting for it, but I haven't been able to find it. If anyone can point me in the right direction, I'd appreciate it as I hate having to remember to switch it to handset after I answer a call. Often, accessing the keyboard after a call starts is impossible, which makes it difficult when you have to navigate through a company VM menu. You can use the Smart theme which works a little better but you will need to use the stylus to access the .5 x .5 dialpad the comes up in a call. SMS messages received will often double themselves, or show five or six times the amount of new messages in the New Message alert. Select All-Move to Trash works sometimes, sometimes not, and it will often redownload them from the SMS server after the phone crashes/hangs/doesn't-come-out-of-suspend and requires a hard restart which, for me, is about every two or three days. Using the stylus is almost a necessity; you're not going to have much luck using your finger for anything other than the largest, most well-divided buttons. Even on the menus, you'll find yourself selecting the wrong entry over and over (fingernails are not much of an option for me. I'm a guitarist and keep them pretty short.) The dockable qwerty keyboard works moderately well for composing messages with the stylus, but the arrow keys don't work in the terminal, so be prepared to type commands over and over, as the bash/ash history is not accessible. The predictive text keyboard is mostly unusable due to the inability after a word or two to change keyboard types or erase characters. I don't use the alarm so I can't comment on the issues others have had with that module. MP3 playback is pointless as it stutters constantly. WEP wireless connections seem to only be available via command line. I can't connect via WEP by the GUI, so I just wrote a script to do it. Even that is weird, as I have to follow the following sequence to get that to work: iwconfig eth0 essid my_ap enc my_encryption_key; sleep 2; iwconfig eth0 essid any; sleep 2; udhcpd eth0; The first time I call the script it fails. so I control-C it, and run it again (the up arrow on the keyboard would be very handy here in the terminal.) The second time it works and gets an IP address, however it seems resolvconf is not updated (even though the DNS addresses are in resolv.conf) as I can't ping by DNS, only IP. Now, if i run it a third time it works like a charm. I don't know if this is something odd with my network and the card on the Neo, or what but my laptop connects fine with Ubuntu. These things of course have all been filed as bugs already AFAIK. If there are fixes for anything I've mentioned here, I'd love to apply them. I'm not sure if the phone is just grossly underpowered for what we are trying to do with it (MP3 playback) or if it's just that the software has a lng way to go before being usable as a day-to-day phone with some extra PDA features. So, in conclusion, I'd say there are a lot less expensive gadget phones out there that do more and will not result in your hair turning gray prematurely. The Neo is a wonderful idea, just not implemented very well I guess. The design is nice, it's case feels better in your hand than any other phone I've used. It's nice to have linux on my phone and be able to do all the things I'd do with my laptop or desktop, but without GPRS or 3G availability, it's kind of silly. If I have access to wireless APs, I'll have my laptop most likely, so why use the phone for that stuff? The display resolution is crisp and many people have commented to me on that. I like the phone, I just can't use it without a lot of finger digit acrobatics. /rambling -Tom Whenever you find that you are on the side of the majority, it is time to pause and reflect. -- Mark Twain On Tue, Oct 21, 2008 at 11:42 AM, Alastair Johnson [EMAIL PROTECTED] wrote: Shawn prjktdtnt Thompson wrote: William Kenworthy wrote: No, you are in the vast majority I think - those who can reliably make phone and sms calls are in the minority - if they even exist. BillK Those of use using reliably are minority but we do exist. Occasionally the phone will coma on me and require a hard restart (remove battery and reinsert)
rpm packages for openmoko-*-arm(v4t)-linux-gnueabi-toolchain
All, I'm currently working on rpm packages (Centos/Fedora/Mandriva/OpenSuSE) for openmoko-*-arm(v4t)-linux-gnueabi-toolchain. (Packed from the binaries provided by the openmoko project). I think I got them to work. I didn't test them yet. I'm wonder is it helpful for the openmoko people? The packages can be found at: http://download.opensuse.org/repositories/home:/worldcitizen/ Please drop me a line if they don't work as they should or when you think it's no use (if possible also explain why). Regards, Joop Boonen. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: rpm packages for openmoko-*-arm(v4t)-linux-gnueabi-toolchain
Short remark: The i686 version is probably not up to date yet as it's not build, yet. The last version that is. Joop Boonen wrote: All, I'm currently working on rpm packages (Centos/Fedora/Mandriva/OpenSuSE) for openmoko-*-arm(v4t)-linux-gnueabi-toolchain. (Packed from the binaries provided by the openmoko project). I think I got them to work. I didn't test them yet. I'm wonder is it helpful for the openmoko people? The packages can be found at: http://download.opensuse.org/repositories/home:/worldcitizen/ Please drop me a line if they don't work as they should or when you think it's no use (if possible also explain why). Regards, Joop Boonen. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
