http://wiki.openmoko.org/api.php?action=feedcontributions&user=Quicksand&feedformat=atomOpenmoko - User contributions [en]2013-05-23T21:40:45ZUser contributionsMediaWiki 1.19.6http://wiki.openmoko.org/wiki/Who_is_WhoWho is Who2008-04-10T18:42:45Z<p>Quicksand: </p>
<hr />
<div>==Why this page ?==<br />
<br />
If you subscribe for a mailing list, you will see people speaking, answering some questions, but you may ask : Who is who ? Who can I trust when they say something ?<br />
So I propose to fill this list to help people knowing each other<br />
<br />
==Officials members of the Openmoko Team==<br />
<br />
{| border="1"<br />
! !! Username !! Real name !! Nationality !! Remarks<br />
|-<br />
|1. ||[[User|User]] || || ||<br />
|}<br />
<br />
==GTA01 Owners==<br />
<br />
{| border="1"<br />
! !! Username !! Real name !! Nationality !! Remarks<br />
|-<br />
|1. ||[[User:jluis|jluis]] || José Luis Perez Diez || Spanish ||Barcelona<br />
|-<br />
|2. ||[[User:liuxf|liuxf]] || Xiangfu liu || Chinese || CHN-CUGSM<br />
|-<br />
|3. ||[[User:Kevin_Dean|Kevin Dean]] || Kevin Dean || USA || Washinton DC Metro Area<br />
|-<br />
|4. ||[[User:Quicksand|Quicksand]] || Clarke Wixon || USA || San Francisco Bay Area<br />
<br />
|}<br />
<br />
==GTA02 (Freerunner) Owners==<br />
<br />
{| border="1"<br />
! !! Username !! Real name !! Nationality !! Remarks<br />
|-<br />
|1. ||[[User|User]] || || ||<br />
|}<br />
<br />
==Future Owner==<br />
<br />
{| border="1"<br />
! !! Username !! Real name !! Nationality !! Remarks<br />
|-<br />
|1. ||[[Sleg|Sleg]] || Cédric D || French || Curious about this future device, will buy one ASAP<br />
|-<br />
|2. ||[[User:Lux|Lux]] || Dirk Deimeke || German || Living in Switzerland, already ordered<br />
|-<br />
|3. ||[[User:Zedd_D1abl0|Zedd_D1abl0]] || Jordan Keith || Australian || Living in Australia, waiting for consumer release<br />
|-<br />
|4. ||[[User:quatrox|quatrox]] || Flemming Richter Mikkelsen || Norwegian || waiting for developer release<br />
|-<br />
|5. ||[[User:Simarillion|Simarillion]] || Michael || German || already preordered<br />
|-<br />
|6. ||[[User:Trevi%C3%B1o|Treviño]] || Marco Trevisan || Italian || Just waiting for a mobile hacking platform!<br />
|-<br />
|7. ||[[User:CdnVapour150C|CdnVapour150C]] || Matt Crane || Canadian || Eagerly waiting GTA2 release<br />
|-<br />
|8. ||[[User:Mmanjos|mmanjos]] || Matt Manjos || Canadian || Living in Ottawa, going to buy the GTA02<br />
|-<br />
|9. ||[[User:bastian|bastian]] || Bastian Muck || German || Student (IT), waiting for shipment to buy one<br />
|-<br />
|10. ||[[User:dalnefre|dalnefre]] || Dale Schumacher || American || Why would editing this page make you trust me?<br />
|}<br />
<br />
==Other (Specify)==<br />
<br />
{| border="1"<br />
! !! Username !! Real name !! Nationality !! Remarks<br />
|-<br />
|1. ||[[User|User]] || || ||<br />
|}</div>Quicksandhttp://wiki.openmoko.org/wiki/Talk:OpkgTalk:Opkg2008-01-18T21:00:13Z<p>Quicksand: </p>
<hr />
<div>Thomas, I am watching with great interest your developments on opkg. Here are a few things I DETEST about ipkg, in case you are soliciting feature requests:<br />
<br />
* opkg should be smarter about non-default installation paths. ipkg-link works well enough most of the time, but when post-install scripts are run by ipkg, those scripts might be looking for files in /etc or /usr/share that don't exist because they aren't yet linked (user hasn't run ipkg-link yet).<br />
<br />
** on a related note, if installing a package also results in the installation of dependencies, opkg might be smarter about where it puts those (e.g., some system libraries in main flash, app libraries on card, etc.)<br />
<br />
** better still, maybe opkg.conf should allow different default locations for different types of packages, so I don't need to remember "-d card" every time<br />
<br />
* ipkg command-line options use a single dash for both one-letter options (e.g. "-d") and long options (e.g. "-force-reinstall"), contrary to nearly every other program in the world.<br />
<br />
* ipkg doesn't seem to handle very well the situation where one package is deprecated in favor of another that provides the same files/functions. I had some manual work to do when gtk+ package was dropped in favor of gtk+-fastscaling, for example.<br />
<br />
* better orphan handling would be nice!<br />
<br />
That's all. Good luck!<br />
<br />
[[User:Quicksand|Quicksand]] 22:00, 18 January 2008 (CET)</div>Quicksandhttp://wiki.openmoko.org/wiki/GllinGllin2008-01-14T21:58:33Z<p>Quicksand: </p>
<hr />
<div>gllin is an userpsace driver for a hammerhead [[GPS]] chip. It was distributed on phase1 openmokos.<br />
<br />
Thanks to a tremendous amount of hard work by many people, we have ready<br />
a release of gllin, the GPS drives. Here is how you can get it:<br />
<br />
http://3rdparty.downloads.openmoko.org/gllin/<br />
<br />
Instructions, how to use the driver, are give at:<br />
<br />
http://lists.openmoko.org/pipermail/community/2007-November/011916.html. <br />
<br />
The similar instructions are described in more details at [[getting GPS console output with gllin]].<br />
<br />
== gllin options ==<br />
<br />
The /home/root/gllin/gllin file installed by the new (legitimate!) .ipk package is really just a shell script. You can modify the options passed to gllin.real by editing that script. Here are the options:<br />
<pre><br />
Usage:<br />
<br />
-help Help<br />
-board <type> Defines board type Ex: '-board matchbox'<br />
supported: matchbox, trident<br />
-com <com port> GPS com port; Ex: '-com com6'<br />
-baud <baud rate> Set baud rate; Ex: '-baud 115200'<br />
-rft <RF type> Set RF type; Ex: '-rft RF_LN22OUT'<br />
-freq <freq plan> | ? set frequency plan for GPS or show the list of all available plans<br />
Ex: '-freq FRQ_PLAN_OCXO_10000'<br />
Ex: '-freq ?' -- Show all available plans<br />
-g <URL> SUPL Server URL or IP address;<br />
Ex: '-g 216.15.9.46'<br />
-p <port> SUPL Server port number;<br />
Ex: '-p 9118'<br />
-udp <port> Local UDP port to send NMEA to.<br />
'-udp 6000' [default]<br />
-gsm_cell <cell ID> set GSM Cell ID information<br />
cell ID has the following format: '<MCC>.<MNC>.<LAC>.<CI>'<br />
Where:<br />
MCC - Mobile Country Code<br />
MNC - Mobile Network Code<br />
LAC - Location Area Code<br />
CI - Cell Identification<br />
Ex: '-gsm_cell 310.170.367.25732'<br />
-set_assisted_off disable SET assisted capability<br />
-set_based_off disable SET based capability<br />
-msisdn <MSISDN> set value for MSISDN (international phone number) as SET id<br />
Ex: '-msisdn 14081234567'<br />
-nai <nai> specify Network Access Identifier as SET id<br />
Ex: '-nai 12345@mywebsite.com'<br />
-periodic <s> make periodic request every s second (-1 to 64)<br />
-1 single shot: perform one fix, then quit<br />
0 native: perform fixes as fast as possible<br />
<s> timed: report a position every <s> seconds<br />
where <s> is 1 to 64<br />
-recover recover GLLIN after signaled exit<br />
-low [<count>] low level test. Default <count> is 1<br />
-low_debug Low level debug ON<br />
+low_debug Low level debug OFF<br />
-train <count> Send train data <count> times<br />
+pty | -pty Enable or disable NMEA output to pty "/tmp/nmeaPTY"<br />
Default is off [-pty]<br />
+np | -np Enable or disable NMEA output to named pipe "/tmp/nmeaNP"<br />
Default is on [-np]<br />
+nmea | -nmea Enable or disable NMEA output to log file<br />
Default is off [-nmea]<br />
+daemon | -daemon Become a daemon (or not)<br />
Default is -daemon<br />
-a2 | -a3 | -a0 Select a GTA01 board revision. Default is a3<br />
-batch <st> <n> <fix> perform batch test of <n> starts of type <st><br />
<st> is hot, warm, cold, or SNR.<br />
Each start has <fix> fixes.<br />
-i start GLLIN command line<br />
+pnd optimize for PND<br />
-pnd look for low signal strength signals<br />
+sim using simulator so don't use almanac<br />
-sim not using simulator<br />
SNR manufacturing SNR test mode<br />
hot hot start [default]<br />
warm warm start<br />
cold cold start<br />
-v[n] Report GLLIN version string.<br />
n is 1234 to report selected versions.<br />
version 1.1.7<br />
</pre><br />
<br />
== Using gpsd with gllin ==<br />
<br />
edit /etc/default/gpsd and set the GPS_DEV to /tmp/nmeaNP start gpsd before gllin.<br />
<br />
== Some notes: ==<br />
<br />
The listed defaults don't seem to be correct. By default it DOES generate NMEA data in log files. These log files are on your flash (/home/root/gllin/log/*) and are written to once every second. Ridiculous!<br />
<br />
To stop this, add the option "-nmea" to the second of the two gllin.real commands in the startup script.<br />
<br />
But note further that the startup script also spawns a command to 'cat' the output of the /tmp/nmeaNP named pipe to a gzipped file in /home/root. If you want this to stop, you can do one of two things:<br />
<br />
* cat to /dev/null instead of | gzip >> file<br />
<br />
* add "-np" to the second gllin.real command<br />
<br />
You can't just take the 'cat' command out of the script, because with the named pipe activated, gllin will QUIT if it doesn't see anybody taking the output from the pipe. To keep it going, either open that pipe or turn it off.<br />
<br />
You can use this [http://obri.sygroup.ch/gllin gllin initscript] to start and stop gllin<br />
<br />
== More Initscripts ==<br />
<br />
The gllin package doesn't come with a very good set of initscripts, and gpsd is flexible enough to use gllin or some other source of GPS coordinates.<br />
<br />
For gpsd and gllin to run together well, upon boot, the following scripts have worked well for me:<br />
<br />
/etc/init.d/gpsd:<br />
<pre><br />
#!/bin/sh<br />
#<br />
# gpsd This shell script starts and stops gpsd.<br />
#<br />
# chkconfig: 345 90 40<br />
# description: Gpsd manages access to a serial- or USB-connected GPS<br />
# processname: gpsd<br />
<br />
# Source function library.<br />
#. /etc/rc.d/init.d/functions<br />
<br />
RETVAL=0<br />
prog="gpsd"<br />
<br />
test -f /etc/default/${prog} && . /etc/default/${prog}<br />
<br />
start() {<br />
# Start daemons.<br />
echo -n "Starting ${prog}: "<br />
# We don't use the daemon function here because of a known bug<br />
# in initlog -- it spuriously returns a nonzero status when <br />
# starting daemons that fork themselves. See<br />
# http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130629<br />
# for discussion. Fortunately:<br />
#<br />
# 1. gpsd startup can't fail, or at least not in the absence of<br />
# much larger resource-exhaustion problems that would be very obvious.<br />
#<br />
# 2. We don't need all the logging crud that daemon/initlog sets<br />
# up -- gpsd does its own syslog calls.<br />
#<br />
<br />
if [ -e "${GPS_DEV}" ]<br />
then<br />
${prog} -n ${GPSD_OPTS} ${GPS_DEV}<br />
RETVAL=$?<br />
echo "success"<br />
else<br />
# User needs to symlink ${GPS_DEV} to the right thing<br />
# Do it automatically if the name contains "NP"<br />
if echo ${GPS_DEV} | grep -q NP<br />
then<br />
mknod ${GPS_DEV} p<br />
${prog} -n ${GPSD_OPTS} ${GPS_DEV}<br />
RETVAL=$?<br />
echo "success"<br />
else<br />
RETVAL=$?<br />
echo "No ${GPS_DEV} GPS device, aborting gpsd startup. Check /etc/default/${prog}"<br />
fi<br />
fi<br />
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/gpsd<br />
return $RETVAL<br />
}<br />
<br />
stop() {<br />
# Stop daemons.<br />
echo -n "Shutting down ${prog}: "<br />
killall ${prog}<br />
RETVAL=$?<br />
echo<br />
if [ $RETVAL -eq 0 ]<br />
then<br />
test -e /var/lock/subsys/gpsd && rm -f /var/lock/subsys/gpsd;<br />
fi<br />
return $RETVAL<br />
}<br />
<br />
# See how we were called.<br />
case "$1" in<br />
start)<br />
start<br />
;;<br />
stop)<br />
stop<br />
;;<br />
restart|reload)<br />
stop<br />
start<br />
RETVAL=$?<br />
;;<br />
condrestart)<br />
if [ -f /var/lock/subsys/gpsd ]; then<br />
stop<br />
start<br />
RETVAL=$?<br />
fi<br />
;;<br />
status)<br />
# status gpsd<br />
# RETVAL=$?<br />
;;<br />
*)<br />
echo "Usage: $0 {start|stop|restart|condrestart|status}"<br />
exit 1<br />
esac<br />
<br />
exit $RETVAL<br />
</pre><br />
<br />
/etc/init.d/gllin:<br />
<pre><br />
#!/bin/sh<br />
#<br />
# This shell script starts and stops gllin.<br />
#<br />
<br />
RETVAL=0<br />
prog="gllin"<br />
GLLIN_PATH=/home/root/gllin<br />
<br />
test -f /etc/default/${prog} && . /etc/default/${prog}<br />
<br />
start() {<br />
# Make fifo if it doesn't already exist<br />
if [ ! -p /tmp/nmeaNP ]<br />
then<br />
mknod /tmp/nmeaNP p<br />
fi<br />
<br />
# Check for gpsd ready (max 5 seconds)<br />
echo -n "Waiting for gpsd . . . "<br />
sleep 1<br />
if [ ! "$(pidof gpsd)" ]<br />
then<br />
sleep 4<br />
if [ ! "$(pidof gpsd)" ]<br />
then<br />
RETVAL=1<br />
echo "failure."<br />
return $RETVAL<br />
fi<br />
fi<br />
<br />
# Start daemons.<br />
echo -n "starting ${prog}: "<br />
cd $GLLIN_PATH<br />
sleep 1<br />
if [ -e $GLLIN_PATH/${prog}.real ]<br />
then<br />
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog}.real -low 5 > /dev/null<br />
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog}.real -periodic 1 +daemon<br />
else<br />
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog} -low 5 > /dev/null<br />
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog} -periodic 1 +daemon<br />
fi<br />
echo "success."<br />
RETVAL=$?<br />
echo<br />
return $RETVAL<br />
}<br />
<br />
stop() {<br />
# Stop daemons.<br />
echo -n "Shutting down ${prog}: "<br />
pkill ld-linux.so.2 <br />
RETVAL=$?<br />
echo "success."<br />
return $RETVAL<br />
}<br />
<br />
# See how we were called.<br />
case "$1" in<br />
start)<br />
start<br />
;;<br />
stop)<br />
stop<br />
;;<br />
restart|reload)<br />
stop<br />
start<br />
RETVAL=$?<br />
;;<br />
status)<br />
# RETVAL=$?<br />
;;<br />
*)<br />
echo "Usage: $0 {start|stop|restart|condrestart|status}"<br />
exit 1<br />
esac<br />
<br />
exit $RETVAL<br />
</pre><br />
<br />
These scripts allow you (or init, if you have them numbered in rcX.d appropriately) to start gpsd *before* gllin. This way, gpsd starts listening on /tmp/nmeaNP immediately, and gllin doesn't need to send output to /dev/null in order to stay alive.<br />
<br />
This version of the gpsd script will create the named pipe (if the device name includes "NP" in the filename) if it doesn't exist.</div>Quicksandhttp://wiki.openmoko.org/wiki/GllinGllin2007-12-01T01:08:38Z<p>Quicksand: /* gllin options */</p>
<hr />
<div>gllin is an userpsace driver for a hammerhead chip. It was distributed on phase1 openmokos.<br />
<br />
Unfortunately, it is an OABI binary, and not even static one, so lots of stuff is needed for it to work. For security reasons, and for compatibility with EABI userland, it is probably best to run it in chroot. [[user:Zdanek|Zdanek's]] wrote an [http://www.openmoko.org.pl/node/55 article] how to put that together.<br />
<br />
__TOC__<br />
<br />
==The changeroot trick==<br />
<br />
Your chroot will need to contain following files:<br />
<br />
./dev<br /><br />
./dev/zero<br /><br />
./dev/ttySAC1<br /><br />
./etc<br /><br />
./etc/hosts<br /><br />
./etc/nsswitch.conf<br /><br />
./etc/host.conf<br /><br />
./lib<br /><br />
./lib/libm.so.6<br /><br />
./lib/libpthread-2.5.so<br /><br />
./lib/libnss_files.so.2<br /><br />
./lib/libnss_compat-2.5.so<br /><br />
./lib/libnss_mdns6_minimal.so.2<br /><br />
./lib/libanl-2.5.so<br /><br />
./lib/libgcc_s.so.1<br /><br />
./lib/libutil-2.5.so<br /><br />
./lib/libmemusage.so<br /><br />
./lib/libm-2.5.so<br /><br />
./lib/libc-2.5.so<br /><br />
./lib/libnss_mdns_minimal.so.2<br /><br />
./lib/libBrokenLocale.so.1<br /><br />
./lib/libnss_mdns4_minimal.so.2<br /><br />
./lib/libpthread.so.0<br /><br />
./lib/librt-2.5.so<br /><br />
./lib/libdl-2.5.so<br /><br />
./lib/libutil.so.1<br /><br />
./lib/libthread_db-1.0.so<br /><br />
./lib/libcrypt-2.5.so<br /><br />
./lib/libnss_compat.so.2<br /><br />
./lib/libnss_mdns4.so.2<br /><br />
./lib/libnss_mdns6.so.2<br /><br />
./lib/ld-2.5.so<br /><br />
./lib/libcidn.so.1<br /><br />
./lib/libthread_db.so.1<br /><br />
./lib/libnss_files-2.5.so<br /><br />
./lib/libanl.so.1<br /><br />
./lib/libcrypt.so.1<br /><br />
./lib/libnss_dns-2.5.so<br /><br />
./lib/ld-linux.so.2<br /><br />
./lib/libnss_mdns.so.2<br /><br />
./lib/libdl.so.2<br /><br />
./lib/libnss_dns.so.2<br /><br />
./lib/libc.so.6<br /><br />
./lib/librt.so.1<br /><br />
./lib/libcidn-2.5.so<br /><br />
./lib/libBrokenLocale-2.5.so<br /><br />
./log<br /><br />
./tmp<br /><br />
./tmp/nmeaNP<br /><br />
./usr<br /><br />
./usr/lib<br /><br />
./usr/lib/libstdc++.so.6<br /><br />
./usr/lib/libstdc++.so.6.0.8<br /><br />
./gllin<br /><br />
./sys<br /><br />
<br />
...and you"ll want to mount /sys there. Then, to get gps to work, do:<br />
<br />
root@fic-gta01:/chroot$ cat /chroot/tmp/nmeaNP &<br /><br />
root@fic-gta01:/chroot$ chroot /chroot/ gllin -low 1<br /><br />
root@fic-gta01:/chroot$ chroot /chroot/ gllin -periodic 1<br /><br />
<br />
More infos and tricks are here: [[Manually_using_GPS]].<br />
<br />
== gllin options ==<br />
<br />
The /home/root/gllin file installed by the new (legitimate!) .ipk package is really just a shell script. You can modify the options passed to gllin.real by editing that script. Here are the options:<br />
<pre><br />
Usage:<br />
<br />
-help Help<br />
-board <type> Defines board type Ex: '-board matchbox'<br />
supported: matchbox, trident<br />
-com <com port> GPS com port; Ex: '-com com6'<br />
-baud <baud rate> Set baud rate; Ex: '-baud 115200'<br />
-rft <RF type> Set RF type; Ex: '-rft RF_LN22OUT'<br />
-freq <freq plan> | ? set frequency plan for GPS or show the list of all available plans<br />
Ex: '-freq FRQ_PLAN_OCXO_10000'<br />
Ex: '-freq ?' -- Show all available plans<br />
-g <URL> SUPL Server URL or IP address;<br />
Ex: '-g 216.15.9.46'<br />
-p <port> SUPL Server port number;<br />
Ex: '-p 9118'<br />
-udp <port> Local UDP port to send NMEA to.<br />
'-udp 6000' [default]<br />
-gsm_cell <cell ID> set GSM Cell ID information<br />
cell ID has the following format: '<MCC>.<MNC>.<LAC>.<CI>'<br />
Where:<br />
MCC - Mobile Country Code<br />
MNC - Mobile Network Code<br />
LAC - Location Area Code<br />
CI - Cell Identification<br />
Ex: '-gsm_cell 310.170.367.25732'<br />
-set_assisted_off disable SET assisted capability<br />
-set_based_off disable SET based capability<br />
-msisdn <MSISDN> set value for MSISDN (international phone number) as SET id<br />
Ex: '-msisdn 14081234567'<br />
-nai <nai> specify Network Access Identifier as SET id<br />
Ex: '-nai 12345@mywebsite.com'<br />
-periodic <s> make periodic request every s second (-1 to 64)<br />
-1 single shot: perform one fix, then quit<br />
0 native: perform fixes as fast as possible<br />
<s> timed: report a position every <s> seconds<br />
where <s> is 1 to 64<br />
-recover recover GLLIN after signaled exit<br />
-low [<count>] low level test. Default <count> is 1<br />
-low_debug Low level debug ON<br />
+low_debug Low level debug OFF<br />
-train <count> Send train data <count> times<br />
+pty | -pty Enable or disable NMEA output to pty "/tmp/nmeaPTY"<br />
Default is off [-pty]<br />
+np | -np Enable or disable NMEA output to named pipe "/tmp/nmeaNP"<br />
Default is on [-np]<br />
+nmea | -nmea Enable or disable NMEA output to log file<br />
Default is off [-nmea]<br />
+daemon | -daemon Become a daemon (or not)<br />
Default is -daemon<br />
-a2 | -a3 | -a0 Select a GTA01 board revision. Default is a3<br />
-batch <st> <n> <fix> perform batch test of <n> starts of type <st><br />
<st> is hot, warm, cold, or SNR.<br />
Each start has <fix> fixes.<br />
-i start GLLIN command line<br />
+pnd optimize for PND<br />
-pnd look for low signal strength signals<br />
+sim using simulator so don't use almanac<br />
-sim not using simulator<br />
SNR manufacturing SNR test mode<br />
hot hot start [default]<br />
warm warm start<br />
cold cold start<br />
-v[n] Report GLLIN version string.<br />
n is 1234 to report selected versions.<br />
version 1.1.7<br />
</pre><br />
<br />
Some notes:<br />
<br />
The listed defaults don't seem to be correct. By default it DOES generate NMEA data in log files. These log files are on your flash (/home/root/gllin/log/*) and are written to once every second. Ridiculous!<br />
<br />
To stop this, add the option "-nmea" to the second of the two gllin.real commands in the startup script.<br />
<br />
But note further that the startup script also spawns a command to 'cat' the output of the /tmp/nmeaNP named pipe to a gzipped file in /home/root. If you want this to stop, you can do one of two things:<br />
<br />
* cat to /dev/null instead of | gzip >> file<br />
<br />
* add "-np" to the second gllin.real command<br />
<br />
You can't just take the 'cat' command out of the script, because with the named pipe activated, gllin will QUIT if it doesn't see anybody taking the output from the pipe. To keep it going, either open that pipe or turn it off.</div>Quicksandhttp://wiki.openmoko.org/wiki/GllinGllin2007-12-01T01:05:01Z<p>Quicksand: /* gllin options */</p>
<hr />
<div>gllin is an userpsace driver for a hammerhead chip. It was distributed on phase1 openmokos.<br />
<br />
Unfortunately, it is an OABI binary, and not even static one, so lots of stuff is needed for it to work. For security reasons, and for compatibility with EABI userland, it is probably best to run it in chroot. [[user:Zdanek|Zdanek's]] wrote an [http://www.openmoko.org.pl/node/55 article] how to put that together.<br />
<br />
__TOC__<br />
<br />
==The changeroot trick==<br />
<br />
Your chroot will need to contain following files:<br />
<br />
./dev<br /><br />
./dev/zero<br /><br />
./dev/ttySAC1<br /><br />
./etc<br /><br />
./etc/hosts<br /><br />
./etc/nsswitch.conf<br /><br />
./etc/host.conf<br /><br />
./lib<br /><br />
./lib/libm.so.6<br /><br />
./lib/libpthread-2.5.so<br /><br />
./lib/libnss_files.so.2<br /><br />
./lib/libnss_compat-2.5.so<br /><br />
./lib/libnss_mdns6_minimal.so.2<br /><br />
./lib/libanl-2.5.so<br /><br />
./lib/libgcc_s.so.1<br /><br />
./lib/libutil-2.5.so<br /><br />
./lib/libmemusage.so<br /><br />
./lib/libm-2.5.so<br /><br />
./lib/libc-2.5.so<br /><br />
./lib/libnss_mdns_minimal.so.2<br /><br />
./lib/libBrokenLocale.so.1<br /><br />
./lib/libnss_mdns4_minimal.so.2<br /><br />
./lib/libpthread.so.0<br /><br />
./lib/librt-2.5.so<br /><br />
./lib/libdl-2.5.so<br /><br />
./lib/libutil.so.1<br /><br />
./lib/libthread_db-1.0.so<br /><br />
./lib/libcrypt-2.5.so<br /><br />
./lib/libnss_compat.so.2<br /><br />
./lib/libnss_mdns4.so.2<br /><br />
./lib/libnss_mdns6.so.2<br /><br />
./lib/ld-2.5.so<br /><br />
./lib/libcidn.so.1<br /><br />
./lib/libthread_db.so.1<br /><br />
./lib/libnss_files-2.5.so<br /><br />
./lib/libanl.so.1<br /><br />
./lib/libcrypt.so.1<br /><br />
./lib/libnss_dns-2.5.so<br /><br />
./lib/ld-linux.so.2<br /><br />
./lib/libnss_mdns.so.2<br /><br />
./lib/libdl.so.2<br /><br />
./lib/libnss_dns.so.2<br /><br />
./lib/libc.so.6<br /><br />
./lib/librt.so.1<br /><br />
./lib/libcidn-2.5.so<br /><br />
./lib/libBrokenLocale-2.5.so<br /><br />
./log<br /><br />
./tmp<br /><br />
./tmp/nmeaNP<br /><br />
./usr<br /><br />
./usr/lib<br /><br />
./usr/lib/libstdc++.so.6<br /><br />
./usr/lib/libstdc++.so.6.0.8<br /><br />
./gllin<br /><br />
./sys<br /><br />
<br />
...and you"ll want to mount /sys there. Then, to get gps to work, do:<br />
<br />
root@fic-gta01:/chroot$ cat /chroot/tmp/nmeaNP &<br /><br />
root@fic-gta01:/chroot$ chroot /chroot/ gllin -low 1<br /><br />
root@fic-gta01:/chroot$ chroot /chroot/ gllin -periodic 1<br /><br />
<br />
More infos and tricks are here: [[Manually_using_GPS]].<br />
<br />
== gllin options ==<br />
<br />
The /home/root/gllin file installed by the new (legitimate!) .ipk package is really just a shell script. You can modify the options passed to gllin.real by editing that script. Here are the options:<br />
<pre><br />
Usage:<br />
<br />
-help Help<br />
-board <type> Defines board type Ex: '-board matchbox'<br />
supported: matchbox, trident<br />
-com <com port> GPS com port; Ex: '-com com6'<br />
-baud <baud rate> Set baud rate; Ex: '-baud 115200'<br />
-rft <RF type> Set RF type; Ex: '-rft RF_LN22OUT'<br />
-freq <freq plan> | ? set frequency plan for GPS or show the list of all available plans<br />
Ex: '-freq FRQ_PLAN_OCXO_10000'<br />
Ex: '-freq ?' -- Show all available plans<br />
-g <URL> SUPL Server URL or IP address;<br />
Ex: '-g 216.15.9.46'<br />
-p <port> SUPL Server port number;<br />
Ex: '-p 9118'<br />
-udp <port> Local UDP port to send NMEA to.<br />
'-udp 6000' [default]<br />
-gsm_cell <cell ID> set GSM Cell ID information<br />
cell ID has the following format: '<MCC>.<MNC>.<LAC>.<CI>'<br />
Where:<br />
MCC - Mobile Country Code<br />
MNC - Mobile Network Code<br />
LAC - Location Area Code<br />
CI - Cell Identification<br />
Ex: '-gsm_cell 310.170.367.25732'<br />
-set_assisted_off disable SET assisted capability<br />
-set_based_off disable SET based capability<br />
-msisdn <MSISDN> set value for MSISDN (international phone number) as SET id<br />
Ex: '-msisdn 14081234567'<br />
-nai <nai> specify Network Access Identifier as SET id<br />
Ex: '-nai 12345@mywebsite.com'<br />
-periodic <s> make periodic request every s second (-1 to 64)<br />
-1 single shot: perform one fix, then quit<br />
0 native: perform fixes as fast as possible<br />
<s> timed: report a position every <s> seconds<br />
where <s> is 1 to 64<br />
-recover recover GLLIN after signaled exit<br />
-low [<count>] low level test. Default <count> is 1<br />
-low_debug Low level debug ON<br />
+low_debug Low level debug OFF<br />
-train <count> Send train data <count> times<br />
+pty | -pty Enable or disable NMEA output to pty "/tmp/nmeaPTY"<br />
Default is off [-pty]<br />
+np | -np Enable or disable NMEA output to named pipe "/tmp/nmeaNP"<br />
Default is on [-np]<br />
+nmea | -nmea Enable or disable NMEA output to log file<br />
Default is off [-nmea]<br />
+daemon | -daemon Become a daemon (or not)<br />
Default is -daemon<br />
-a2 | -a3 | -a0 Select a GTA01 board revision. Default is a3<br />
-batch <st> <n> <fix> perform batch test of <n> starts of type <st><br />
<st> is hot, warm, cold, or SNR.<br />
Each start has <fix> fixes.<br />
-i start GLLIN command line<br />
+pnd optimize for PND<br />
-pnd look for low signal strength signals<br />
+sim using simulator so don't use almanac<br />
-sim not using simulator<br />
SNR manufacturing SNR test mode<br />
hot hot start [default]<br />
warm warm start<br />
cold cold start<br />
-v[n] Report GLLIN version string.<br />
n is 1234 to report selected versions.<br />
version 1.1.7<br />
</pre><br />
<br />
Some notes:<br />
<br />
The listed defaults don't seem to be correct. By default it DOES generate NMEA data in log files. These log files are on your flash (/home/root/gllin/log/*) and are written to once every second. Ridiculous!<br />
<br />
To stop this, add the option "-nmea" to the second of the two gllin.real commands in the startup script.<br />
<br />
But note further that the startup script also spawns a command to cat the output of the /tmp/nmeaNP named pipe to a gzipped file in /home/root. If you want this to stop, you can do one of two things:<br />
<br />
* cat to /dev/null instead of | gzip >> file<br />
<br />
* add "-np" to the second gllin.real command<br />
<br />
You can't just take the cat out of the script, because with the named pipe activated, gllin will QUIT if it doesn't see anybody taking the output from the pipe. To keep it going, either open that pipe or turn it off.</div>Quicksandhttp://wiki.openmoko.org/wiki/GllinGllin2007-11-30T23:30:23Z<p>Quicksand: </p>
<hr />
<div>gllin is an userpsace driver for a hammerhead chip. It was distributed on phase1 openmokos.<br />
<br />
Unfortunately, it is an OABI binary, and not even static one, so lots of stuff is needed for it to work. For security reasons, and for compatibility with EABI userland, it is probably best to run it in chroot. [[user:Zdanek|Zdanek's]] wrote an [http://www.openmoko.org.pl/node/55 article] how to put that together.<br />
<br />
__TOC__<br />
<br />
==The changeroot trick==<br />
<br />
Your chroot will need to contain following files:<br />
<br />
./dev<br /><br />
./dev/zero<br /><br />
./dev/ttySAC1<br /><br />
./etc<br /><br />
./etc/hosts<br /><br />
./etc/nsswitch.conf<br /><br />
./etc/host.conf<br /><br />
./lib<br /><br />
./lib/libm.so.6<br /><br />
./lib/libpthread-2.5.so<br /><br />
./lib/libnss_files.so.2<br /><br />
./lib/libnss_compat-2.5.so<br /><br />
./lib/libnss_mdns6_minimal.so.2<br /><br />
./lib/libanl-2.5.so<br /><br />
./lib/libgcc_s.so.1<br /><br />
./lib/libutil-2.5.so<br /><br />
./lib/libmemusage.so<br /><br />
./lib/libm-2.5.so<br /><br />
./lib/libc-2.5.so<br /><br />
./lib/libnss_mdns_minimal.so.2<br /><br />
./lib/libBrokenLocale.so.1<br /><br />
./lib/libnss_mdns4_minimal.so.2<br /><br />
./lib/libpthread.so.0<br /><br />
./lib/librt-2.5.so<br /><br />
./lib/libdl-2.5.so<br /><br />
./lib/libutil.so.1<br /><br />
./lib/libthread_db-1.0.so<br /><br />
./lib/libcrypt-2.5.so<br /><br />
./lib/libnss_compat.so.2<br /><br />
./lib/libnss_mdns4.so.2<br /><br />
./lib/libnss_mdns6.so.2<br /><br />
./lib/ld-2.5.so<br /><br />
./lib/libcidn.so.1<br /><br />
./lib/libthread_db.so.1<br /><br />
./lib/libnss_files-2.5.so<br /><br />
./lib/libanl.so.1<br /><br />
./lib/libcrypt.so.1<br /><br />
./lib/libnss_dns-2.5.so<br /><br />
./lib/ld-linux.so.2<br /><br />
./lib/libnss_mdns.so.2<br /><br />
./lib/libdl.so.2<br /><br />
./lib/libnss_dns.so.2<br /><br />
./lib/libc.so.6<br /><br />
./lib/librt.so.1<br /><br />
./lib/libcidn-2.5.so<br /><br />
./lib/libBrokenLocale-2.5.so<br /><br />
./log<br /><br />
./tmp<br /><br />
./tmp/nmeaNP<br /><br />
./usr<br /><br />
./usr/lib<br /><br />
./usr/lib/libstdc++.so.6<br /><br />
./usr/lib/libstdc++.so.6.0.8<br /><br />
./gllin<br /><br />
./sys<br /><br />
<br />
...and you"ll want to mount /sys there. Then, to get gps to work, do:<br />
<br />
root@fic-gta01:/chroot$ cat /chroot/tmp/nmeaNP &<br /><br />
root@fic-gta01:/chroot$ chroot /chroot/ gllin -low 1<br /><br />
root@fic-gta01:/chroot$ chroot /chroot/ gllin -periodic 1<br /><br />
<br />
More infos and tricks are here: [[Manually_using_GPS]].<br />
<br />
== gllin options ==<br />
<br />
The /home/root/gllin file installed by the new (legitimate!) .ipk package is really just a shell script. You can modify the options passed to gllin.real by editing that script. Here are the options:<br />
<pre><br />
Usage:<br />
<br />
-help Help<br />
-board <type> Defines board type Ex: '-board matchbox'<br />
supported: matchbox, trident<br />
-com <com port> GPS com port; Ex: '-com com6'<br />
-baud <baud rate> Set baud rate; Ex: '-baud 115200'<br />
-rft <RF type> Set RF type; Ex: '-rft RF_LN22OUT'<br />
-freq <freq plan> | ? set frequency plan for GPS or show the list of all available plans<br />
Ex: '-freq FRQ_PLAN_OCXO_10000'<br />
Ex: '-freq ?' -- Show all available plans<br />
-g <URL> SUPL Server URL or IP address;<br />
Ex: '-g 216.15.9.46'<br />
-p <port> SUPL Server port number;<br />
Ex: '-p 9118'<br />
-udp <port> Local UDP port to send NMEA to.<br />
'-udp 6000' [default]<br />
-gsm_cell <cell ID> set GSM Cell ID information<br />
cell ID has the following format: '<MCC>.<MNC>.<LAC>.<CI>'<br />
Where:<br />
MCC - Mobile Country Code<br />
MNC - Mobile Network Code<br />
LAC - Location Area Code<br />
CI - Cell Identification<br />
Ex: '-gsm_cell 310.170.367.25732'<br />
-set_assisted_off disable SET assisted capability<br />
-set_based_off disable SET based capability<br />
-msisdn <MSISDN> set value for MSISDN (international phone number) as SET id<br />
Ex: '-msisdn 14081234567'<br />
-nai <nai> specify Network Access Identifier as SET id<br />
Ex: '-nai 12345@mywebsite.com'<br />
-periodic <s> make periodic request every s second (-1 to 64)<br />
-1 single shot: perform one fix, then quit<br />
0 native: perform fixes as fast as possible<br />
<s> timed: report a position every <s> seconds<br />
where <s> is 1 to 64<br />
-recover recover GLLIN after signaled exit<br />
-low [<count>] low level test. Default <count> is 1<br />
-low_debug Low level debug ON<br />
+low_debug Low level debug OFF<br />
-train <count> Send train data <count> times<br />
+pty | -pty Enable or disable NMEA output to pty "/tmp/nmeaPTY"<br />
Default is off [-pty]<br />
+np | -np Enable or disable NMEA output to named pipe "/tmp/nmeaNP"<br />
Default is on [-np]<br />
+nmea | -nmea Enable or disable NMEA output to log file<br />
Default is off [-nmea]<br />
+daemon | -daemon Become a daemon (or not)<br />
Default is -daemon<br />
-a2 | -a3 | -a0 Select a GTA01 board revision. Default is a3<br />
-batch <st> <n> <fix> perform batch test of <n> starts of type <st><br />
<st> is hot, warm, cold, or SNR.<br />
Each start has <fix> fixes.<br />
-i start GLLIN command line<br />
+pnd optimize for PND<br />
-pnd look for low signal strength signals<br />
+sim using simulator so don't use almanac<br />
-sim not using simulator<br />
SNR manufacturing SNR test mode<br />
hot hot start [default]<br />
warm warm start<br />
cold cold start<br />
-v[n] Report GLLIN version string.<br />
n is 1234 to report selected versions.<br />
version 1.1.7<br />
</pre></div>Quicksandhttp://wiki.openmoko.org/wiki/GllinGllin2007-11-30T23:26:59Z<p>Quicksand: </p>
<hr />
<div>gllin is an userpsace driver for a hammerhead chip. It was distributed on phase1 openmokos.<br />
<br />
Unfortunately, it is an OABI binary, and not even static one, so lots of stuff is needed for it to work. For security reasons, and for compatibility with EABI userland, it is probably best to run it in chroot. [[user:Zdanek|Zdanek's]] wrote an [http://www.openmoko.org.pl/node/55 article] how to put that together.<br />
<br />
==The changeroot trick==<br />
<br />
Your chroot will need to contain following files:<br />
<br />
./dev<br /><br />
./dev/zero<br /><br />
./dev/ttySAC1<br /><br />
./etc<br /><br />
./etc/hosts<br /><br />
./etc/nsswitch.conf<br /><br />
./etc/host.conf<br /><br />
./lib<br /><br />
./lib/libm.so.6<br /><br />
./lib/libpthread-2.5.so<br /><br />
./lib/libnss_files.so.2<br /><br />
./lib/libnss_compat-2.5.so<br /><br />
./lib/libnss_mdns6_minimal.so.2<br /><br />
./lib/libanl-2.5.so<br /><br />
./lib/libgcc_s.so.1<br /><br />
./lib/libutil-2.5.so<br /><br />
./lib/libmemusage.so<br /><br />
./lib/libm-2.5.so<br /><br />
./lib/libc-2.5.so<br /><br />
./lib/libnss_mdns_minimal.so.2<br /><br />
./lib/libBrokenLocale.so.1<br /><br />
./lib/libnss_mdns4_minimal.so.2<br /><br />
./lib/libpthread.so.0<br /><br />
./lib/librt-2.5.so<br /><br />
./lib/libdl-2.5.so<br /><br />
./lib/libutil.so.1<br /><br />
./lib/libthread_db-1.0.so<br /><br />
./lib/libcrypt-2.5.so<br /><br />
./lib/libnss_compat.so.2<br /><br />
./lib/libnss_mdns4.so.2<br /><br />
./lib/libnss_mdns6.so.2<br /><br />
./lib/ld-2.5.so<br /><br />
./lib/libcidn.so.1<br /><br />
./lib/libthread_db.so.1<br /><br />
./lib/libnss_files-2.5.so<br /><br />
./lib/libanl.so.1<br /><br />
./lib/libcrypt.so.1<br /><br />
./lib/libnss_dns-2.5.so<br /><br />
./lib/ld-linux.so.2<br /><br />
./lib/libnss_mdns.so.2<br /><br />
./lib/libdl.so.2<br /><br />
./lib/libnss_dns.so.2<br /><br />
./lib/libc.so.6<br /><br />
./lib/librt.so.1<br /><br />
./lib/libcidn-2.5.so<br /><br />
./lib/libBrokenLocale-2.5.so<br /><br />
./log<br /><br />
./tmp<br /><br />
./tmp/nmeaNP<br /><br />
./usr<br /><br />
./usr/lib<br /><br />
./usr/lib/libstdc++.so.6<br /><br />
./usr/lib/libstdc++.so.6.0.8<br /><br />
./gllin<br /><br />
./sys<br /><br />
<br />
...and you"ll want to mount /sys there. Then, to get gps to work, do:<br />
<br />
root@fic-gta01:/chroot$ cat /chroot/tmp/nmeaNP &<br /><br />
root@fic-gta01:/chroot$ chroot /chroot/ gllin -low 1<br /><br />
root@fic-gta01:/chroot$ chroot /chroot/ gllin -periodic 1<br /><br />
<br />
More infos and tricks are here: [[Manually_using_GPS]].<br />
<br />
== gllin options ==<br />
<br />
The /home/root/gllin file installed by the new (legitimate!) .ipk package is really just a shell script. You can modify the options passed to gllin.real by editing that script. Here are the options:<br />
<pre><br />
Usage:<br />
<br />
-help Help<br />
-board <type> Defines board type Ex: '-board matchbox'<br />
supported: matchbox, trident<br />
-com <com port> GPS com port; Ex: '-com com6'<br />
-baud <baud rate> Set baud rate; Ex: '-baud 115200'<br />
-rft <RF type> Set RF type; Ex: '-rft RF_LN22OUT'<br />
-freq <freq plan> | ? set frequency plan for GPS or show the list of all available plans<br />
Ex: '-freq FRQ_PLAN_OCXO_10000'<br />
Ex: '-freq ?' -- Show all available plans<br />
-g <URL> SUPL Server URL or IP address;<br />
Ex: '-g 216.15.9.46'<br />
-p <port> SUPL Server port number;<br />
Ex: '-p 9118'<br />
-udp <port> Local UDP port to send NMEA to.<br />
'-udp 6000' [default]<br />
-gsm_cell <cell ID> set GSM Cell ID information<br />
cell ID has the following format: '<MCC>.<MNC>.<LAC>.<CI>'<br />
Where:<br />
MCC - Mobile Country Code<br />
MNC - Mobile Network Code<br />
LAC - Location Area Code<br />
CI - Cell Identification<br />
Ex: '-gsm_cell 310.170.367.25732'<br />
-set_assisted_off disable SET assisted capability<br />
-set_based_off disable SET based capability<br />
-msisdn <MSISDN> set value for MSISDN (international phone number) as SET id<br />
Ex: '-msisdn 14081234567'<br />
-nai <nai> specify Network Access Identifier as SET id<br />
Ex: '-nai 12345@mywebsite.com'<br />
-periodic <s> make periodic request every s second (-1 to 64)<br />
-1 single shot: perform one fix, then quit<br />
0 native: perform fixes as fast as possible<br />
<s> timed: report a position every <s> seconds<br />
where <s> is 1 to 64<br />
-recover recover GLLIN after signaled exit<br />
-low [<count>] low level test. Default <count> is 1<br />
-low_debug Low level debug ON<br />
+low_debug Low level debug OFF<br />
-train <count> Send train data <count> times<br />
+pty | -pty Enable or disable NMEA output to pty "/tmp/nmeaPTY"<br />
Default is off [-pty]<br />
+np | -np Enable or disable NMEA output to named pipe "/tmp/nmeaNP"<br />
Default is on [-np]<br />
+nmea | -nmea Enable or disable NMEA output to log file<br />
Default is off [-nmea]<br />
+daemon | -daemon Become a daemon (or not)<br />
Default is -daemon<br />
-a2 | -a3 | -a0 Select a GTA01 board revision. Default is a3<br />
-batch <st> <n> <fix> perform batch test of <n> starts of type <st><br />
<st> is hot, warm, cold, or SNR.<br />
Each start has <fix> fixes.<br />
-i start GLLIN command line<br />
+pnd optimize for PND<br />
-pnd look for low signal strength signals<br />
+sim using simulator so don't use almanac<br />
-sim not using simulator<br />
SNR manufacturing SNR test mode<br />
hot hot start [default]<br />
warm warm start<br />
cold cold start<br />
-v[n] Report GLLIN version string.<br />
n is 1234 to report selected versions.<br />
version 1.1.7<br />
</pre></div>Quicksandhttp://wiki.openmoko.org/wiki/Talk:Display_LockerTalk:Display Locker2007-11-27T20:32:55Z<p>Quicksand: </p>
<hr />
<div>Well borg, you beat me to something that actually works!<br />
<br />
If you haven't seen it yet, check out my python prototype of a screen lock program:<br />
<br />
http://wiki.openmoko.org/wiki/User:Quicksand#zedlock<br />
<br />
I put this up a few weeks ago. It's intended to be less visual, more tactile/kinetic (i.e., easy to use without looking). I want the locked screen to have information on it eventually, but I haven't gotten around to recoding it in C (with dbus, etc.) in part because neod seemed like kind of a dead-end.<br />
<br />
Perhaps some collaboration is in order? I'd LOVE to see a combination graphical unlocker with dbus interfaces to useful info (voicemails, SMSes, GPRS state, etc.) that is both tactile/kinetic and attractive.<br />
<br />
--Quicksand</div>Quicksandhttp://wiki.openmoko.org/wiki/Talk:Display_LockerTalk:Display Locker2007-11-27T19:17:04Z<p>Quicksand: </p>
<hr />
<div>Well borg, you beat me to something that actually works!<br />
<br />
If you haven't seen it yet, check out my python prototype of a screen lock program:<br />
<br />
http://wiki.openmoko.org/wiki/User:Quicksand#zedlock<br />
<br />
I put this up a few weeks ago. It's intended to be less visual, more kinetic (i.e., easy to use without looking). I want the locked screen to have information on it eventually, but I haven't gotten around to recoding it in C (with dbus, etc.) in part because neod seemed like kind of a dead-end.<br />
<br />
Perhaps some collaboration is in order? I'd LOVE to see a combination graphical unlocker with dbus interfaces to useful info (voicemails, SMSes, GPRS state, etc.) that is both kinetic and attractive.<br />
<br />
--Quicksand</div>Quicksandhttp://wiki.openmoko.org/wiki/Talk:Display_LockerTalk:Display Locker2007-11-27T19:16:41Z<p>Quicksand: </p>
<hr />
<div>Well borg, you beat me to something that actually works!<br />
<br />
If you haven't seen it yet, check out my python prototype of a screen lock program:<br />
<br />
http://wiki.openmoko.org/wiki/User:Quicksand#zedlock<br />
<br />
I put this up a few weeks ago. It's intended to be less visual, more kinetic (i.e., easy to use without looking). I want the locked screen to have information on it eventually, but I haven't gotten around to recoding it in C (with dbus, etc.) in part because neod seemed like kind of a dead-end.<br />
<br />
Perhaps some collaboration is in order? I'd LOVE to see a combination graphical unlocker with dbus interfaces to useful info (voicemails, SMSes, GPRS state, etc.) that is both kinetic and attractive.</div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-10-11T22:29:43Z<p>Quicksand: /* Xournal */</p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at [http://www.wixonlaw.com wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
=== zedlock ===<br />
<br />
Screen locking program. Currently in PROTOTYPE form.<br />
<br />
Download [http://wixonlaw.com/public/zedlock-0.0.1.tar.bz2 zedlock 0.0.1]<br />
<br />
[[Image:Zedlock-screenshot-1.png]]<br />
<br />
'''How it works'''<br />
<br />
This is a screen-lock program in prototype form. To run it, just run zedlock.py from a terminal in the directory where it's installed.<br />
<br />
It's really simple. To unlock, just trace a large 'Z' with a single stroke of your finger or stylus, anywhere on the screen. It must be BIG ENOUGH (about half the smallest screen dimension in both height and width, approx. 2cm on the Neo), it must be drawn in the CORRECT SEQUENCE (from top-left to bottom-right), and it must be QUICK ENOUGH (completed in less than one second). Within these parameters, a fair amount of variation (i.e., sloppiness) is tolerated. (As a result, you can make some non-Z patterns that fool it.)<br />
<br />
'''Who's Zed?'''<br />
<br />
Zed's dead, baby, Zed's dead.<br />
<br />
'''No, really, why Zed?'''<br />
<br />
There are a bunch of things out there already called "zlock" or the like. I selected the 'Z' glyph because it's fast and easy to make without looking, and its four points are easy to pull out of a stream of touchscreen data -- they are simply the maxima and minima of the functions (x+y) and (x-y). I don't need to keep a linked list of intermediate points or anything like that; these points are updated on-the-fly.<br />
<br />
'''Why would I want this?'''<br />
<br />
You don't need to be looking at the screen to unlock it. It is pretty unlikely to unlock accidentally (by your face while you are on the phone, in your pocket, etc.). But it's simple and fast enough to perform frequently and easily, and to become second-nature.<br />
<br />
Plus it looks nice: gtk+ and cairo are used for fluid anti-aliased graphics. Visual feedback is provided after a stroke is completed: an openmoko-orange line shows where you made your stroke, and if it finds the 'Z' pattern, it is highlighted in white for a moment. <br />
<br />
Success:<br />
<br />
[[Image:Zedlock-screenshot-2.png]]<br />
<br />
If your stroke doesn't meet the criteria, you get a big red 'X' on the screen and a three-second lockout.<br />
<br />
Too small:<br />
<br />
[[Image:Zedlock-screenshot-3.png]]<br />
<br />
Wrong sequence:<br />
<br />
[[Image:Zedlock-screenshot-4.png]]<br />
<br />
With the iPhone and the Qtopia phone platform, you need to be looking at the touchscreen to unlock it. Their sliders and animated keys are cool, but this is better.<br />
<br />
'''Remember, this is a prototype'''<br />
<br />
To install it, copy zedlock.py and zedlock.png to your home directory (or a subdirectory), make sure zedlock.py is executable, and run it from the directory you installed it in. The program depends on python-pygtk and python-pycairo. Note that it doesn't actually do anything all that functional yet -- it is simply a demonstration program. This prototype doesn't actually lock or unlock anything; it just clears the screen after each stroke (and the subsequent visual feedback) so you can try it again and again and again.<br />
<br />
The program should be more-or-less QVGA-friendly (well, almost, just change two global variables) and orientation-friendly already, but YMMV.<br />
<br />
Yes, it's slow, especially to start up. But that's embedded python for ya. Plus I had to do some weird hacky things in cairo to get it to render predictably. This is my first cairo project and my first python program, SO DON'T GIVE ME ANY GRIEF! There are probably terrible, ugly, spaghetti-code-monsters in there if you care to look. They'll go away over time. :)<br />
<br />
'''Future Plans'''<br />
<br />
After the featureset solidifies a bit more, I will rewrite it in C (which I'm much more comfortable with), optimize it (a lot!), and add some features:<br />
<br />
'''1)''' It will be rotationally insensitive so you don't need to look at it to determine portrait vs. landscape before you unlock. This will be pretty easy to add.<br />
<br />
'''2)''' The text on there is statically-coded right now, and fixing that will be trivial, so don't complain about it now. It doesn't actually tell you the GSM/GPRS status or even the real time of day. Yes, wise guy, IT'S ALWAYS 5:35 pm HERE.<br />
<br />
'''3)''' Eventually it will get a battery/charging state icon, GSM signal strength bars, and a ringer volume indicator, so you can see those things while the screen remains locked. I don't want to make the interface too cluttered, but those items seem essential.<br />
<br />
'''4)''' Ideally this will slip right into the OpenMoko power management scheme. Preferably neod and/or the dialer will *lock* the screen and require an unlock program (such as zedlock) in the following circumstances:<br />
<br />
* immediately after an incoming call is answered<br />
(to prevent touchscreen input from the user's face or ear)<br />
<br />
* immediately after an outgoing call is dialed<br />
(ditto)<br />
<br />
* on request<br />
(via a lock button or menu, before you put it in your pocket)<br />
<br />
* upon an automatic return-from-suspend<br />
(e.g., a datebook alarm, incoming phone call, SMS, etc.)<br />
<br />
* but *not* following a manual return-from-suspend<br />
<br />
Note that this concept of screen-lock is different from the power-management concept of screen blanking. Screen LOCK should probably occur more often, and is intended primarily to prevent accidental user-interface manipulation while the touchscreen is against the user's face, in the user's pocket, or otherwise subject to spurious inputs. It is not intended to save power.<br />
<br />
=== Password Safe ===<br />
<br />
Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives. KeePassX compiles successfully but never opens a window on the Neo, and I'm not sure why -- other QT applications seem to work fine.<br />
<br />
=== Xournal ===<br />
<br />
[http://xournal.sourceforge.net Xournal] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
== Finished Projects ==<br />
<br />
=== Free42 ===<br />
<br />
[http://home.planet.nl/~demun000/thomas_projects/free42/ Free42] is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
[[Image:Image-free42.jpg]]<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo.<br />
<br />
It's now available in the OE repository. The package name is free42-vga<br />
<br />
=== Notecase ===<br />
<br />
[http://notecase.sourceforge.net Notecase] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. I have uploaded a .bb file and patch for the latest version (1.6.6) to the OE bugtracker.<br />
<br />
== Future Projects ==<br />
<br />
=== Handwriting Recognition ===<br />
<br />
Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
=== Music Platform ===<br />
<br />
I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-10-11T22:27:38Z<p>Quicksand: </p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at [http://www.wixonlaw.com wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
=== zedlock ===<br />
<br />
Screen locking program. Currently in PROTOTYPE form.<br />
<br />
Download [http://wixonlaw.com/public/zedlock-0.0.1.tar.bz2 zedlock 0.0.1]<br />
<br />
[[Image:Zedlock-screenshot-1.png]]<br />
<br />
'''How it works'''<br />
<br />
This is a screen-lock program in prototype form. To run it, just run zedlock.py from a terminal in the directory where it's installed.<br />
<br />
It's really simple. To unlock, just trace a large 'Z' with a single stroke of your finger or stylus, anywhere on the screen. It must be BIG ENOUGH (about half the smallest screen dimension in both height and width, approx. 2cm on the Neo), it must be drawn in the CORRECT SEQUENCE (from top-left to bottom-right), and it must be QUICK ENOUGH (completed in less than one second). Within these parameters, a fair amount of variation (i.e., sloppiness) is tolerated. (As a result, you can make some non-Z patterns that fool it.)<br />
<br />
'''Who's Zed?'''<br />
<br />
Zed's dead, baby, Zed's dead.<br />
<br />
'''No, really, why Zed?'''<br />
<br />
There are a bunch of things out there already called "zlock" or the like. I selected the 'Z' glyph because it's fast and easy to make without looking, and its four points are easy to pull out of a stream of touchscreen data -- they are simply the maxima and minima of the functions (x+y) and (x-y). I don't need to keep a linked list of intermediate points or anything like that; these points are updated on-the-fly.<br />
<br />
'''Why would I want this?'''<br />
<br />
You don't need to be looking at the screen to unlock it. It is pretty unlikely to unlock accidentally (by your face while you are on the phone, in your pocket, etc.). But it's simple and fast enough to perform frequently and easily, and to become second-nature.<br />
<br />
Plus it looks nice: gtk+ and cairo are used for fluid anti-aliased graphics. Visual feedback is provided after a stroke is completed: an openmoko-orange line shows where you made your stroke, and if it finds the 'Z' pattern, it is highlighted in white for a moment. <br />
<br />
Success:<br />
<br />
[[Image:Zedlock-screenshot-2.png]]<br />
<br />
If your stroke doesn't meet the criteria, you get a big red 'X' on the screen and a three-second lockout.<br />
<br />
Too small:<br />
<br />
[[Image:Zedlock-screenshot-3.png]]<br />
<br />
Wrong sequence:<br />
<br />
[[Image:Zedlock-screenshot-4.png]]<br />
<br />
With the iPhone and the Qtopia phone platform, you need to be looking at the touchscreen to unlock it. Their sliders and animated keys are cool, but this is better.<br />
<br />
'''Remember, this is a prototype'''<br />
<br />
To install it, copy zedlock.py and zedlock.png to your home directory (or a subdirectory), make sure zedlock.py is executable, and run it from the directory you installed it in. The program depends on python-pygtk and python-pycairo. Note that it doesn't actually do anything all that functional yet -- it is simply a demonstration program. This prototype doesn't actually lock or unlock anything; it just clears the screen after each stroke (and the subsequent visual feedback) so you can try it again and again and again.<br />
<br />
The program should be more-or-less QVGA-friendly (well, almost, just change two global variables) and orientation-friendly already, but YMMV.<br />
<br />
Yes, it's slow, especially to start up. But that's embedded python for ya. Plus I had to do some weird hacky things in cairo to get it to render predictably. This is my first cairo project and my first python program, SO DON'T GIVE ME ANY GRIEF! There are probably terrible, ugly, spaghetti-code-monsters in there if you care to look. They'll go away over time. :)<br />
<br />
'''Future Plans'''<br />
<br />
After the featureset solidifies a bit more, I will rewrite it in C (which I'm much more comfortable with), optimize it (a lot!), and add some features:<br />
<br />
'''1)''' It will be rotationally insensitive so you don't need to look at it to determine portrait vs. landscape before you unlock. This will be pretty easy to add.<br />
<br />
'''2)''' The text on there is statically-coded right now, and fixing that will be trivial, so don't complain about it now. It doesn't actually tell you the GSM/GPRS status or even the real time of day. Yes, wise guy, IT'S ALWAYS 5:35 pm HERE.<br />
<br />
'''3)''' Eventually it will get a battery/charging state icon, GSM signal strength bars, and a ringer volume indicator, so you can see those things while the screen remains locked. I don't want to make the interface too cluttered, but those items seem essential.<br />
<br />
'''4)''' Ideally this will slip right into the OpenMoko power management scheme. Preferably neod and/or the dialer will *lock* the screen and require an unlock program (such as zedlock) in the following circumstances:<br />
<br />
* immediately after an incoming call is answered<br />
(to prevent touchscreen input from the user's face or ear)<br />
<br />
* immediately after an outgoing call is dialed<br />
(ditto)<br />
<br />
* on request<br />
(via a lock button or menu, before you put it in your pocket)<br />
<br />
* upon an automatic return-from-suspend<br />
(e.g., a datebook alarm, incoming phone call, SMS, etc.)<br />
<br />
* but *not* following a manual return-from-suspend<br />
<br />
Note that this concept of screen-lock is different from the power-management concept of screen blanking. Screen LOCK should probably occur more often, and is intended primarily to prevent accidental user-interface manipulation while the touchscreen is against the user's face, in the user's pocket, or otherwise subject to spurious inputs. It is not intended to save power.<br />
<br />
=== Password Safe ===<br />
<br />
Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives. KeePassX compiles successfully but never opens a window on the Neo, and I'm not sure why -- other QT applications seem to work fine.<br />
<br />
=== Xournal ===<br />
<br />
Xournal [http://xournal.sourceforge.net] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
== Finished Projects ==<br />
<br />
=== Free42 ===<br />
<br />
[http://home.planet.nl/~demun000/thomas_projects/free42/ Free42] is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
[[Image:Image-free42.jpg]]<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo.<br />
<br />
It's now available in the OE repository. The package name is free42-vga<br />
<br />
=== Notecase ===<br />
<br />
[http://notecase.sourceforge.net Notecase] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. I have uploaded a .bb file and patch for the latest version (1.6.6) to the OE bugtracker.<br />
<br />
== Future Projects ==<br />
<br />
=== Handwriting Recognition ===<br />
<br />
Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
=== Music Platform ===<br />
<br />
I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-10-11T22:26:00Z<p>Quicksand: /* zedlock */</p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at wixonlaw.com [http://www.wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
=== zedlock ===<br />
<br />
Screen locking program. Currently in PROTOTYPE form.<br />
<br />
Download [http://wixonlaw.com/public/zedlock-0.0.1.tar.bz2 zedlock 0.0.1]<br />
<br />
[[Image:Zedlock-screenshot-1.png]]<br />
<br />
'''How it works'''<br />
<br />
This is a screen-lock program in prototype form. To run it, just run zedlock.py from a terminal in the directory where it's installed.<br />
<br />
It's really simple. To unlock, just trace a large 'Z' with a single stroke of your finger or stylus, anywhere on the screen. It must be BIG ENOUGH (about half the smallest screen dimension in both height and width, approx. 2cm on the Neo), it must be drawn in the CORRECT SEQUENCE (from top-left to bottom-right), and it must be QUICK ENOUGH (completed in less than one second). Within these parameters, a fair amount of variation (i.e., sloppiness) is tolerated. (As a result, you can make some non-Z patterns that fool it.)<br />
<br />
'''Who's Zed?'''<br />
<br />
Zed's dead, baby, Zed's dead.<br />
<br />
'''No, really, why Zed?'''<br />
<br />
There are a bunch of things out there already called "zlock" or the like. I selected the 'Z' glyph because it's fast and easy to make without looking, and its four points are easy to pull out of a stream of touchscreen data -- they are simply the maxima and minima of the functions (x+y) and (x-y). I don't need to keep a linked list of intermediate points or anything like that; these points are updated on-the-fly.<br />
<br />
'''Why would I want this?'''<br />
<br />
You don't need to be looking at the screen to unlock it. It is pretty unlikely to unlock accidentally (by your face while you are on the phone, in your pocket, etc.). But it's simple and fast enough to perform frequently and easily, and to become second-nature.<br />
<br />
Plus it looks nice: gtk+ and cairo are used for fluid anti-aliased graphics. Visual feedback is provided after a stroke is completed: an openmoko-orange line shows where you made your stroke, and if it finds the 'Z' pattern, it is highlighted in white for a moment. <br />
<br />
Success:<br />
<br />
[[Image:Zedlock-screenshot-2.png]]<br />
<br />
If your stroke doesn't meet the criteria, you get a big red 'X' on the screen and a three-second lockout.<br />
<br />
Too small:<br />
<br />
[[Image:Zedlock-screenshot-3.png]]<br />
<br />
Wrong sequence:<br />
<br />
[[Image:Zedlock-screenshot-4.png]]<br />
<br />
With the iPhone and the Qtopia phone platform, you need to be looking at the touchscreen to unlock it. Their sliders and animated keys are cool, but this is better.<br />
<br />
'''Remember, this is a prototype'''<br />
<br />
To install it, copy zedlock.py and zedlock.png to your home directory (or a subdirectory), make sure zedlock.py is executable, and run it from the directory you installed it in. The program depends on python-pygtk and python-pycairo. Note that it doesn't actually do anything all that functional yet -- it is simply a demonstration program. This prototype doesn't actually lock or unlock anything; it just clears the screen after each stroke (and the subsequent visual feedback) so you can try it again and again and again.<br />
<br />
The program should be more-or-less QVGA-friendly (well, almost, just change two global variables) and orientation-friendly already, but YMMV.<br />
<br />
Yes, it's slow, especially to start up. But that's embedded python for ya. Plus I had to do some weird hacky things in cairo to get it to render predictably. This is my first cairo project and my first python program, SO DON'T GIVE ME ANY GRIEF! There are probably terrible, ugly, spaghetti-code-monsters in there if you care to look. They'll go away over time. :)<br />
<br />
'''Future Plans'''<br />
<br />
After the featureset solidifies a bit more, I will rewrite it in C (which I'm much more comfortable with), optimize it (a lot!), and add some features:<br />
<br />
'''1)''' It will be rotationally insensitive so you don't need to look at it to determine portrait vs. landscape before you unlock. This will be pretty easy to add.<br />
<br />
'''2)''' The text on there is statically-coded right now, and fixing that will be trivial, so don't complain about it now. It doesn't actually tell you the GSM/GPRS status or even the real time of day. Yes, wise guy, IT'S ALWAYS 5:35 pm HERE.<br />
<br />
'''3)''' Eventually it will get a battery/charging state icon, GSM signal strength bars, and a ringer volume indicator, so you can see those things while the screen remains locked. I don't want to make the interface too cluttered, but those items seem essential.<br />
<br />
'''4)''' Ideally this will slip right into the OpenMoko power management scheme. Preferably neod and/or the dialer will *lock* the screen and require an unlock program (such as zedlock) in the following circumstances:<br />
<br />
* immediately after an incoming call is answered<br />
(to prevent touchscreen input from the user's face or ear)<br />
<br />
* immediately after an outgoing call is dialed<br />
(ditto)<br />
<br />
* on request<br />
(via a lock button or menu, before you put it in your pocket)<br />
<br />
* upon an automatic return-from-suspend<br />
(e.g., a datebook alarm, incoming phone call, SMS, etc.)<br />
<br />
* but *not* following a manual return-from-suspend<br />
<br />
Note that this concept of screen-lock is different from the power-management concept of screen blanking. Screen LOCK should probably occur more often, and is intended primarily to prevent accidental user-interface manipulation while the touchscreen is against the user's face, in the user's pocket, or otherwise subject to spurious inputs. It is not intended to save power.<br />
<br />
=== Password Safe ===<br />
<br />
Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives. KeePassX compiles successfully but never opens a window on the Neo, and I'm not sure why -- other QT applications seem to work fine.<br />
<br />
=== Xournal ===<br />
<br />
Xournal [http://xournal.sourceforge.net] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
== Finished Projects ==<br />
<br />
=== Free42 ===<br />
<br />
Free42 [http://home.planet.nl/~demun000/thomas_projects/free42/] is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
[[Image:Image-free42.jpg]]<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo.<br />
<br />
I have submitted this to the OE people upstream for inclusion into their metadata package. For the impatient, the .bb recipe and patches are available via their bugtracker. [http://bugs.openembedded.org/show_bug.cgi?id=2920] <br />
<br />
=== Notecase ===<br />
<br />
Notecase [http://notecase.sourceforge.net] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. I have uploaded a .bb file and patch for the latest version (1.6.6) to the OE bugtracker.<br />
<br />
== Future Projects ==<br />
<br />
=== Handwriting Recognition ===<br />
<br />
Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
=== Music Platform ===<br />
<br />
I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-10-11T18:51:09Z<p>Quicksand: </p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at wixonlaw.com [http://www.wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
=== zedlock ===<br />
<br />
Screen locking program. Currently in PROTOTYPE form.<br />
<br />
[[Image:Zedlock-screenshot-1.png]]<br />
<br />
'''How it works'''<br />
<br />
This is a screen-lock program in prototype form. To run it, just run zedlock.py from a terminal in the directory where it's installed.<br />
<br />
It's really simple. To unlock, just trace a large 'Z' with a single stroke of your finger or stylus, anywhere on the screen. It must be BIG ENOUGH (about half the smallest screen dimension in both height and width, approx. 2cm on the Neo), it must be drawn in the CORRECT SEQUENCE (from top-left to bottom-right), and it must be QUICK ENOUGH (completed in less than one second). Within these parameters, a fair amount of variation (i.e., sloppiness) is tolerated. (As a result, you can make some non-Z patterns that fool it.)<br />
<br />
'''Who's Zed?'''<br />
<br />
Zed's dead, baby, Zed's dead.<br />
<br />
'''No, really, why Zed?'''<br />
<br />
There are a bunch of things out there already called "zlock" or the like. I selected the 'Z' glyph because it's fast and easy to make without looking, and its four points are easy to pull out of a stream of touchscreen data -- they are simply the maxima and minima of the functions (x+y) and (x-y). I don't need to keep a linked list of intermediate points or anything like that; these points are updated on-the-fly.<br />
<br />
'''Why would I want this?'''<br />
<br />
You don't need to be looking at the screen to unlock it. It is pretty unlikely to unlock accidentally (by your face while you are on the phone, in your pocket, etc.). But it's simple and fast enough to perform frequently and easily, and to become second-nature.<br />
<br />
Plus it looks nice: gtk+ and cairo are used for fluid anti-aliased graphics. Visual feedback is provided after a stroke is completed: an openmoko-orange line shows where you made your stroke, and if it finds the 'Z' pattern, it is highlighted in white for a moment. <br />
<br />
Success:<br />
<br />
[[Image:Zedlock-screenshot-2.png]]<br />
<br />
If your stroke doesn't meet the criteria, you get a big red 'X' on the screen and a three-second lockout.<br />
<br />
Too small:<br />
<br />
[[Image:Zedlock-screenshot-3.png]]<br />
<br />
Wrong sequence:<br />
<br />
[[Image:Zedlock-screenshot-4.png]]<br />
<br />
With the iPhone and the Qtopia phone platform, you need to be looking at the touchscreen to unlock it. Their sliders and animated keys are cool, but this is better.<br />
<br />
'''Remember, this is a prototype'''<br />
<br />
To install it, copy zedlock.py and zedlock.png to your home directory (or a subdirectory), make sure zedlock.py is executable, and run it from the directory you installed it in. The program depends on python-pygtk and python-pycairo. Note that it doesn't actually do anything all that functional yet -- it is simply a demonstration program. This prototype doesn't actually lock or unlock anything; it just clears the screen after each stroke (and the subsequent visual feedback) so you can try it again and again and again.<br />
<br />
The program should be more-or-less QVGA-friendly (well, almost, just change two global variables) and orientation-friendly already, but YMMV.<br />
<br />
Yes, it's slow, especially to start up. But that's embedded python for ya. Plus I had to do some weird hacky things in cairo to get it to render predictably. This is my first cairo project and my first python program, SO DON'T GIVE ME ANY GRIEF! There are probably terrible, ugly, spaghetti-code-monsters in there if you care to look. They'll go away over time. :)<br />
<br />
'''Future Plans'''<br />
<br />
After the featureset solidifies a bit more, I will rewrite it in C (which I'm much more comfortable with), optimize it (a lot!), and add some features:<br />
<br />
'''1)''' It will be rotationally insensitive so you don't need to look at it to determine portrait vs. landscape before you unlock. This will be pretty easy to add.<br />
<br />
'''2)''' The text on there is statically-coded right now, and fixing that will be trivial, so don't complain about it now. It doesn't actually tell you the GSM/GPRS status or even the real time of day. Yes, wise guy, IT'S ALWAYS 5:35 pm HERE.<br />
<br />
'''3)''' Eventually it will get a battery/charging state icon, GSM signal strength bars, and a ringer volume indicator, so you can see those things while the screen remains locked. I don't want to make the interface too cluttered, but those items seem essential.<br />
<br />
'''4)''' Ideally this will slip right into the OpenMoko power management scheme. Preferably neod and/or the dialer will *lock* the screen and require an unlock program (such as zedlock) in the following circumstances:<br />
<br />
* immediately after an incoming call is answered<br />
(to prevent touchscreen input from the user's face or ear)<br />
<br />
* immediately after an outgoing call is dialed<br />
(ditto)<br />
<br />
* on request<br />
(via a lock button or menu, before you put it in your pocket)<br />
<br />
* upon an automatic return-from-suspend<br />
(e.g., a datebook alarm, incoming phone call, SMS, etc.)<br />
<br />
* but *not* following a manual return-from-suspend<br />
<br />
Note that this concept of screen-lock is different from the power-management concept of screen blanking. Screen LOCK should probably occur more often, and is intended primarily to prevent accidental user-interface manipulation while the touchscreen is against the user's face, in the user's pocket, or otherwise subject to spurious inputs. It is not intended to save power.<br />
<br />
=== Password Safe ===<br />
<br />
Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives. KeePassX compiles successfully but never opens a window on the Neo, and I'm not sure why -- other QT applications seem to work fine.<br />
<br />
=== Xournal ===<br />
<br />
Xournal [http://xournal.sourceforge.net] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
== Finished Projects ==<br />
<br />
=== Free42 ===<br />
<br />
Free42 [http://home.planet.nl/~demun000/thomas_projects/free42/] is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
[[Image:Image-free42.jpg]]<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo.<br />
<br />
I have submitted this to the OE people upstream for inclusion into their metadata package. For the impatient, the .bb recipe and patches are available via their bugtracker. [http://bugs.openembedded.org/show_bug.cgi?id=2920] <br />
<br />
=== Notecase ===<br />
<br />
Notecase [http://notecase.sourceforge.net] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. I have uploaded a .bb file and patch for the latest version (1.6.6) to the OE bugtracker.<br />
<br />
== Future Projects ==<br />
<br />
=== Handwriting Recognition ===<br />
<br />
Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
=== Music Platform ===<br />
<br />
I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/File:Zedlock-screenshot-4.pngFile:Zedlock-screenshot-4.png2007-10-11T18:43:55Z<p>Quicksand: </p>
<hr />
<div></div>Quicksandhttp://wiki.openmoko.org/wiki/File:Zedlock-screenshot-3.pngFile:Zedlock-screenshot-3.png2007-10-11T18:43:37Z<p>Quicksand: </p>
<hr />
<div></div>Quicksandhttp://wiki.openmoko.org/wiki/File:Zedlock-screenshot-2.pngFile:Zedlock-screenshot-2.png2007-10-11T18:43:12Z<p>Quicksand: </p>
<hr />
<div></div>Quicksandhttp://wiki.openmoko.org/wiki/File:Zedlock-screenshot-1.pngFile:Zedlock-screenshot-1.png2007-10-11T18:42:49Z<p>Quicksand: </p>
<hr />
<div></div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-10-11T18:41:57Z<p>Quicksand: </p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at wixonlaw.com [http://www.wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
=== zedlock ===<br />
<br />
Screen locking program. Currently in PROTOTYPE form. I will have a download and some screenshots ready shortly.<br />
<br />
'''How it works'''<br />
<br />
This is a screen-lock program in prototype form. To run it, just run zedlock.py from a terminal in the directory where it's installed.<br />
<br />
It's really simple. To unlock, just trace a large 'Z' with a single stroke of your finger or stylus, anywhere on the screen. It must be BIG ENOUGH (about half the smallest screen dimension in both height and width, approx. 2cm on the Neo), it must be drawn in the CORRECT SEQUENCE (from top-left to bottom-right), and it must be QUICK ENOUGH (completed in less than one second). Within these parameters, a fair amount of variation (i.e., sloppiness) is tolerated. (As a result, you can make some non-Z patterns that fool it.)<br />
<br />
'''Who's Zed?'''<br />
<br />
Zed's dead, baby, Zed's dead.<br />
<br />
'''No, really, why Zed?'''<br />
<br />
There are a bunch of things out there already called "zlock" or the like. I selected the 'Z' glyph because it's fast and easy to make without looking, and its four points are easy to pull out of a stream of touchscreen data -- they are simply the maxima and minima of the functions (x+y) and (x-y). I don't need to keep a linked list of intermediate points or anything like that; these points are updated on-the-fly.<br />
<br />
'''Why would I want this?'''<br />
<br />
You don't need to be looking at the screen to unlock it. It is pretty unlikely to unlock accidentally (by your face while you are on the phone, in your pocket, etc.). But it's simple and fast enough to perform frequently and easily, and to become second-nature.<br />
<br />
Plus it looks nice: gtk+ and cairo are used for fluid anti-aliased graphics. Visual feedback is provided after a stroke is completed: an openmoko-orange line shows where you made your stroke, and if it finds the 'Z' pattern, it is highlighted in white for a moment. If your stroke doesn't meet the criteria, you get a big red 'X' on the screen and a three-second lockout.<br />
<br />
With the iPhone and the Qtopia phone platform, you need to be looking at the touchscreen to unlock it. Their sliders and animated keys are cool, but this is better.<br />
<br />
'''Remember, this is a prototype'''<br />
<br />
To install it, copy zedlock.py and zedlock.png to your home directory (or a subdirectory), make sure zedlock.py is executable, and run it from the directory you installed it in. The program depends on python-pygtk and python-pycairo. Note that it doesn't actually do anything all that functional yet -- it is simply a demonstration program. This prototype doesn't actually lock or unlock anything; it just clears the screen after each stroke (and the subsequent visual feedback) so you can try it again and again and again.<br />
<br />
The program should be more-or-less QVGA-friendly (well, almost, just change two global variables) and orientation-friendly already, but YMMV.<br />
<br />
Yes, it's slow, especially to start up. But that's embedded python for ya. Plus I had to do some weird hacky things in cairo to get it to render predictably. This is my first cairo project and my first python program, SO DON'T GIVE ME ANY GRIEF! There are probably terrible, ugly, spaghetti-code-monsters in there if you care to look. They'll go away over time. :)<br />
<br />
'''Future Plans'''<br />
<br />
After the featureset solidifies a bit more, I will rewrite it in C (which I'm much more comfortable with), optimize it (a lot!), and add some features:<br />
<br />
'''1)''' It will be rotationally insensitive so you don't need to look at it to determine portrait vs. landscape before you unlock. This will be pretty easy to add.<br />
<br />
'''2)''' The text on there is statically-coded right now, and fixing that will be trivial, so don't complain about it now. It doesn't actually tell you the GSM/GPRS status or even the real time of day. Yes, wise guy, IT'S ALWAYS 5:35 pm HERE.<br />
<br />
'''3)''' Eventually it will get a battery/charging state icon, GSM signal strength bars, and a ringer volume indicator, so you can see those things while the screen remains locked. I don't want to make the interface too cluttered, but those items seem essential.<br />
<br />
'''4)''' Ideally this will slip right into the OpenMoko power management scheme. Preferably neod and/or the dialer will *lock* the screen and require an unlock program (such as zedlock) in the following circumstances:<br />
<br />
* immediately after an incoming call is answered<br />
(to prevent touchscreen input from the user's face or ear)<br />
<br />
* immediately after an outgoing call is dialed<br />
(ditto)<br />
<br />
* on request<br />
(via a lock button or menu, before you put it in your pocket)<br />
<br />
* upon an automatic return-from-suspend<br />
(e.g., a datebook alarm, incoming phone call, SMS, etc.)<br />
<br />
* but *not* following a manual return-from-suspend<br />
<br />
Note that this concept of screen-lock is different from the power-management concept of screen blanking. Screen LOCK should probably occur more often, and is intended primarily to prevent accidental user-interface manipulation while the touchscreen is against the user's face, in the user's pocket, or otherwise subject to spurious inputs. It is not intended to save power.<br />
<br />
=== Password Safe ===<br />
<br />
Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives. KeePassX compiles successfully but never opens a window on the Neo, and I'm not sure why -- other QT applications seem to work fine.<br />
<br />
=== Xournal ===<br />
<br />
Xournal [http://xournal.sourceforge.net] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
== Finished Projects ==<br />
<br />
=== Free42 ===<br />
<br />
Free42 [http://home.planet.nl/~demun000/thomas_projects/free42/] is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
[[Image:Image-free42.jpg]]<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo.<br />
<br />
I have submitted this to the OE people upstream for inclusion into their metadata package. For the impatient, the .bb recipe and patches are available via their bugtracker. [http://bugs.openembedded.org/show_bug.cgi?id=2920] <br />
<br />
=== Notecase ===<br />
<br />
Notecase [http://notecase.sourceforge.net] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. I have uploaded a .bb file and patch for the latest version (1.6.6) to the OE bugtracker.<br />
<br />
== Future Projects ==<br />
<br />
=== Handwriting Recognition ===<br />
<br />
Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
=== Music Platform ===<br />
<br />
I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/Main_PageMain Page2007-09-10T23:11:19Z<p>Quicksand: </p>
<hr />
<div>{{Languages|Main_Page}}<br />
__NOTOC__<br />
__NOEDITSECTION__<br />
__NOTOC__<br />
{| cellspacing="5" cellpadding="0" style="padding: 2%; margin:0em 0em 1em 0em; border:1px solid #F9D163; background:#FCE9B4; width:100%" <br />
| <big>'''Welcome to the [[OpenMoko]]&trade; public Wiki'''</big><br><br />
|}<br />
<br />
[[Image:FIC-neo1973_small.jpg|200px|right|frontside]]<br />
OpenMoko&trade; is an [http://en.wikipedia.org/wiki/Open_source Open Source] project to create the world's first free mobile phone operating system.<br />
<br />
The [[OpenMoko]] project is a community that anyone can join, to help design their ideal phone.<br />
<br />
Eventually, phone software won't be tied to any particular phone.<br />
<br />
You can install any OpenMoko software over the whole range of [[Supported Hardware|supported phones]], and if you upgrade your phone, you don't lose that software. Bugs fixed on any phone are fixed on all. <br />
<br />
'''Currently it is not suitable for users.''' The state of the software at the moment is pre-alpha. If you order a Neo1973, DO NOT expect to be able to use it as an everyday phone until October 2007 at the soonest, and probably later.<br />
<br />
The [[Neo1973]] from [[FIC]] is the first of many phones that OpenMoko will run on. Buy it at [https://direct.openmoko.com/ Openmoko Online Shop] (currently [http://jouston.no-ip.com/archives/000230.html out of stock]). You may wish to see the [[SH1 FAQ|Shipment 1 FAQ]].<br />
<br />
Please join us in collaborating on the OpenMoko project through any of the [[Development resources | project resources]] including this OpenMoko wiki. Please see the [[Help:Contents | wiki editing help]] page for information on making contributions to this wiki. A [[Meet the Core Team | core team]] of developers funded by FIC, Inc. leads the project.<br />
<br />
An [[introduction]] page is available, with [[Introduction#Photos|photos]] and [[Introduction#Videos|videos]]. Moreover, the usual [[FAQ | Frequently Asked Questions]] (FAQ) page might be helpful. Developers may find the [[ChangeLog | change log]] an important resource.<br />
<br />
Update 2007-07-25: The [http://forums.makeopensource.com/ Unofficial OpenMoko Forums] are now open! Everyone is invited to participate!<br />
<br />
<br />
The members of the OpenMoko community would like to thank FIC Inc. for showing leadership and initiating the OpenMoko project.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="5" width=100%<br />
! width=100% colspan="2" style="background:#F9D163;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | What's Your Interest?<br />
|-<br />
<br />
|valign="TOP" width="50%" style="background:#FCE9B4;border-left:5px solid white;border-bottom:5px solid white;" | <br />
<br />
* [[Basic End-user]] - Information for end users who want basic functionality and no surprises<br />
* [[Advanced End-user]] - Information for advanced end-users who want advanced and experimental functionality but who are not programmers<br />
* [[Business Development]] - Exchange of commercial opportunities for promoting widespread end-user acceptance.<br />
<br />
|valign="TOP" width="50%" style="background:#FCE9B4;border-right:5px solid white;border-bottom:5px solid white;" | <br />
* [[Application Developer]] - Information for application developers, including ideas and specifications for applications, and tools to build them<br />
* [[System Developer]] - Information for system developers, including bootloader, kernel, and libraries<br />
* [[Hardware Developer]] - Information for hardware developers, including hardware specs and debug board<br />
<br />
|}<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="5" width=100%<br />
! width=33% style="background:#d1d1d1;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | General<br />
! width=33% style="background:#C5FDAF;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Developer Guides<br />
! width=33% style="background:#FDAFAF;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Developer Reference Documentation<br />
|-<br />
|valign="TOP" style="background:#ebebeb;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" |<br />
* [[Development resources | Project Resources]] - Provides a centralized location of all resources such as [[Development resources#Mailing_Lists|mailing lists]], [[Development resources#IRC | communication tools]], and other software development oriented resources.<br />
<br />
* [[Current events]] - Information on both past and future events where FIC or OpenMoko had or will have a presence.<br />
* [http://forums.makeopensource.com/ Unofficial OpenMoko Forums] - Everyone is invited to collaborate with OpenMoko users and developers on the forums.<br />
* Most of the documentation and Wiki assumes you are using Linux; here are some notes for users of [[Other OSes]].<br />
* [[MacOS_X|Mac OS X]] - Information specific for those who use Mac OS X<br />
<br />
'''Administrative + Organizational'''<br />
* [[Shipping Notes]] - Information to help FIC figure out how to ship products to you, and how much it might cost.<br />
* [[My Account]] - Ideas for what sort of account-based services FIC should provide with the phone.<br />
* [[Hear Me FIC]] - Information to help FIC know what the community wants.<br />
* [[Listen Up Community]] - Community's To-Do-List<br />
* [[Wiki Issues]] - problems/requests regarding this Wiki<br />
<br />
<br />
|valign="TOP" style="background:#E8FFDF;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" | <br />
* [[Getting Started with your Neo1973]]<br />
* [[installation_guide|A guide for flashing and emulating the openmoko software]] (In progress, this should replace the following options)<br />
** [[Flashing_openmoko|Flashing openmoko with the kernel, the root filesystem and optionally u-boot.]]<br />
** [[MokoMakefile|Building OpenMoko using the MokoMakefile]]<br />
** [[Application Development Crash Course]] -A very basic how-to for the new people. <br />
** [[OpenMoko2007.2|Building OpenMoko 2007.2]]<br />
** [[Building OpenMoko from scratch]]<br />
*** [[Building a hello world application]]<br />
*** Old [[Building OpenMoko from scratch (pre-BBT)]]<br />
** [[Running OpenMoko on PC]]<br />
*** [[Getting OpenMoko working on host with Xoo]]<br />
*** [[Getting OpenMoko working on host with Xephyr]]<br />
*** [[How to run OpenMoko Apps on PC]]<br />
*** [[OpenMoko under QEMU]]<br />
*** [[Test Openmoko Emulation with chroot image|Test Openmoko Emulation with a Prebuilt chroot Image]]<br />
* [[Migration to bad block tolerant builds]]<br />
* [[Booting from SD]]<br />
<br />
|valign="TOP" style="background:#FFDADA;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;"| <br />
'''Hardware Reference Documentation'''<br />
* All [[:Category:Hardware|Hardware]] related documentation and specifications are found on the [[:Category:Hardware|Hardware page]].<br />
* The [[Neo1973 Hardware]] page provides an overview of the hardware components used by the [[:Category:Neo1973 Hardware|Neo1973 hardware platform]]. PCB photographs are also included. A [[Disassembling Neo1973 | photo disassembly story]] may be an interesting starting place.<br />
* [[:Category:Neo1973 Hardware Debugging | Neo1973 Hardware Debugging]] is assisted with the [[Debug Board | Neo1973 debug board]]. A page discussing [[Connecting Neo1973 with Debug Board v2 | debug board and Neo1973 configurations]] is also provided.<br />
<br />
'''Software Reference Documentation'''<br />
* Architectural<br />
** [[OpenMokoFramework]] - The OpenMoko Application Framework<br />
* [[Neo1973 host software]]<br />
* Device Software<br />
** Low-Level<br />
*** [[u-boot]] - The bootloader we use, including documentation for our modifications<br />
*** [[kernel]] - The Linux kernel we use, including documentation for our modifications<br />
** Userspace<br />
*** [[binary compatibility]]<br />
*** [[gsmd]] - the GSM daemon managing the GSM Modem<br />
*** [[gpsd]] - the AGPS (Assisted GPS) daemon<br />
<br />
<br />
|}<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="5" width=100%<br />
! width=33% style="background:#FCC6FF;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | OpenMoko-specific Development<br />
! width=33% style="background:#B3DDF4;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | OpenMoko Miscellaneous Development<br />
! width=33% style="background:#F5FC7F;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Miscellaneous<br />
|-<br />
|valign="TOP" style="background:#FEE9FF;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" | <br />
* [[OpenEmbedded]] - The distribution-building framework<br />
* [[Toolchain]] - The toolchain we use for compilation<br />
* [[OpenMoko]] - The OpenMoko distribution<br />
** [[OpenMoko2007]] - The first intended release of it<br />
** [[OpenMoko2007.2]] - An improved release with more formalized style guidelines.<br />
** [[Userspace root image]]<br />
<br />
'''User Interface Related'''<br />
* [[GUI Style Guidelines]] -- New for [[OpenMoko2007.2]]<br />
* [[Look & Feel]]<br />
** [[Artwork]]<br />
* [[Applications]]<br />
* [[Widgets]]<br />
** [[Widget Inheritance Graph]]<br />
* [[Application UI Design Recommendations]]<br />
<br />
|valign="TOP" style="background:#D4EDFB;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" | <br />
* [[Freshman todo]]<br />
* [[Templates]]<br />
* [[PIM Storage]]<br />
* [[Coding Guidelines]]<br />
* [[OpenMoko#Setting_up_an_OpenMoko_SDK|How to setup the OpenMoko SDK]]<br />
* Alternative distributions for [[Neo1973]] GTA01: [[Angstrom on Neo1973]], [http://pokylinux.org Poky] [http://www.usome.com](instructions needed!)<br />
* [[License]] - How we license our code<br />
* [[Development resources]] - Describes resources for developers (lists, svn, ...)<br />
* [[Neo1973 Phase 0]] - Information for Phase 0 device owners<br />
* [[Wishlist:Neo1973 P0 Review]] - Impressions of the Phase 0 hardware device, also the Phase 0 FAQ<br />
* [[Neo1973 Phase 1]] - Information for Phase 1 device owners<br />
* [[Wishlist:Neo1973 P1 Review]] - Impressions of the Phase 1 hardware device<br />
* [[External Feeds]] - List of feeds from people blogging about OpenMoko<br />
<br />
<br />
|valign="TOP" style="background:#FCFFCD;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" | <br />
* [[WiFi support in OpenMoko]]<br />
* [[Neo1973 and Windows]] - If you want to commit that offence ;)<br />
* [[Press Coverage]] - What the press says about the OpenMoko project<br />
* [[mFAQ]] - The OpenMoko Misinformation FAQ ('''mFAQ''') - What the press '''''incorrectly''''' says about the OpenMoko project<br />
* [[Wish List]] - A collection of ideas and ideals we'd like to see implemented some day<br />
* [[Wish List - Hardware]] - A collection of ideas we'd like to see in the next Neo release<br />
* [[Wishlist:BuiltInScriptingLanguage|Wish List - Built-in Scripting Language]] - Discussion on a suitable scripting language to be included<br />
* [[Wish List - OpenMoko Ringtones and Sounds]] Collection of [http://en.wikipedia.org/wiki/Free_music free music]/sounds/ringtones we'd like to listen in the next Neo release<br />
* [[Media Content]] - What types of media on the device can we use (that is non-software)?<br />
* [[Testimonials]] - How did you get to OpenMoko?<br />
* [[Buying Interest List]] - (Not official and not a pre-order page) Have you put money aside for Neo1973? Put your nick here.<br />
* [[iPhone]] - Comparison between Apple iPhone and FIC Neo1973<br />
* [[Translation]] - Translation of OpenMoko<br />
* [[Summer of code]] - Our page with project applications for Google's Summer of Code<br />
* [[SWAG]] - Where to purchase openmoko swag (T-Shirts!)<br />
* [[Trademark Policy]] -- The OpenMoko Trademark Policy<br />
<br />
|}<br />
<br />
<br />
<br />
<span id="bottom"></span><br />
<br />
[[Category:Information| ]]<br />
[[Category:Categories| ]]</div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-09-04T20:09:10Z<p>Quicksand: /* Current Projects */</p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at wixonlaw.com [http://www.wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
'''Free42''' [http://home.planet.nl/~demun000/thomas_projects/free42/]is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
[[Image:Image-free42.jpg]]<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo.<br />
<br />
I have submitted this to the OE people upstream for inclusion into their metadata package. For the impatient, the .bb recipe and patches are available via their bugtracker. [http://bugs.openembedded.org/show_bug.cgi?id=2920] <br />
<br />
'''Xournal''' [http://xournal.sourceforge.net] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
'''Notecase''' [http://notecase.sourceforge.net] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. There's a .bb recipe for an old version of Notecase in the OE metadata, and in the coming days I will be bringing that up to date and tweaking the user interface for small-screen devices such as the Neo.<br />
<br />
'''Password Safe''' - Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives.<br />
<br />
== Future Projects ==<br />
<br />
'''Handwriting Recognition''' - Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
'''Music Platform''' - I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-09-04T19:30:08Z<p>Quicksand: /* Future Projects */</p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at wixonlaw.com [http://www.wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
'''Free42''' [http://home.planet.nl/~demun000/thomas_projects/free42/]is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
[[Image:Image-free42.jpg]]<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo.<br />
<br />
I will upload the .bb recipe and patches soon, and I will also submit it to the OE people upstream for inclusion into their metadata package.<br />
<br />
'''Xournal''' [http://xournal.sourceforge.net] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
'''Notecase''' [http://notecase.sourceforge.net] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. There's a .bb recipe for an old version of Notecase in the OE metadata, and in the coming days I will be bringing that up to date and tweaking the user interface for small-screen devices such as the Neo.<br />
<br />
'''Password Safe''' - Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives.<br />
<br />
== Future Projects ==<br />
<br />
'''Handwriting Recognition''' - Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
'''Music Platform''' - I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-09-04T19:29:07Z<p>Quicksand: /* Current Projects */</p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at wixonlaw.com [http://www.wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
'''Free42''' [http://home.planet.nl/~demun000/thomas_projects/free42/]is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
[[Image:Image-free42.jpg]]<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo.<br />
<br />
I will upload the .bb recipe and patches soon, and I will also submit it to the OE people upstream for inclusion into their metadata package.<br />
<br />
'''Xournal''' [http://xournal.sourceforge.net] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
'''Notecase''' [http://notecase.sourceforge.net] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. There's a .bb recipe for an old version of Notecase in the OE metadata, and in the coming days I will be bringing that up to date and tweaking the user interface for small-screen devices such as the Neo.<br />
<br />
'''Password Safe''' - Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives.<br />
<br />
== Upcoming Projects ==<br />
<br />
'''Handwriting Recognition''' - Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
'''Music Platform''' - I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-09-04T19:26:57Z<p>Quicksand: /* Current Projects */</p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at wixonlaw.com [http://www.wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
'''Free42''' [http://home.planet.nl/~demun000/thomas_projects/free42/]is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo. See [[Image:free42.jpg]].<br />
<br />
I will upload the .bb recipe and patches soon, and I will also submit it to the OE people upstream for inclusion into their metadata package.<br />
<br />
'''Xournal''' [http://xournal.sourceforge.net] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
'''Notecase''' [http://notecase.sourceforge.net] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. There's a .bb recipe for an old version of Notecase in the OE metadata, and in the coming days I will be bringing that up to date and tweaking the user interface for small-screen devices such as the Neo.<br />
<br />
'''Password Safe''' - Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives.<br />
<br />
== Upcoming Projects ==<br />
<br />
'''Handwriting Recognition''' - Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
'''Music Platform''' - I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/File:Image-free42.jpgFile:Image-free42.jpg2007-09-04T19:26:33Z<p>Quicksand: </p>
<hr />
<div></div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-09-04T19:22:48Z<p>Quicksand: </p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at wixonlaw.com [http://www.wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
'''Free42''' [http://home.planet.nl/~demun000/thomas_projects/free42/]is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo. See [[Image:http://scap.linuxtogo.org/files/287b2c44ec16c6aece2cb4fbaa66b02d.png]].<br />
<br />
I will upload the .bb recipe and patches soon, and I will also submit it to the OE people upstream for inclusion into their metadata package.<br />
<br />
'''Xournal''' [http://xournal.sourceforge.net] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
'''Notecase''' [http://notecase.sourceforge.net] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. There's a .bb recipe for an old version of Notecase in the OE metadata, and in the coming days I will be bringing that up to date and tweaking the user interface for small-screen devices such as the Neo.<br />
<br />
'''Password Safe''' - Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives.<br />
<br />
== Upcoming Projects ==<br />
<br />
'''Handwriting Recognition''' - Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
'''Music Platform''' - I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-09-04T17:59:49Z<p>Quicksand: </p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at wixonlaw.com [http://www.wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
'''Free42''' [http://home.planet.nl/~demun000/thomas_projects/free42/]is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo. See [http://scap.linuxtogo.org/files/287b2c44ec16c6aece2cb4fbaa66b02d.png].<br />
<br />
I will upload the .bb recipe and patches soon, and I will also submit it to the OE people upstream for inclusion into their metadata package.<br />
<br />
'''Xournal''' [http://xournal.sourceforge.net] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
'''Notecase''' [http://notecase.sourceforge.net] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. There's a .bb recipe for an old version of Notecase in the OE metadata, and in the coming days I will be bringing that up to date and tweaking the user interface for small-screen devices such as the Neo.<br />
<br />
'''Password Safe''' - Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives.<br />
<br />
== Upcoming Projects ==<br />
<br />
'''Handwriting Recognition''' - Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
'''Music Platform''' - I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/User:QuicksandUser:Quicksand2007-09-04T17:49:34Z<p>Quicksand: </p>
<hr />
<div>Clarke A. Wixon ("Quicksand") is a U.S. (California) intellectual property attorney by day, OpenMoko hacker by night.<br />
<br />
I hope to bring some useful PDA-style applications to the OpenMoko platform, either by porting existing desktop applications, by fine-tuning existing bitbake recipes and user interface definitions in the OpenEmbedded database to better take advantage of the OpenMoko form factor and capabilities, or by coding something up to fit my own personal needs.<br />
<br />
I have a degree in mathematics, and I have interests in natural language processing and in electronic music. Accordingly, as time permits, I have some ideas for a free-form handwriting recognition engine for Linux that I would like to at least prototype (the currently available options, for example as in the Nokia 770/800, are proprietary). And I'd love to have a simple softsynth and sequencer combination available on the Neo for sketching out musical ideas while traveling.<br />
<br />
My intellectual property law practice is online at [http://www.wixonlaw.com]<br />
<br />
== Current Projects ==<br />
<br />
'''Free42''' [http://home.planet.nl/~demun000/thomas_projects/free42/]is an excellent GPL2 RPN calculator by Thomas Okken modeled after the HP42 series of calculators. I have been using it for several years on my VGA PocketPC, and before that on a PalmOS device.<br />
<br />
Unfortunately, there was no bitbake recipe for it in the OE database, so I had to make one. This being my first attempt at such, it might be a bit of an ugly hack, but it works! And it runs beautifully on the Neo. See [http://scap.linuxtogo.org/files/287b2c44ec16c6aece2cb4fbaa66b02d.png].<br />
<br />
I will upload the .bb recipe and patches soon, and I will also submit it to the OE people upstream for inclusion into their metadata package.<br />
<br />
'''Xournal''' [http://xournal.sourceforge.net] is a very nice scribble-notes package inspired by the Microsoft Journal application provided with Tablet PC versions of Windows. It uses a vector-based ink model and supports multi-colored ink, different kinds of erasers, highlighters, and (in the new version) typed text. It runs very well on the desktop, and marginally well on the Neo at this time, but with some fine-tuning and user-interface consolidation I think it will be a very useful addition to our suite of applications. I will be working on it in the coming days.<br />
<br />
'''Notecase''' [http://notecase.sourceforge.net] is a hierarchical text note manager with rich text formatting capabilities. It already runs well on the Linux desktop, the Windows desktop, and on the linux-based Zauruses. There's a .bb recipe for an old version of Notecase in the OE metadata, and in the coming days I will be bringing that up to date and tweaking the user interface for small-screen devices such as the Neo.<br />
<br />
'''Password Safe''' - Unless someone beats me to it, I would like to implement or port an encrypted password safe for the Neo, preferably one that is able to exchange data with both a Linux desktop application and a Windows desktop application. A good candidate for this would be '''KeePass''' and '''KeePassX''' but I need to investigate alternatives.<br />
<br />
== Upcoming Projects ==<br />
<br />
'''Handwriting Recognition''' - Handwriting recognition does pretty well these days, both on the Windows platform (XP Tablet PC Edition and Vista), and on Mac OSX (Inkwell, I believe it is called, which is based on work originally done for the Newton). Even Microsoft PocketPC platform has reasonably good recognition (through the Calligrapher third-party application, which Microsoft has licensed in an older version as the Transcriber built into Windows Mobile).<br />
<br />
The Nokia 770/800 apparently has a handwriting recognition engine that is proprietary, without source available.<br />
<br />
I would love to see a free handwriting recognition engine that is unencumbered by commercial license restrictions and patents, and can be used with OpenMoko. With my background in mathematics and natural language processing (which I had the privilege to work on at Xerox PARC some years ago), I have some ideas on how to go about this in a relatively "processor-light" manner.<br />
<br />
This will be a spare-time project at best, so it might not see the light of day for quite a while.<br />
<br />
'''Music Platform''' - I had a General Midi sound generator that attached to my ancient Palm Vx, and a rudimentary step sequencer to go with it. It was polyphonic and multitimbral, but it wasn't really useful for anything more than skething out ideas because of the constraints of the old PalmOS 3.x user interface. But it was a load of fun, and useful within its constraints, so I would love to see something like this available in the OpenMoko project.<br />
<br />
This is another project that might take a long while to come to fruition, but it is one I have had in mind for a while.</div>Quicksandhttp://wiki.openmoko.org/wiki/OpenMoko2007.2OpenMoko2007.22007-09-04T17:07:43Z<p>Quicksand: /* Updating your image */</p>
<hr />
<div>'''OM 2007.2''' is the second version of the OpenMoko distribution. Development began on 2007-07-26.<br />
<br />
Goals of the new version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the 1st generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.<br />
<br />
An official announcement was made by Sean Moss-Pultz on August 20:<br />
* http://lists.openmoko.org/pipermail/announce/2007-August/000018.html<br />
<br />
(Initially this was named OM-2008 in SVN but renamed shortly after that.)<br />
<br />
==FAQ==<br />
<br />
=== Q: What are differences between 2007.1 and 2007.2? ===<br />
<br />
* UI redesigned for small and recessed screen<br />
* Simplified visuals for performance<br />
* Simplified UI<br />
* More interactions including finger scrolling<br />
* [[Today|openmoko-today]] rewritten; supports AUX and POWER buttons for navigation<br />
* Updated upstream packages<br />
<br />
=== Q: Where to get snapshot images? ===<br />
<br />
* [[OpenMoko2007.2#Pre-built_snapshot_images|Unofficial images]] listed at the bottom of this article<br />
<br />
* Official snapshots and ipkg repository:<br />
** http://buildhost.openmoko.org/snapshots/2007.08/<br />
<br />
=== Q: Where are official releases? ===<br />
<br />
No official releases yet, just official snapshots. The first release is targetted for October, 2007.<br />
<br />
=== Q: My mrxvt (terminal) fonts are huge. ===<br />
<br />
Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:<br />
#define MIN_XFT_FONT_SIZE (2)<br />
and rebuild mrxvt & openmoko-devel-image.<br />
<br />
End edit /etc/mrxvt/mrxvt.conf<br />
Mrxvt.xftSize: 4<br />
Mrxvt.xftHint: 1<br />
<br />
==Building 2007.2==<br />
<br />
=== How to build ===<br />
<br />
The MokoMakefile is now able to build OM-2007.2 images. If you use this new version of the MokoMakefile, you can ignore everything below and just continue building OM-2007.2 in the same way that you previously built images (i.e. according to http://wiki.openmoko.org/wiki/MokoMakefile). Make sure you set the generation correctly at the top of the file.<br />
<br />
Follow the [http://www.openembedded.org/wiki/GettingStarted getting started] steps of OpenEmbedded. It is suggested to use Bitbake 1.8.8 at least.<br />
<br />
Put the following in your local.conf<br />
<br />
BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"<br />
<br />
MACHINE = "fic-gta01"<br />
DISTRO = "openmoko"<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"<br />
<br />
Replace "${HOME}/oe" with the path to where your "org.openembeded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.<br />
<br />
Run ''bitbake <package name>'' (e.g. openmoko-devel-image).<br />
<br />
=== Build issues ===<br />
<br />
==== Wrong certificate ====<br />
You may get something like this while the bitbake recipes are parsed:<br />
<br />
Error validating server certificate for 'https://libw100.svn.sf.net:443':<br />
- The certificate hostname does not match.<br />
Certificate information:<br />
- Hostname: *.svn.sourceforge.net<br />
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT<br />
- Issuer: Equifax Secure Certificate Authority, Equifax, US<br />
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e<br />
<br />
That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.<br />
<br />
==== openmoko-libs FTBFS ====<br />
Some applications have not been fully modified to build with the new libraries of OpenMoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unneccessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:<br />
<br />
.<br />
.<br />
.<br />
openmoko-terminal \<br />
matchbox-panel-2 \<br />
matchbox-panel-2-applets \<br />
matchbox-applet-inputmanager \<br />
# openmoko-appmanager \<br />
matchbox-keyboard \<br />
matchbox-stroke \<br />
openmoko-keyboard \<br />
.<br />
.<br />
.<br />
<br />
Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphicall terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.<br />
<br />
<br />
==== gtk+ fails building w/ gtkcombobox.c ====<br />
<br />
If you get these errors:<br />
<br />
gtkcombobox.c: In function 'gtk_combo_box_size_request':<br />
gtkcombobox.c:1859: warning: unused variable 'font_desc'<br />
gtkcombobox.c:1858: warning: unused variable 'metrics'<br />
gtkcombobox.c:1857: warning: unused variable 'context'<br />
gtkcombobox.c:1855: warning: unused variable 'arrow_size'<br />
gtkcombobox.c:1854: warning: unused variable 'font_size'<br />
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':<br />
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)<br />
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once<br />
gtkcombobox.c:1962: error: for each function it appears in.)<br />
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)<br />
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)<br />
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)<br />
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function) <br />
<br />
Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:<br />
<br />
Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )<br />
<br />
--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200<br />
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200<br />
@@ -1948,6 +1948,12 @@<br />
gtk_combo_box_size_allocate (GtkWidget *widget,<br />
GtkAllocation *allocation)<br />
{<br />
+ gint font_size;<br />
+ gint arrow_size;<br />
+ PangoContext *context;<br />
+ PangoFontMetrics *metrics;<br />
+ PangoFontDescription *font_desc;<br />
+<br />
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);<br />
gint focus_width, focus_pad;<br />
GtkAllocation child;<br />
<br />
<br />
==== Building glibc fails with a segfault in QEMU ====<br />
<br />
If your build aborts and you see something like this:<br />
<br />
NOTE: package glibc-2.5: started<br />
NOTE: package glibc-2.5-r6: task do_package: started<br />
NOTE: preparing tree for binary locale generation<br />
NOTE: generating locale en_US (UTF-8)<br />
qemu: uncaught target signal 11 (Segmentation fault) - exiting<br />
<br />
...<br />
<br />
NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.<br />
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed<br />
<br />
Try editing your local.conf file. Change:<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
<br />
to<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "0"<br />
<br />
and restart the build. This may have some effect on internationalization (you will see a warning indicating that), but at least the build will continue. Thanks to rwhitby for the tip.<br />
<br />
Alternatively, as suggested by XorA in #openmoko, if you are running a 64-bit host distribution, try forcing a different QEMU rev, also in local.conf:<br />
<br />
PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"<br />
SRCDATE_qemu-native = 20070701<br />
<br />
<br />
==== libxml2-native fails with xmlCatalogPtr errors ====<br />
<br />
Go to your build/tmp/work/i686-linux/libxml2-native-2.6.29-r1/libxml2-2.6.29/include/libxml/ directory and patch xmlversion.h with the following:<br />
<br />
--- xmlversion.h 2007-08-17 10:45:42.000000000 +0100<br />
+++ xmlversion.h 2007-08-17 10:51:36.000000000 +0100<br />
@@ -219,7 +219,7 @@<br />
*<br />
* Whether the Catalog support is configured in<br />
*/<br />
-#if 0<br />
+#if 1<br />
#define LIBXML_CATALOG_ENABLED<br />
#endif<br />
<br />
On my system the libxml2-native-2.6.29-r1 directory is in a directory named i686-linux, yours may be different. I believe this patch to be a workaround to make libxml2-native build. I am not yet sure what the consequences of enabling XML catalogue support are.<br />
<br />
<br />
<br />
<br />
== Pre-built snapshot images ==<br />
* http://ipkg.nslu2-linux.org/feeds/openmoko/images/<br />
<br />
* http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/fic-gta01/<br />
<br />
* http://buildhost.openmoko.org/snapshots/2007.08/ (Official snapshots and ipkg repository)<br />
<br />
[[Category:OpenMoko2007.2| ]]<br />
<br />
<br />
== Updating your image ==<br />
<br />
Now that you have a functional 2007.2 image on your Neo, you will want to keep it updated. Fortunately, ipkg is already set up to pull updated packages from the openmoko buildhost.<br />
<br />
On the phone, in the terminal (or via ssh), if you have a live internet connection and DNS resolution set up in /etc/resolv.conf:<br />
<br />
ipkg update && ipkg upgrade<br />
<br />
will bring your installed packages up to the most recent versions. Also have a look at alternative/additional ipkg sources at [[repositories]].<br />
<br />
If you are also building your own images and packages, you can also run a simple httpd on your build host and serve your own ipkg files to the Neo.<br />
<br />
On the build host, for example:<br />
<br />
thttpd -d <path_to_moko/tmp/deploy/glibc/ipk> -p 8080<br />
<br />
will serve your packages on port 8080.<br />
<br />
Then, on the neo, make a new file at /etc/ipkg/local-feed.conf with these contents:<br />
<br />
src/gz local-all http://192.168.0.200:8080/all<br />
src/gz local-armv4t http://192.168.0.200:8080/armv4t<br />
src/gz local-fic-gta01 http://192.168.0.200:8080/fic-gta01<br />
<br />
and ipkg on the Neo (update-upgrade) will pick up files from your local build host's repository (assuming its IP address is 192.168.0.200, as is default in the [[USB Networking]] setup) in addition to the openmoko buildhost.<br />
<br />
Or better yet, change the 192.168.0.200:8080 addresses above to the eth0 IP address of your build machine (instead of the usb0 IP address), and then you can access your local repository with your Neo plugged into any machine on your local net, or even via bluetooth.<br />
<br />
Also if you are building your own packages or packages from the OE database that aren't part of OpenMoko by default, you can install those packages as follows.<br />
<br />
On the build host:<br />
<br />
bitbake <name_of_package><br />
bitbake -crebuild package-index<br />
<br />
Then on the Neo:<br />
<br />
ipkg update<br />
ipkg install <name_of_package><br />
<br />
The new package might not show up in the program menu until you reboot or restart X.</div>Quicksandhttp://wiki.openmoko.org/wiki/Neo_1973_and_WindowsNeo 1973 and Windows2007-08-30T20:46:34Z<p>Quicksand: /* USB Ethernet emulation */</p>
<hr />
<div>This page tries to collect some information on how to use your Neo1973 together with a computer running a Microsoft(R) Windows(TM) series operating system.<br />
<br />
Please note that this is not really supported, and that the OpenMoko developers themselves only use Linux for testing.<br />
<br />
== Connecting to the phone ==<br />
<br />
=== Bluetooth connection ===<br />
<br />
How to connect to Windows XP via Bluetooth is described here: [[Manually_using_Bluetooth#Bluetooth_networking_with_a_Windows_XP_system]]<br />
<br />
=== USB Ethernet emulation ===<br />
{{note|As of Kernel 2.6.22.5-moko11, USB RNDIS networking ''finally works'' in Windows XP using the procedure described below.}}<br />
<br />
# Download http://privat.wmo.de/~c_schweers/NeoRndis.inf to somewhere convenient on your Windows machine.<br />
# Connect the Neo1973 USB port to the Windows machine, using a standard USB-A to USB-mini-B cable.<br />
# Assuming the new drivers have been installed as above, Windows should detect the Neo1973 and prompt you for a driver for the USB device. Select to specify your own driver, and then choose the NeoRndis.inf file you downloaded earlier. This file tells Windows XP to use its own built-in RNDIS driver for the device.<br />
# Windows may complain of "reduced network connectivity". This is because it expects to be able to get an address automatically from the Neo1973 and it doesn't provide one in the default setup. To fix this, see the next step.<br />
# Go into the Windows network configuration for the new USB networking adapter and set the IP address of the interface to 192.168.0.200.<br />
<br />
You should now be able to connect to your Neo1973 on 192.168.0.202.<br />
<br />
Further references:<br />
* http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx<br />
* http://maemo.org/maemowiki/USBnetworkingWinXP<br />
* http://docwiki.gumstix.org/Setting_up_USBnet<br />
* http://handhelds.org/moin/moin.cgi/WindowsXpUsbNetworkHowTo<br />
<br />
[[Category:Documentation]]<br />
[[Category:Guides]]</div>Quicksandhttp://wiki.openmoko.org/wiki/Neo_1973_and_WindowsNeo 1973 and Windows2007-08-30T20:17:35Z<p>Quicksand: /* USB Ethernet emulation */</p>
<hr />
<div>This page tries to collect some information on how to use your Neo1973 together with a computer running a Microsoft(R) Windows(TM) series operating system.<br />
<br />
Please note that this is not really supported, and that the OpenMoko developers themselves only use Linux for testing.<br />
<br />
== Connecting to the phone ==<br />
<br />
=== Bluetooth connection ===<br />
<br />
How to connect to Windows XP via Bluetooth is described here: [[Manually_using_Bluetooth#Bluetooth_networking_with_a_Windows_XP_system]]<br />
<br />
=== USB Ethernet emulation ===<br />
{{note|As of Kernel 2.6.22.5-moko11, USB RNDIS networking ''finally works'' in Windows XP using the procedure described below.}}<br />
<br />
# Download http://privat.wmo.de/~c_schweers/NeoRndis.inf to somewhere convenient on your Windows machine.<br />
# Connect the Neo1973 USB port to the Windows machine, using a standard USB-A to USB-mini-B cable.<br />
# Assuming the new drivers have been installed as above, Windows should detect the Neo1973 and prompt you for a driver for the USB device. Select to specify your own driver, and then choose the neo1973_ethernet.inf file you downloaded earlier. This file tells Windows XP to use its own built-in RNDIS driver for the device.<br />
# Windows may complain of "reduced network connectivity". This is because it expects to be able to get an address automatically from the Neo1973 and it doesn't provide one in the default setup. To fix this, see the next step.<br />
# Go into the Windows network configuration for the new USB networking adapter and set the IP address of the interface to 192.168.0.200.<br />
<br />
You should now be able to connect to your Neo1973 on 192.168.0.202.<br />
<br />
Further references:<br />
* http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx<br />
* http://maemo.org/maemowiki/USBnetworkingWinXP<br />
* http://docwiki.gumstix.org/Setting_up_USBnet<br />
* http://handhelds.org/moin/moin.cgi/WindowsXpUsbNetworkHowTo<br />
<br />
[[Category:Documentation]]<br />
[[Category:Guides]]</div>Quicksandhttp://wiki.openmoko.org/wiki/OpenMoko2007.2OpenMoko2007.22007-08-25T19:46:10Z<p>Quicksand: /* Updating your image */</p>
<hr />
<div>'''OM 2007.2''' is the second version of the OpenMoko distribution. Development began on 2007-07-26.<br />
<br />
Goals of the new version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the 1st generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.<br />
<br />
An official announcement was made by Sean Moss-Pultz on August 20:<br />
* http://lists.openmoko.org/pipermail/announce/2007-August/000018.html<br />
<br />
(Initially this was named OM-2008 in SVN but renamed shortly after that.)<br />
<br />
==FAQ==<br />
<br />
=== Q: What are differences between 2007.1 and 2007.2? ===<br />
<br />
* UI redesigned for small and recessed screen<br />
* Simplified visuals for performance<br />
* Simplified UI<br />
* More interactions including finger scrolling<br />
* [[Today|openmoko-today]] rewritten; supports AUX and POWER buttons for navigation<br />
* Updated upstream packages<br />
<br />
=== Q: Where to get snapshot images? ===<br />
<br />
* [[OpenMoko2007.2#Pre-built_snapshot_images|Unofficial images]] listed at the bottom of this article<br />
<br />
* Official snapshots and ipkg repository:<br />
** http://buildhost.openmoko.org/snapshots/2007.08/<br />
<br />
=== Q: Where are official releases? ===<br />
<br />
No official releases yet, just official snapshots. The first release is targetted for October, 2007.<br />
<br />
=== Q: My mrxvt (terminal) fonts are huge. ===<br />
<br />
Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:<br />
#define MIN_XFT_FONT_SIZE (2)<br />
and rebuild mrxvt & openmoko-devel-image.<br />
<br />
End edit /etc/mrxvt/mrxvt.conf<br />
Mrxvt.xftSize: 4<br />
Mrxvt.xftHint: 1<br />
<br />
==Building 2007.2==<br />
<br />
=== How to build ===<br />
<br />
The MokoMakefile is now able to build OM-2007.2 images. If you use this new version of the MokoMakefile, you can ignore everything below and just continue building OM-2007.2 in the same way that you previously built images (i.e. according to http://wiki.openmoko.org/wiki/MokoMakefile). Make sure you set the generation correctly at the top of the file.<br />
<br />
Follow the [http://www.openembedded.org/wiki/GettingStarted getting started] steps of OpenEmbedded. It is suggested to use Bitbake 1.8.8 at least.<br />
<br />
Put the following in your local.conf<br />
<br />
BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"<br />
<br />
MACHINE = "fic-gta01"<br />
DISTRO = "openmoko"<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"<br />
<br />
Replace "${HOME}/oe" with the path to where your "org.openembeded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.<br />
<br />
Run ''bitbake <package name>'' (e.g. openmoko-devel-image).<br />
<br />
=== Build issues ===<br />
<br />
==== Wrong certificate ====<br />
You may get something like this while the bitbake recipes are parsed:<br />
<br />
Error validating server certificate for 'https://libw100.svn.sf.net:443':<br />
- The certificate hostname does not match.<br />
Certificate information:<br />
- Hostname: *.svn.sourceforge.net<br />
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT<br />
- Issuer: Equifax Secure Certificate Authority, Equifax, US<br />
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e<br />
<br />
That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.<br />
<br />
==== openmoko-libs FTBFS ====<br />
Some applications have not been fully modified to build with the new libraries of OpenMoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unneccessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:<br />
<br />
.<br />
.<br />
.<br />
openmoko-terminal \<br />
matchbox-panel-2 \<br />
matchbox-panel-2-applets \<br />
matchbox-applet-inputmanager \<br />
# openmoko-appmanager \<br />
matchbox-keyboard \<br />
matchbox-stroke \<br />
openmoko-keyboard \<br />
.<br />
.<br />
.<br />
<br />
Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphicall terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.<br />
<br />
<br />
==== gtk+ fails building w/ gtkcombobox.c ====<br />
<br />
If you get these errors:<br />
<br />
gtkcombobox.c: In function 'gtk_combo_box_size_request':<br />
gtkcombobox.c:1859: warning: unused variable 'font_desc'<br />
gtkcombobox.c:1858: warning: unused variable 'metrics'<br />
gtkcombobox.c:1857: warning: unused variable 'context'<br />
gtkcombobox.c:1855: warning: unused variable 'arrow_size'<br />
gtkcombobox.c:1854: warning: unused variable 'font_size'<br />
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':<br />
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)<br />
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once<br />
gtkcombobox.c:1962: error: for each function it appears in.)<br />
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)<br />
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)<br />
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)<br />
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function) <br />
<br />
Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:<br />
<br />
Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )<br />
<br />
--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200<br />
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200<br />
@@ -1948,6 +1948,12 @@<br />
gtk_combo_box_size_allocate (GtkWidget *widget,<br />
GtkAllocation *allocation)<br />
{<br />
+ gint font_size;<br />
+ gint arrow_size;<br />
+ PangoContext *context;<br />
+ PangoFontMetrics *metrics;<br />
+ PangoFontDescription *font_desc;<br />
+<br />
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);<br />
gint focus_width, focus_pad;<br />
GtkAllocation child;<br />
<br />
<br />
==== Building glibc fails with a segfault in QEMU ====<br />
<br />
If your build aborts and you see something like this:<br />
<br />
NOTE: package glibc-2.5: started<br />
NOTE: package glibc-2.5-r6: task do_package: started<br />
NOTE: preparing tree for binary locale generation<br />
NOTE: generating locale en_US (UTF-8)<br />
qemu: uncaught target signal 11 (Segmentation fault) - exiting<br />
<br />
...<br />
<br />
NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.<br />
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed<br />
<br />
Try editing your local.conf file. Change:<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
<br />
to<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "0"<br />
<br />
and restart the build. This may have some effect on internationalization (you will see a warning indicating that), but at least the build will continue. Thanks to rwhitby for the tip.<br />
<br />
Alternatively, as suggested by XorA in #openmoko, if you are running a 64-bit host distribution, try forcing a different QEMU rev, also in local.conf:<br />
<br />
PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"<br />
SRCDATE_qemu-native = 20070701<br />
<br />
<br />
==== libxml2-native fails with xmlCatalogPtr errors ====<br />
<br />
Go to your build/tmp/work/i686-linux/libxml2-native-2.6.29-r1/libxml2-2.6.29/include/libxml/ directory and patch xmlversion.h with the following:<br />
<br />
--- xmlversion.h 2007-08-17 10:45:42.000000000 +0100<br />
+++ xmlversion.h 2007-08-17 10:51:36.000000000 +0100<br />
@@ -219,7 +219,7 @@<br />
*<br />
* Whether the Catalog support is configured in<br />
*/<br />
-#if 0<br />
+#if 1<br />
#define LIBXML_CATALOG_ENABLED<br />
#endif<br />
<br />
On my system the libxml2-native-2.6.29-r1 directory is in a directory named i686-linux, yours may be different. I believe this patch to be a workaround to make libxml2-native build. I am not yet sure what the consequences of enabling XML catalogue support are.<br />
<br />
<br />
<br />
<br />
== Pre-built snapshot images ==<br />
* http://ipkg.nslu2-linux.org/feeds/openmoko/images/<br />
<br />
* http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/fic-gta01/<br />
<br />
* http://buildhost.openmoko.org/snapshots/2007.08/ (Official snapshots and ipkg repository)<br />
<br />
[[Category:OpenMoko2007.2| ]]<br />
<br />
<br />
== Updating your image ==<br />
<br />
Now that you have a functional 2007.2 image on your Neo, you will want to keep it updated. Fortunately, ipkg is already set up to pull updated packages from the openmoko buildhost.<br />
<br />
On the phone, in the terminal (or via ssh), if you have a live internet connection and DNS resolution set up in /etc/resolv.conf:<br />
<br />
ipkg update && ipkg upgrade<br />
<br />
will bring your installed packages up to the most recent versions.<br />
<br />
If you are also building your own images and packages, you can also run a simple httpd on your build host and serve your own ipkg files to the Neo.<br />
<br />
On the build host, for example:<br />
<br />
thttpd -d <path_to_moko/tmp/deploy/glibc/ipk> -p 8080<br />
<br />
will serve your packages on port 8080.<br />
<br />
Then, on the neo, make a new file at /etc/ipkg/local-feed.conf with these contents:<br />
<br />
src/gz local-all http://192.168.0.200:8080/all<br />
src/gz local-armv4t http://192.168.0.200:8080/armv4t<br />
src/gz local-fic-gta01 http://192.168.0.200:8080/fic-gta01<br />
<br />
and ipkg on the Neo (update-upgrade) will pick up files from your local build host's repository (assuming its IP address is 192.168.0.200, as is default in the [[USB Networking]] setup) in addition to the openmoko buildhost.<br />
<br />
Also if you are building your own packages or packages from the OE database that aren't part of OpenMoko by default, you can install those packages as follows.<br />
<br />
On the build host:<br />
<br />
bitbake <name_of_package><br />
bitbake -crebuild package-index<br />
<br />
Then on the Neo:<br />
<br />
ipkg update<br />
ipkg install <name_of_package><br />
<br />
The new package might not show up in the program menu until you reboot or restart X.</div>Quicksandhttp://wiki.openmoko.org/wiki/OpenMoko2007.2OpenMoko2007.22007-08-22T19:47:04Z<p>Quicksand: </p>
<hr />
<div>'''OM 2007.2''' is the second version of the OpenMoko distribution. Development began on 2007-07-26.<br />
<br />
Goals of the new version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the 1st generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.<br />
<br />
An official announcement was made by Sean Moss-Pultz on August 20:<br />
* http://lists.openmoko.org/pipermail/announce/2007-August/000018.html<br />
<br />
(Initially this was named OM-2008 in SVN but renamed shortly after that.)<br />
<br />
==FAQ==<br />
<br />
=== Q: What are differences between 2007.1 and 2007.2? ===<br />
<br />
* UI redesigned for small and recessed screen<br />
* Simplified visuals for performance<br />
* Simplified UI<br />
* More interactions including finger scrolling<br />
* [[Today|openmoko-today]] rewritten; supports AUX and POWER buttons for navigation<br />
* Updated upstream packages<br />
<br />
=== Q: Where to get snapshot images? ===<br />
<br />
* [[OpenMoko2007.2#Pre-built_snapshot_images|Unofficial images]] listed at the bottom of this article<br />
<br />
* Official snapshots and ipkg repository:<br />
** http://buildhost.openmoko.org/snapshots/2007.08/<br />
<br />
=== Q: Where are official releases? ===<br />
<br />
No official releases yet, just official snapshots. The first release is targetted for October, 2007.<br />
<br />
=== Q: My mrxvt (terminal) fonts are huge. ===<br />
<br />
Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:<br />
#define MIN_XFT_FONT_SIZE (2)<br />
and rebuild mrxvt & openmoko-devel-image.<br />
<br />
End edit /etc/mrxvt/mrxvt.conf<br />
Mrxvt.xftSize: 4<br />
Mrxvt.xftHint: 1<br />
<br />
==Building 2007.2==<br />
<br />
=== How to build ===<br />
<br />
The MokoMakefile is now able to build OM-2007.2 images. If you use this new version of the MokoMakefile, you can ignore everything below and just continue building OM-2007.2 in the same way that you previously built images (i.e. according to http://wiki.openmoko.org/wiki/MokoMakefile). Make sure you set the generation correctly at the top of the file.<br />
<br />
'''Please note that this is no official guide on how to build OM-2007.2. I am just making my first steps getting this to compile and think it would be a [http://en.wikipedia.org/wiki/Proprietary_software waste of time] of I keep problems I found for my own. Additionally it would be good if the new distro gets more exposure and testing so less things will break after the official announcement.'''<br />
<br />
Follow the [http://www.openembedded.org/wiki/GettingStarted getting started] steps of OpenEmbedded. Use Bitbake 1.8.6 not a SVN version from the stable branch (otherwise you will get problems with checking out repositories) and the ''org.openembedded.dev'' branch of OE.<br />
<br />
Put the following in your local.conf<br />
<br />
BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"<br />
<br />
MACHINE = "fic-gta01"<br />
DISTRO = "openmoko"<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"<br />
<br />
Replace "${HOME}/oe" with the path to where your "org.openembeded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.<br />
<br />
Run ''bitbake <package name>'' (e.g. openmoko-devel-image).<br />
<br />
=== Build issues ===<br />
<br />
==== Wrong certificate ====<br />
You may get something like this while the bitbake recipes are parsed:<br />
<br />
Error validating server certificate for 'https://libw100.svn.sf.net:443':<br />
- The certificate hostname does not match.<br />
Certificate information:<br />
- Hostname: *.svn.sourceforge.net<br />
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT<br />
- Issuer: Equifax Secure Certificate Authority, Equifax, US<br />
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e<br />
<br />
That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.<br />
<br />
==== openmoko-libs FTBFS ====<br />
Some applications have not been fully modified to build with the new libraries of OpenMoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unneccessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:<br />
<br />
.<br />
.<br />
.<br />
openmoko-terminal \<br />
matchbox-panel-2 \<br />
matchbox-panel-2-applets \<br />
matchbox-applet-inputmanager \<br />
# openmoko-appmanager \<br />
matchbox-keyboard \<br />
matchbox-stroke \<br />
openmoko-keyboard \<br />
.<br />
.<br />
.<br />
<br />
Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphicall terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.<br />
<br />
<br />
==== gtk+ fails building w/ gtkcombobox.c ====<br />
<br />
If you get these errors:<br />
<br />
gtkcombobox.c: In function 'gtk_combo_box_size_request':<br />
gtkcombobox.c:1859: warning: unused variable 'font_desc'<br />
gtkcombobox.c:1858: warning: unused variable 'metrics'<br />
gtkcombobox.c:1857: warning: unused variable 'context'<br />
gtkcombobox.c:1855: warning: unused variable 'arrow_size'<br />
gtkcombobox.c:1854: warning: unused variable 'font_size'<br />
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':<br />
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)<br />
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once<br />
gtkcombobox.c:1962: error: for each function it appears in.)<br />
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)<br />
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)<br />
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)<br />
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function) <br />
<br />
Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:<br />
<br />
Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )<br />
<br />
--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200<br />
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200<br />
@@ -1948,6 +1948,12 @@<br />
gtk_combo_box_size_allocate (GtkWidget *widget,<br />
GtkAllocation *allocation)<br />
{<br />
+ gint font_size;<br />
+ gint arrow_size;<br />
+ PangoContext *context;<br />
+ PangoFontMetrics *metrics;<br />
+ PangoFontDescription *font_desc;<br />
+<br />
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);<br />
gint focus_width, focus_pad;<br />
GtkAllocation child;<br />
<br />
<br />
==== Building glibc fails with a segfault in QEMU ====<br />
<br />
If your build aborts and you see something like this:<br />
<br />
NOTE: package glibc-2.5: started<br />
NOTE: package glibc-2.5-r6: task do_package: started<br />
NOTE: preparing tree for binary locale generation<br />
NOTE: generating locale en_US (UTF-8)<br />
qemu: uncaught target signal 11 (Segmentation fault) - exiting<br />
<br />
...<br />
<br />
NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.<br />
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed<br />
<br />
Try editing your local.conf file. Change:<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
<br />
to<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "0"<br />
<br />
and restart the build. This may have some effect on internationalization (you will see a warning indicating that), but at least the build will continue. Thanks to rwhitby for the tip.<br />
<br />
Alternatively, as suggested by XorA in #openmoko, if you are running a 64-bit host distribution, try forcing a different QEMU rev, also in local.conf:<br />
<br />
PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"<br />
SRCDATE_qemu-native = 20070701<br />
<br />
<br />
==== libxml2-native fails with xmlCatalogPtr errors ====<br />
<br />
Go to your build/tmp/work/i686-linux/libxml2-native-2.6.29-r1/libxml2-2.6.29/include/libxml/ directory and patch xmlversion.h with the following:<br />
<br />
--- xmlversion.h 2007-08-17 10:45:42.000000000 +0100<br />
+++ xmlversion.h 2007-08-17 10:51:36.000000000 +0100<br />
@@ -219,7 +219,7 @@<br />
*<br />
* Whether the Catalog support is configured in<br />
*/<br />
-#if 0<br />
+#if 1<br />
#define LIBXML_CATALOG_ENABLED<br />
#endif<br />
<br />
On my system the libxml2-native-2.6.29-r1 directory is in a directory named i686-linux, yours may be different. I believe this patch to be a workaround to make libxml2-native build. I am not yet sure what the consequences of enabling XML catalogue support are.<br />
<br />
<br />
=== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ===<br />
<br />
'''Note that the normal [[MokoMakefile]] can build OM-2007.2 now, so there is no need to use the procedure below. The nslu2-linux master makefile is designed for building various OE distributions, and is likely to produce something different from the standard OpenMoko images.<br />
'''<br />
<br />
<br />
'''Check that your /bin/sh (ls -l /bin/sh) is not linked to dash rather than bash.''' Using dash will cause you pain. This is true for a standard install of Ubuntu 7.04 (at least when installing from Live CD). If your /bin/sh points to /bin/dash, correct it with (as root):<br />
ln -sf /bin/bash /bin/sh<br />
<br />
Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.<br />
<br />
Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like): <br />
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2<br />
<br />
Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:<br />
wget http://www.nslu2-linux.org/Makefile<br />
<br />
This will make sure you'll have all the required packages:<br />
sudo apt-get install \<br />
autoconf automake automake1.9 \<br />
bison \<br />
ccache cogito \<br />
cvs \<br />
diffstat \<br />
docbook \<br />
flex \<br />
gcc g++ gawk gcj gettext git-core \<br />
help2man \<br />
libc6-dev libglib2.0-dev libtool libxext-dev\<br />
m4 make \<br />
patch pkg-config \<br />
python python-dev python2.4 python2.4-dev python-psyco \<br />
sed \<br />
sharutils \<br />
texinfo texi2html \<br />
unzip \<br />
subversion \<br />
sysutils \<br />
texinfo \<br />
bzip2<br />
<br />
Ubuntu 7.04 comes with monotone 0.31. You could just go with that and do a mtn db migrate but this takes hours so the easier way would be to download a suitable mtn db from http://www.openembedded.org/snapshots/ and use this.<br />
mkdir -p monotone<br />
wget http://www.openembedded.org/snapshots/\<br />
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2<br />
bunzip2 monotone/nslu2-linux.mtn.bz2<br />
<br />
If you're using MokoMakefile for building OM2007.1 you probably have fresh OE.mtn for version 0.31 already downloaded. So you can just make symlink to the OE.mtn in your OM2007.1 build directory.<br />
<br />
(current directory(pwd) is /path/to/OM2007.2)<br />
ln -s /path/to/OM2007.1/OE.mtn monotone/nslu2-linux.mtn<br />
<br />
To save even more bandwith you can also use already donwloaded source files from OM2007.1. Just make a symlink to OM2007.1 sources directory. Something like this.<br />
<br />
(current directory(pwd) is /path/to/OM2007.2)<br />
ln -s /path/to/OM2007.1/sources downloads<br />
<br />
Go build ;)<br />
make openmoko-devel-image<br />
<br />
<br />
* If you an encounter an error with monotone similar to the following: <br />
<br />
mtn: misuse: database monotone/nslu2-linux.mtn is laid out according to an old schema<br />
<br />
Then you need to upgrade nslu2-linux.mtn Use the following command:<br />
<br />
# mtn --db monotone/nslu2-linux.mtn db migrate<br />
<br />
== Flashing with MokoMakefile ==<br />
Since MokoMakefile has not been adjusted to use the new build layout you cannot use it. As a quick hack to make flashing local built image possible again try this:<br />
<br />
Find the following lines in the MokoMakefile:<br />
<br />
flash-qemu-local: stamps/qemu stamps/openmoko-devel-image<br />
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )<br />
<br />
And replace them with:<br />
<br />
flash-qemu-local: stamps/qemu<br />
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )<br />
<br />
Where you should replace <MY_NEW_BUILD_DIR> with the full path to your build directory (the one where ''conf/local.conf'' lives in). Running the image should work, too. :-)<br />
<br />
With this changes kernel and uboot image are picked up correctly. However the name of the root filesystem image has changed in OM-2007.2 and the current scripts will not pick it up any more. Just edit ''$OM_DIR/build/qemu/openmoko/env'' and change the line saying:<br />
<br />
rootfs_wildcard="openmoko-*.rootfs.jffs2"<br />
<br />
to<br />
<br />
rootfs_wildcard="OpenMoko-*.rootfs.jffs2"<br />
<br />
Now it will work correctly again.<br />
<br />
<br />
== Pre-built snapshot images ==<br />
* http://ipkg.nslu2-linux.org/feeds/openmoko/images/<br />
<br />
* http://buildhost.openmoko.org/OM2007.2/snapshots/2007.08/ (Confirmed working)<br />
<br />
* http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/fic-gta01/<br />
<br />
* http://buildhost.openmoko.org/snapshots/2007.08/ (Official snapshots and ipkg repository)<br />
<br />
[[Category:OpenMoko2007.2| ]]<br />
<br />
<br />
== Updating your image ==<br />
<br />
Now that you have a functional 2007.2 image on your Neo, you will want to keep it updated. Fortunately, ipkg is already set up to pull updated packages from the openmoko buildhost.<br />
<br />
On the phone, in the terminal (or via ssh), if you have a live internet connection and DNS resolution set up in /etc/resolv.conf:<br />
<br />
ipkg update && ipkg upgrade<br />
<br />
will bring your installed packages up to the most recent versions.<br />
<br />
If you are also building your own images and packages, you can also run a simple httpd on your build host and serve your own ipkg files to the Neo.<br />
<br />
On the build host, for example:<br />
<br />
thttpd -d <path_to_moko/tmp/deploy/glibc/ipk> -p 8080<br />
<br />
will serve your packages on port 8080.<br />
<br />
Then, on the neo, make a new file at /etc/ipkg/local-feed.conf with these contents:<br />
<br />
src/gz local-all http://192.168.0.200:8080/all<br />
src/gz local-armv4t http://192.168.0.200:8080/armv4t<br />
src/gz local-fic-gta01 http://192.168.0.200:8080/fic-gta01<br />
<br />
and ipkg on the Neo (update-upgrade) will pick up files from your local build host's repository (assuming its IP address is 192.168.0.200, as is default in the [[USB Networking]] setup) in addition to the openmoko buildhost.<br />
<br />
Also if you are building your own packages or packages from the OE database that aren't part of OpenMoko by default, you can install those packages as follows.<br />
<br />
On the build host:<br />
<br />
bitbake <name_of_package><br />
bitbake -c rebuild openmoko-devel-image<br />
<br />
Then on the Neo:<br />
<br />
ipkg update<br />
ipkg install <name_of_package><br />
<br />
(NB: The local package repository is rebuilt as a consequence of the "rebuild openmoko-devel-image" operation, which also makes another rootfs image. There's probably a way to rebuild the repository without rebuilding the image but I don't know what it is -- please feel free to update.)</div>Quicksandhttp://wiki.openmoko.org/wiki/OpenMoko2007.2OpenMoko2007.22007-08-16T18:14:40Z<p>Quicksand: /* Building glibc fails with a segfault in QEMU */</p>
<hr />
<div>== FAQ ==<br />
=== What is 2007.2? ===<br />
<br />
As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun. <br />
<br />
Goals of the new version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the 1st generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.<br />
<br />
An official announcement is expected soon (Aug 19).<br />
<br />
(Initially this was named OM-2008 in SVN but renamed shortly after that.)<br />
<br />
=== What are differences between 2007.1 and 2007.2? ===<br />
<br />
=== Where to get images? ===<br />
<br />
=== Where are official images? ===<br />
<br />
No official images yet.<br />
<br />
=== My mrxvt (terminal) fonts are huge. ===<br />
<br />
Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:<br />
#define MIN_XFT_FONT_SIZE (2)<br />
and rebuild mrxvt & openmoko-devel-image.<br />
<br />
End edit /etc/mrxvt/mrxvt.conf<br />
Mrxvt.xftSize: 4<br />
Mrxvt.xftHint: 1<br />
<br />
<br />
== How to build ==<br />
'''Please note that this is no official guide on how to build OM-2007.2. I am just making my first steps getting this to compile and think it would be a [http://en.wikipedia.org/wiki/Proprietary_software waste of time] of I keep problems I found for my own. Additionally it would be good if the new distro gets more exposure and testing so less things will break after the official announcement.'''<br />
<br />
Follow the [http://www.openembedded.org/wiki/GettingStarted getting started] steps of OpenEmbedded. Use Bitbake 1.8.6 not a SVN version from the stable branch (otherwise you will get problems with checking out repositories) and the ''org.openembedded.dev'' branch of OE.<br />
<br />
Put the following in your local.conf<br />
<br />
BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"<br />
<br />
MACHINE = "fic-gta01"<br />
DISTRO = "openmoko"<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"<br />
<br />
Replace "${HOME}/oe" with the path to where your "org.openembeded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.<br />
<br />
Run ''bitbake <package name>'' (e.g. openmoko-devel-image).<br />
<br />
Hopefully the MokoMakeFile is soon upgraded to be used for OM-2007.2. Since OpenMoko is not using the overlay any more that makefile should be simpler then. :-)<br />
<br />
=== Build issues ===<br />
<br />
==== Wrong certificate ====<br />
You may get something like this while the bitbake recipes are parsed:<br />
<br />
Error validating server certificate for 'https://libw100.svn.sf.net:443':<br />
- The certificate hostname does not match.<br />
Certificate information:<br />
- Hostname: *.svn.sourceforge.net<br />
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT<br />
- Issuer: Equifax Secure Certificate Authority, Equifax, US<br />
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e<br />
<br />
That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.<br />
<br />
==== openmoko-libs FTBFS ====<br />
Some applications have not been fully modified to build with the new libraries of OpenMoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unneccessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:<br />
<br />
.<br />
.<br />
.<br />
openmoko-terminal \<br />
matchbox-panel-2 \<br />
matchbox-panel-2-applets \<br />
matchbox-applet-inputmanager \<br />
# openmoko-appmanager \<br />
matchbox-keyboard \<br />
matchbox-stroke \<br />
openmoko-keyboard \<br />
.<br />
.<br />
.<br />
<br />
Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphicall terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.<br />
<br />
<br />
==== gtk+ fails building w/ gtkcombobox.c ====<br />
<br />
If you get these errors:<br />
<br />
gtkcombobox.c: In function 'gtk_combo_box_size_request':<br />
gtkcombobox.c:1859: warning: unused variable 'font_desc'<br />
gtkcombobox.c:1858: warning: unused variable 'metrics'<br />
gtkcombobox.c:1857: warning: unused variable 'context'<br />
gtkcombobox.c:1855: warning: unused variable 'arrow_size'<br />
gtkcombobox.c:1854: warning: unused variable 'font_size'<br />
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':<br />
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)<br />
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once<br />
gtkcombobox.c:1962: error: for each function it appears in.)<br />
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)<br />
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)<br />
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)<br />
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function) <br />
<br />
Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:<br />
<br />
Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )<br />
<br />
--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200<br />
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200<br />
@@ -1948,6 +1948,12 @@<br />
gtk_combo_box_size_allocate (GtkWidget *widget,<br />
GtkAllocation *allocation)<br />
{<br />
+ gint font_size;<br />
+ gint arrow_size;<br />
+ PangoContext *context;<br />
+ PangoFontMetrics *metrics;<br />
+ PangoFontDescription *font_desc;<br />
+<br />
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);<br />
gint focus_width, focus_pad;<br />
GtkAllocation child;<br />
<br />
<br />
==== Building glibc fails with a segfault in QEMU ====<br />
<br />
If your build aborts and you see something like this:<br />
<br />
NOTE: package glibc-2.5: started<br />
NOTE: package glibc-2.5-r6: task do_package: started<br />
NOTE: preparing tree for binary locale generation<br />
NOTE: generating locale en_US (UTF-8)<br />
qemu: uncaught target signal 11 (Segmentation fault) - exiting<br />
<br />
...<br />
<br />
NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.<br />
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed<br />
<br />
Try editing your local.conf file. Change:<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
<br />
to<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "0"<br />
<br />
and restart the build. This may have some effect on internationalization (you will see a warning indicating that), but at least the build will continue. Thanks to rwhitby for the tip.<br />
<br />
Alternatively, as suggested by XorA in #openmoko, if you are running a 64-bit host distribution, try forcing a different QEMU rev, also in local.conf:<br />
<br />
PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"<br />
SRCDATE_qemu-native = 20070701<br />
<br />
=== Flashing with MokoMakefile ===<br />
Since MokoMakefile has not been adjusted to use the new build layout you cannot use it. As a quick hack to make flashing local built image possible again try this:<br />
<br />
Find the following lines in the MokoMakefile:<br />
<br />
flash-qemu-local: stamps/qemu stamps/openmoko-devel-image<br />
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )<br />
<br />
And replace them with:<br />
<br />
flash-qemu-local: stamps/qemu<br />
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )<br />
<br />
Where you should replace <MY_NEW_BUILD_DIR> with the full path to your build directory (the one where ''conf/local.conf'' lives in). Running the image should work, too. :-)<br />
<br />
With this changes kernel and uboot image are picked up correctly. However the name of the root filesystem image has changed in OM-2007.2 and the current scripts will not pick it up any more. Just edit ''$OM_DIR/build/qemu/openmoko/env'' and change the line saying:<br />
<br />
rootfs_wildcard="openmoko-*.rootfs.jffs2"<br />
<br />
to<br />
<br />
rootfs_wildcard="OpenMoko-*.rootfs.jffs2"<br />
<br />
Now it will work correctly again.<br />
<br />
== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==<br />
[disclaimer]<br />
<br />
'''Check that your /bin/sh (ls -l /bin/sh) is not linked to dash rather than bash.''' Using dash will cause you pain. This is true for a standard install of Ubuntu 7.04 (at least when installing from Live CD). If your /bin/sh points to /bin/dash, correct it with (as root):<br />
ln -sf /bin/bash /bin/sh<br />
<br />
Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.<br />
<br />
Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like): <br />
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2<br />
<br />
Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:<br />
wget http://www.nslu2-linux.org/Makefile<br />
<br />
This will make sure you'll have all the required packages:<br />
sudo apt-get install \<br />
autoconf automake automake1.9 \<br />
bison \<br />
ccache cogito \<br />
cvs \<br />
diffstat \<br />
docbook \<br />
flex \<br />
gcc g++ gawk gcj gettext git-core \<br />
help2man \<br />
libc6-dev libglib2.0-dev libtool libxext-dev\<br />
m4 make \<br />
patch pkg-config \<br />
python python-dev python2.4 python2.4-dev python-psyco \<br />
sed \<br />
sharutils \<br />
texinfo texi2html \<br />
unzip \<br />
subversion \<br />
sysutils \<br />
texinfo \<br />
bzip2<br />
<br />
Ubuntu 7.04 comes with monotone 0.31. You could just go with that and do a mtn db migrate but this takes hours so the easier way would be to download a suitable mtn db from http://www.openembedded.org/snapshots/ and use this.<br />
mkdir -p monotone<br />
wget http://www.openembedded.org/snapshots/\<br />
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2<br />
bunzip2 monotone/nslu2-linux.mtn.bz2<br />
<br />
If you're using MokoMakefile for building OM2007.1 you probably have fresh OE.mtn for version 0.31 already downloaded. So you can just make symlink to the OE.mtn in your OM2007.1 build directory.<br />
<br />
(current directory(pwd) is /path/to/OM2007.2)<br />
ln -s /path/to/OM2007.1/OE.mtn monotone/nslu2-linux.mtn<br />
<br />
To save even more bandwith you can also use already donwloaded source files from OM2007.1. Just make a symlink to OM2007.1 sources directory. Something like this.<br />
<br />
(current directory(pwd) is /path/to/OM2007.2)<br />
ln -s /path/to/OM2007.1/sources downloads<br />
<br />
Go build ;)<br />
make openmoko-image<br />
<br />
<br />
* If you an encounter an error with monotone similar to the following: <br />
<br />
mtn: misuse: database monotone/nslu2-linux.mtn is laid out according to an old schema<br />
<br />
Then you need to upgrade nslu2-linux.mtn Use the following command:<br />
<br />
# mtn --db monotone/nslu2-linux.mtn db migrate<br />
<br />
== Pre-built snapshot images ==<br />
http://ipkg.nslu2-linux.org/feeds/openmoko/images/<br />
<br />
http://people.openmoko.org/mickey/images/ (Confirmed working)<br />
<br />
http://buildhost.openmoko.org/tmp2/deploy/glibc/images/fic-gta01/<br />
<br />
[[Category:OpenMoko2007.2| ]]</div>Quicksandhttp://wiki.openmoko.org/wiki/OpenMoko2007.2OpenMoko2007.22007-08-15T20:49:56Z<p>Quicksand: /* Building glibc fails with a segfault in QEMU */</p>
<hr />
<div>== FAQ ==<br />
=== What is 2007.2? ===<br />
<br />
As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun. <br />
<br />
Goals of the new version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the 1st generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.<br />
<br />
An official announcement is expected soon (Aug 19).<br />
<br />
(Initially this was named OM-2008 in SVN but renamed shortly after that.)<br />
<br />
=== What are differences between 2007.1 and 2007.2? ===<br />
<br />
=== Where to get images? ===<br />
<br />
=== Where are official images? ===<br />
<br />
No official images yet.<br />
<br />
=== My mrxvt (terminal) fonts are huge. ===<br />
<br />
Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:<br />
#define MIN_XFT_FONT_SIZE (2)<br />
and rebuild mrxvt & openmoko-devel-image.<br />
<br />
End edit /etc/mrxvt/mrxvt.conf<br />
Mrxvt.xftSize: 4<br />
Mrxvt.xftHint: 1<br />
<br />
<br />
== How to build ==<br />
'''Please note that this is no official guide on how to build OM-2007.2. I am just making my first steps getting this to compile and think it would be a [http://en.wikipedia.org/wiki/Proprietary_software waste of time] of I keep problems I found for my own. Additionally it would be good if the new distro gets more exposure and testing so less things will break after the official announcement.'''<br />
<br />
Follow the [http://www.openembedded.org/wiki/GettingStarted getting started] steps of OpenEmbedded. Use Bitbake 1.8.6 not a SVN version from the stable branch (otherwise you will get problems with checking out repositories) and the ''org.openembedded.dev'' branch of OE.<br />
<br />
Put the following in your local.conf<br />
<br />
BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"<br />
<br />
MACHINE = "fic-gta01"<br />
DISTRO = "openmoko"<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"<br />
<br />
Replace "${HOME}/oe" with the path to where your "org.openembeded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.<br />
<br />
Run ''bitbake <package name>'' (e.g. openmoko-devel-image).<br />
<br />
Hopefully the MokoMakeFile is soon upgraded to be used for OM-2007.2. Since OpenMoko is not using the overlay any more that makefile should be simpler then. :-)<br />
<br />
=== Build issues ===<br />
<br />
==== Wrong certificate ====<br />
You may get something like this while the bitbake recipes are parsed:<br />
<br />
Error validating server certificate for 'https://libw100.svn.sf.net:443':<br />
- The certificate hostname does not match.<br />
Certificate information:<br />
- Hostname: *.svn.sourceforge.net<br />
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT<br />
- Issuer: Equifax Secure Certificate Authority, Equifax, US<br />
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e<br />
<br />
That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.<br />
<br />
==== openmoko-libs FTBFS ====<br />
Some applications have not been fully modified to build with the new libraries of OpenMoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unneccessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:<br />
<br />
.<br />
.<br />
.<br />
openmoko-terminal \<br />
matchbox-panel-2 \<br />
matchbox-panel-2-applets \<br />
matchbox-applet-inputmanager \<br />
# openmoko-appmanager \<br />
matchbox-keyboard \<br />
matchbox-stroke \<br />
openmoko-keyboard \<br />
.<br />
.<br />
.<br />
<br />
Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphicall terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.<br />
<br />
<br />
==== gtk+ fails building w/ gtkcombobox.c ====<br />
<br />
If you get these errors:<br />
<br />
gtkcombobox.c: In function 'gtk_combo_box_size_request':<br />
gtkcombobox.c:1859: warning: unused variable 'font_desc'<br />
gtkcombobox.c:1858: warning: unused variable 'metrics'<br />
gtkcombobox.c:1857: warning: unused variable 'context'<br />
gtkcombobox.c:1855: warning: unused variable 'arrow_size'<br />
gtkcombobox.c:1854: warning: unused variable 'font_size'<br />
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':<br />
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)<br />
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once<br />
gtkcombobox.c:1962: error: for each function it appears in.)<br />
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)<br />
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)<br />
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)<br />
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function) <br />
<br />
Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:<br />
<br />
Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )<br />
<br />
--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200<br />
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200<br />
@@ -1948,6 +1948,12 @@<br />
gtk_combo_box_size_allocate (GtkWidget *widget,<br />
GtkAllocation *allocation)<br />
{<br />
+ gint font_size;<br />
+ gint arrow_size;<br />
+ PangoContext *context;<br />
+ PangoFontMetrics *metrics;<br />
+ PangoFontDescription *font_desc;<br />
+<br />
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);<br />
gint focus_width, focus_pad;<br />
GtkAllocation child;<br />
<br />
<br />
==== Building glibc fails with a segfault in QEMU ====<br />
<br />
If your build aborts and you see something like this:<br />
<br />
NOTE: package glibc-2.5: started<br />
NOTE: package glibc-2.5-r6: task do_package: started<br />
NOTE: preparing tree for binary locale generation<br />
NOTE: generating locale en_US (UTF-8)<br />
qemu: uncaught target signal 11 (Segmentation fault) - exiting<br />
<br />
...<br />
<br />
NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.<br />
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed<br />
<br />
Try editing your local.conf file. Change:<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
<br />
to<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "0"<br />
<br />
and restart the build. This may have some effect on internationalization (you will see a warning indicating that), but at least the build will continue. Thanks to rwhitby for the tip.<br />
<br />
=== Flashing with MokoMakefile ===<br />
Since MokoMakefile has not been adjusted to use the new build layout you cannot use it. As a quick hack to make flashing local built image possible again try this:<br />
<br />
Find the following lines in the MokoMakefile:<br />
<br />
flash-qemu-local: stamps/qemu stamps/openmoko-devel-image<br />
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )<br />
<br />
And replace them with:<br />
<br />
flash-qemu-local: stamps/qemu<br />
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )<br />
<br />
Where you should replace <MY_NEW_BUILD_DIR> with the full path to your build directory (the one where ''conf/local.conf'' lives in). Running the image should work, too. :-)<br />
<br />
With this changes kernel and uboot image are picked up correctly. However the name of the root filesystem image has changed in OM-2007.2 and the current scripts will not pick it up any more. Just edit ''$OM_DIR/build/qemu/openmoko/env'' and change the line saying:<br />
<br />
rootfs_wildcard="openmoko-*.rootfs.jffs2"<br />
<br />
to<br />
<br />
rootfs_wildcard="OpenMoko-*.rootfs.jffs2"<br />
<br />
Now it will work correctly again.<br />
<br />
== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==<br />
[disclaimer]<br />
<br />
'''Check that your /bin/sh (ls -l /bin/sh) is not linked to dash rather than bash.''' Using dash will cause you pain. This is true for a standard install of Ubuntu 7.04 (at least when installing from Live CD). If your /bin/sh points to /bin/dash, correct it with (as root):<br />
ln -sf /bin/bash /bin/sh<br />
<br />
Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.<br />
<br />
Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like): <br />
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2<br />
<br />
Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:<br />
wget http://www.nslu2-linux.org/Makefile<br />
<br />
This will make sure you'll have all the required packages:<br />
sudo apt-get install \<br />
autoconf automake automake1.9 \<br />
bison \<br />
ccache cogito \<br />
cvs \<br />
diffstat \<br />
docbook \<br />
flex \<br />
gcc g++ gawk gcj gettext git-core \<br />
help2man \<br />
libc6-dev libglib2.0-dev libtool libxext-dev\<br />
m4 make \<br />
patch pkg-config \<br />
python python-dev python2.4 python2.4-dev python-psyco \<br />
sed \<br />
sharutils \<br />
texinfo texi2html \<br />
unzip \<br />
subversion \<br />
sysutils \<br />
texinfo \<br />
bzip2<br />
<br />
Ubuntu 7.04 comes with monotone 0.31. You could just go with that and do a mtn db migrate but this takes hours so the easier way would be to download a suitable mtn db from http://www.openembedded.org/snapshots/ and use this.<br />
mkdir -p monotone<br />
wget http://www.openembedded.org/snapshots/\<br />
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2<br />
bunzip2 monotone/nslu2-linux.mtn.bz2<br />
<br />
If you're using MokoMakefile for building OM2007.1 you probably have fresh OE.mtn for version 0.31 already downloaded. So you can just make symlink to the OE.mtn in your OM2007.1 build directory.<br />
<br />
(current directory(pwd) is /path/to/OM2007.2)<br />
ln -s /path/to/OM2007.1/OE.mtn monotone/nslu2-linux.mtn<br />
<br />
To save even more bandwith you can also use already donwloaded source files from OM2007.1. Just make a symlink to OM2007.1 sources directory. Something like this.<br />
<br />
(current directory(pwd) is /path/to/OM2007.2)<br />
ln -s /path/to/OM2007.1/sources downloads<br />
<br />
Go build ;)<br />
make openmoko-image<br />
<br />
<br />
* If you an encounter an error with monotone similar to the following: <br />
<br />
mtn: misuse: database monotone/nslu2-linux.mtn is laid out according to an old schema<br />
<br />
Then you need to upgrade nslu2-linux.mtn Use the following command:<br />
<br />
# mtn --db monotone/nslu2-linux.mtn db migrate<br />
<br />
== Pre-built snapshot images ==<br />
http://ipkg.nslu2-linux.org/feeds/openmoko/images/<br />
<br />
http://people.openmoko.org/mickey/images/ (Confirmed working)<br />
<br />
http://buildhost.openmoko.org/tmp2/deploy/glibc/images/fic-gta01/<br />
<br />
[[Category:OpenMoko2007.2| ]]</div>Quicksandhttp://wiki.openmoko.org/wiki/OpenMoko2007.2OpenMoko2007.22007-08-15T20:47:56Z<p>Quicksand: /* Build issues */</p>
<hr />
<div>== FAQ ==<br />
=== What is 2007.2? ===<br />
<br />
As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun. <br />
<br />
Goals of the new version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the 1st generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.<br />
<br />
An official announcement is expected soon (Aug 19).<br />
<br />
(Initially this was named OM-2008 in SVN but renamed shortly after that.)<br />
<br />
=== What are differences between 2007.1 and 2007.2? ===<br />
<br />
=== Where to get images? ===<br />
<br />
=== Where are official images? ===<br />
<br />
No official images yet.<br />
<br />
=== My mrxvt (terminal) fonts are huge. ===<br />
<br />
Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:<br />
#define MIN_XFT_FONT_SIZE (2)<br />
and rebuild mrxvt & openmoko-devel-image.<br />
<br />
End edit /etc/mrxvt/mrxvt.conf<br />
Mrxvt.xftSize: 4<br />
Mrxvt.xftHint: 1<br />
<br />
<br />
== How to build ==<br />
'''Please note that this is no official guide on how to build OM-2007.2. I am just making my first steps getting this to compile and think it would be a [http://en.wikipedia.org/wiki/Proprietary_software waste of time] of I keep problems I found for my own. Additionally it would be good if the new distro gets more exposure and testing so less things will break after the official announcement.'''<br />
<br />
Follow the [http://www.openembedded.org/wiki/GettingStarted getting started] steps of OpenEmbedded. Use Bitbake 1.8.6 not a SVN version from the stable branch (otherwise you will get problems with checking out repositories) and the ''org.openembedded.dev'' branch of OE.<br />
<br />
Put the following in your local.conf<br />
<br />
BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"<br />
<br />
MACHINE = "fic-gta01"<br />
DISTRO = "openmoko"<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"<br />
<br />
Replace "${HOME}/oe" with the path to where your "org.openembeded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.<br />
<br />
Run ''bitbake <package name>'' (e.g. openmoko-devel-image).<br />
<br />
Hopefully the MokoMakeFile is soon upgraded to be used for OM-2007.2. Since OpenMoko is not using the overlay any more that makefile should be simpler then. :-)<br />
<br />
=== Build issues ===<br />
<br />
==== Wrong certificate ====<br />
You may get something like this while the bitbake recipes are parsed:<br />
<br />
Error validating server certificate for 'https://libw100.svn.sf.net:443':<br />
- The certificate hostname does not match.<br />
Certificate information:<br />
- Hostname: *.svn.sourceforge.net<br />
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT<br />
- Issuer: Equifax Secure Certificate Authority, Equifax, US<br />
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e<br />
<br />
That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.<br />
<br />
==== openmoko-libs FTBFS ====<br />
Some applications have not been fully modified to build with the new libraries of OpenMoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unneccessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:<br />
<br />
.<br />
.<br />
.<br />
openmoko-terminal \<br />
matchbox-panel-2 \<br />
matchbox-panel-2-applets \<br />
matchbox-applet-inputmanager \<br />
# openmoko-appmanager \<br />
matchbox-keyboard \<br />
matchbox-stroke \<br />
openmoko-keyboard \<br />
.<br />
.<br />
.<br />
<br />
Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphicall terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.<br />
<br />
<br />
==== gtk+ fails building w/ gtkcombobox.c ====<br />
<br />
If you get these errors:<br />
<br />
gtkcombobox.c: In function 'gtk_combo_box_size_request':<br />
gtkcombobox.c:1859: warning: unused variable 'font_desc'<br />
gtkcombobox.c:1858: warning: unused variable 'metrics'<br />
gtkcombobox.c:1857: warning: unused variable 'context'<br />
gtkcombobox.c:1855: warning: unused variable 'arrow_size'<br />
gtkcombobox.c:1854: warning: unused variable 'font_size'<br />
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':<br />
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)<br />
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once<br />
gtkcombobox.c:1962: error: for each function it appears in.)<br />
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)<br />
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)<br />
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)<br />
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function) <br />
<br />
Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:<br />
<br />
Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )<br />
<br />
--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200<br />
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200<br />
@@ -1948,6 +1948,12 @@<br />
gtk_combo_box_size_allocate (GtkWidget *widget,<br />
GtkAllocation *allocation)<br />
{<br />
+ gint font_size;<br />
+ gint arrow_size;<br />
+ PangoContext *context;<br />
+ PangoFontMetrics *metrics;<br />
+ PangoFontDescription *font_desc;<br />
+<br />
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);<br />
gint focus_width, focus_pad;<br />
GtkAllocation child;<br />
<br />
<br />
==== Building glibc fails with a segfault in QEMU ====<br />
<br />
If your build aborts and you see something like this:<br />
<br />
NOTE: package glibc-2.5: started<br />
NOTE: package glibc-2.5-r6: task do_package: started<br />
NOTE: preparing tree for binary locale generation<br />
NOTE: generating locale en_US (UTF-8)<br />
qemu: uncaught target signal 11 (Segmentation fault) - exiting<br />
<br />
...<br />
<br />
NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.<br />
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed<br />
<br />
Try editing your local.conf file. Change:<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
<br />
to<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "0"<br />
<br />
and restart the build. This may have some effect on internationalization, but at least the build will continue. Thanks to rwhitby for the tip.<br />
<br />
=== Flashing with MokoMakefile ===<br />
Since MokoMakefile has not been adjusted to use the new build layout you cannot use it. As a quick hack to make flashing local built image possible again try this:<br />
<br />
Find the following lines in the MokoMakefile:<br />
<br />
flash-qemu-local: stamps/qemu stamps/openmoko-devel-image<br />
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )<br />
<br />
And replace them with:<br />
<br />
flash-qemu-local: stamps/qemu<br />
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )<br />
<br />
Where you should replace <MY_NEW_BUILD_DIR> with the full path to your build directory (the one where ''conf/local.conf'' lives in). Running the image should work, too. :-)<br />
<br />
With this changes kernel and uboot image are picked up correctly. However the name of the root filesystem image has changed in OM-2007.2 and the current scripts will not pick it up any more. Just edit ''$OM_DIR/build/qemu/openmoko/env'' and change the line saying:<br />
<br />
rootfs_wildcard="openmoko-*.rootfs.jffs2"<br />
<br />
to<br />
<br />
rootfs_wildcard="OpenMoko-*.rootfs.jffs2"<br />
<br />
Now it will work correctly again.<br />
<br />
== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==<br />
[disclaimer]<br />
<br />
'''Check that your /bin/sh (ls -l /bin/sh) is not linked to dash rather than bash.''' Using dash will cause you pain. This is true for a standard install of Ubuntu 7.04 (at least when installing from Live CD). If your /bin/sh points to /bin/dash, correct it with (as root):<br />
ln -sf /bin/bash /bin/sh<br />
<br />
Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.<br />
<br />
Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like): <br />
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2<br />
<br />
Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:<br />
wget http://www.nslu2-linux.org/Makefile<br />
<br />
This will make sure you'll have all the required packages:<br />
sudo apt-get install \<br />
autoconf automake automake1.9 \<br />
bison \<br />
ccache cogito \<br />
cvs \<br />
diffstat \<br />
docbook \<br />
flex \<br />
gcc g++ gawk gcj gettext git-core \<br />
help2man \<br />
libc6-dev libglib2.0-dev libtool libxext-dev\<br />
m4 make \<br />
patch pkg-config \<br />
python python-dev python2.4 python2.4-dev python-psyco \<br />
sed \<br />
sharutils \<br />
texinfo texi2html \<br />
unzip \<br />
subversion \<br />
sysutils \<br />
texinfo \<br />
bzip2<br />
<br />
Ubuntu 7.04 comes with monotone 0.31. You could just go with that and do a mtn db migrate but this takes hours so the easier way would be to download a suitable mtn db from http://www.openembedded.org/snapshots/ and use this.<br />
mkdir -p monotone<br />
wget http://www.openembedded.org/snapshots/\<br />
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2<br />
bunzip2 monotone/nslu2-linux.mtn.bz2<br />
<br />
If you're using MokoMakefile for building OM2007.1 you probably have fresh OE.mtn for version 0.31 already downloaded. So you can just make symlink to the OE.mtn in your OM2007.1 build directory.<br />
<br />
(current directory(pwd) is /path/to/OM2007.2)<br />
ln -s /path/to/OM2007.1/OE.mtn monotone/nslu2-linux.mtn<br />
<br />
To save even more bandwith you can also use already donwloaded source files from OM2007.1. Just make a symlink to OM2007.1 sources directory. Something like this.<br />
<br />
(current directory(pwd) is /path/to/OM2007.2)<br />
ln -s /path/to/OM2007.1/sources downloads<br />
<br />
Go build ;)<br />
make openmoko-image<br />
<br />
<br />
* If you an encounter an error with monotone similar to the following: <br />
<br />
mtn: misuse: database monotone/nslu2-linux.mtn is laid out according to an old schema<br />
<br />
Then you need to upgrade nslu2-linux.mtn Use the following command:<br />
<br />
# mtn --db monotone/nslu2-linux.mtn db migrate<br />
<br />
== Pre-built snapshot images ==<br />
http://ipkg.nslu2-linux.org/feeds/openmoko/images/<br />
<br />
http://people.openmoko.org/mickey/images/ (Confirmed working)<br />
<br />
http://buildhost.openmoko.org/tmp2/deploy/glibc/images/fic-gta01/<br />
<br />
[[Category:OpenMoko2007.2| ]]</div>Quicksand