Openmoko - User contributions [en]

Android

2008-11-04T19:07:05Z

C7: /* Updates */ reordering (newst first)

{{Distributions|Android}}

= Updates =

* 20081104 The first Android-image has been successfully created by Sean McNeil! You can try on your own: [http://people.openmoko.org/sean_mcneil/ android image and kernel] - sms, calling and wifi doesn't work at this time. [http://onlinedev.blogspot.com/2008/11/porting-android-phase-3-done.html ''news-source'']
* 20081029 [[User:Cfriedt]] [http://benno.id.au Benno] has modified Android's build system so that it will output a JFFS2 image instead of YAFFS . Unlike JFFS2, which [http://64.233.169.104/search?q=cache:e8czlAdKTn0J:gentoo-wiki.com/JFFS2/Mounting+gentoo+jffs2&hl=en&ct=clnk&cd=1&gl=ca&client=firefox-a can be mounted read-only from an image], mounting a YAFFS image is not possible unless it's already been written to flash (it complains about the block device being of type '1' and not 'NAND'). JFFS2 also has the benefit that it's a standard OpenMoko image format (See [[Flashing the Neo FreeRunner]] or [[Flashing the Neo 1973]])
* 20081023 [[User:Bricode]] To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw
* 20081022 [[User:Cfriedt]] I was able to 'trivially' compile all of the Android source code without error for the ARMv4T architecture by removing v5TE instructions. Although it will definitely not run anything predictably, at least now that I know the build system will work with a few simple substitutions in build/core/combo/arm-linux.mk. At this point I am able to go ahead and re-implement v5TE instructions as v4T instruction sequences instead (or re-implement entire sections of assembly with hand-optimized v4T instructions).
* 20081021 [[User:Cfriedt]] Android -> FreeRunner updates on my [http://perpetual-notion.blogspot.com/search/label/android blog]
* 20081021 Google released the majority [http://source.android.com/download source code] for the phone under Apache free and open-source [http://source.android.com/license license], with portions covered by other existing licenses, such as the Linux kernel under GPLv2.
* 200810?? [http://www.koolu.com Koolu.com] has announced that they will be '''selling the OpenMoko Freerunner with Android pre-installed''' beginning in November 2008, as well as offering '''free downloads of the Freerunner port of Android''' to existing Freerunner owners. Well-known open-source advocate [http://koolu.com/The-Koolu-Team/maddog.html Jon "maddog" Hall] is CTO and Ambassador for Koolu.

= Introduction =
This page is dedicated to porting the [http://www.android.com Android OS] to the [[Neo 1973]] and [[Neo FreeRunner]] handsets. Since the Android OS was [http://source.android.com/posts/opensource publically released] on 20081021, [http://benno.id.au/blog/2007/11/21/android-neo1973 work] [http://perpetual-notion.blogspot.com/search/label/android is] [http://groups.google.com/group/android-porting currently underway] to port Android to the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

== Goals ==
# Systematically introduce patches for ARMv4T in the Android codebase
# Provide Neo1973 and Neo FreeRunner hardware-dependent patches in the Android codebase, leveraging the work already done by the Openmoko developers, without forcing Android-specific changes upstream
# Provide a useable Android filesystem and kernel on the [[Distributions]] page that conform to current Openmoko installation routines

== Early Attempts ==
As [http://benno.id.au Ben Leslie] had pointed out on his [http://benno.id.au/blog/2007/11/21/android-neo1973 blog] far before the source code was released, [http://www.android.com Android] was originally designed to work with the ARMv5TE [http://en.wikipedia.org/wiki/Instruction_set_architecture instruction set architecture] (ISA), which allows for [http://en.wikipedia.org/wiki/ARM_architecture#DSP_Enhancement_Instructions DSP enhanced instructions]. Contrary to the ARMv5TE ISA, the Neo1973 and FreeRunner handsets both feature an arm920t core, which comply to the ARMv4T ISA.

Before the source code was released, kernel trap handlers were implemented to 'emulate' the ARMv5TE ISA. Although the results worked in many cases, trapping is costly and performance suffered as a result. Moreover, without explicitly knowing which conditions were set by various instructions, such as Thumb Mode execution, the result became nondeterministic.

== Current State ==

With the release of the Android [http://source.android.com source code], the Open Source community is no longer limited to dealing with a binary-only product. The Open Handset Alliance (OHA) has let their source code become their product for everyone enrich and benefit from.

Currently, porting efforts are underway in many circles. Patches should be submitted via the [http://source.android.com/submit-patches official Android channels].

To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw [[User:Bricode]]

[[User:Seanmcneil3|Sean McNeil]] said that he was able to get Androind running (including telephony) in his Freerunner [http://3v1n0.tuxfamily.org/tumblelog/post/368 source].

Ben Leslie mentioned on the android-porting list that he was able to get the 'Android' logo to appear on his Neo 1973.

= How to Help =

== Getting Started ==

You can start by following the instructions to download and build the Android source from scratch. Please see [http://source.android.com/download http://source.android.com/download] and follow the instructions for your architecture.

== Publicize Your Efforts ==

It's generally a good idea to make your efforts known via wiki systems, public mailing lists, forums, and publically open version control systems.

Always take credit for your work but please don't do it in the form of comments. Some code is already hard enough to read without comments polluting the text. The best thing to do is to create a patch and put a header with your information at the top. Collaboration systems such as git might already do this for you (??).

If you create something new and have the ability to designate the license for it, please consider license compatibility issues.

== Porting Strategy ==

* Analysis and leverage of the existing build system
** buid/core/combo/arm-linux.mk
*** -D__ARCH_ARM_4__ -D__ARCH_ARM_4T__
*** -march=armv4t -mcpu=arm920t
** fix various static references to 'armv5'
* Isolating ARMv5TE ISA dependent code
** e.g. grep -n -R -i "${armv5te_isa_pattern}" ~/android
* Abstracting
** ( C/C++ )
*** Use inlined functions / #ifdef statments to implement functions in a portable manner
*** For inlined assembler calls, it's acceptable for now to use generic C code instead, so long as later on we optimize it by hand.
** ( ASM )
*** Proprocessor statements based on ISA / architecture, e.g. #ifdef __ARCH_ARM_5__ ... #endif #ifdef __ARCH_ARM_4__ ... #endif
*** It's highly suggested that preprocessor statements should not be nested (i.e. make them mutually exclusive)
*** Some people have suggested that we should not do #ifdef's based on ARCH or ISA, but rather based on an AndroidConfig.h which would define macros like PLD(...) #ifdef HAVE_ARM_PLD pld #else ... #endif .

For each ARMv5TE instruction, one could potentially
* Implement the instruction using general registers instead of DSP calls (i.e. eabi / softfloat)
* If that is a) nondeterministic, or b) slow, then sections of code need to be analyzed and hand-optimized for the ARMv4T isa

== List of Unsupported Instructions ==

This is a list of opcodes, extracted from the Android source, that are unsupported for ARMv4T compliant processors (specifically the arm920t). The opcodes represent instructions available for ARMv5, ARMv5T, and ARMv5TE architectures, which are not present in the ARMv4T ISA. The list was obtained by exhaustively editing the recompiling the Android source code until it compiled without error.

Please keep in mind, that in some cases, translating these instructions into a sequence of ARMv4T instructions will be impossible and / or result in nondeterministic execution because of
* the requirement of additional context
* the tendencies of certain opcodes to change condition registers that may or may not be present in the arm920t core

=== Opcodes ===

{{scroll box|height=480px|text=
<TABLE BORDER="1">
<TR>
<TH>Opcode</TH>
<TH>Desription</TH>
<TH>[[http://www.arm.com/miscPDFs/14128.pdf PDF]] Page Number</TH>
<TH>C</TH>
<TH>ASM</TH>
</TR>
<TR>
<TH VALIGN="TOP">BLX(1)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>166</TD>
<TD>N/A (Unused in Android)</TD>
<TD>N/A (Unused in Android)</TD>
</TR>
<TR>
<TH VALIGN="TOP">BLX(2)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>168</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_BLX
... (inline asm) ...
#else
... (inline asm with equivalent blx code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_BLX
#define BLX(a) \
blx a
#else
#define BLX(a) \
mov pc,lr \
bx a
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">CLZ</TH>
<TD>Count Leading Zeros</TD>
<TD>175</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_CLZ
... (inline asm) ...
#else
... (inline asm with equivalent clz code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081029
<pre>
#ifdef HAVE_CLZ
#define CLZ(Rd,Rm) \
clz Rd,Rm
#else
#define CLZ(Rd,Rm) \
...
#endif
...
CLZ(Rd,Rm)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">LDRD</TH>
<TD>Load Registers Doubleword</TD>
<TD>200</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_LDRD
... (inline asm) ...
#else
... (inline asm with ldrd substituted) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_LDRD
#define LDRD(a,b) \
ldrd a,b
#else
#define LDRD(a,b) \
...
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">PLD</TH>
<TD>Preload Data</TD>
<TD>240</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_PLD
... (inline asm) ...
#else
... (inline asm with pld removed) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove or substitute with a macro reference such as
<pre>
#ifdef HAVE_PLD
#define PLD(a,b) \
pld a,b
#else
#define PLD(a,b)
#endif
...
PLD(r0,#0)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLA<x><y></TH>
<TD>Signed Multiply-Accumulate</TD>
<TD>291</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAL<x><y></TH>
<TD>Signed Multiply Accumulate Long</TD>
<TD>298</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAW<y></TH>
<TD>Signed Multiply-Accumulate Word</TD>
<TD>302</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMUL<x><y></TH>
<TD>Signed Multiply</TD>
<TD>316</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMULW<y></TH>
<TD>Signed Multiply Word</TD>
<TD>320</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QADD</TH>
<TD>Saturating Add</TD>
<TD>242</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDADD</TH>
<TD>Saturating Double and Add</TD>
<TD>249</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDSUB</TH>
<TD>Saturating Double and Subtract</TD>
<TD>251</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QSUB</TH>
<TD>Saturating Subtract</TD>
<TD>253</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">STRD</TH>
<TD>Store Registers Doubleword</TD>
<TD>349</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_STRD
... (inline asm) ...
#else
... (inline asm without strd) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_STRD
#define STRD(a,b) \
strd a,b
#else
#define STRD(a,b) \
...
#endif
</pre>

</TD>
</TR>
</TABLE>
}}

=== Scanning for Files That Use the ARMv5TE ISA ===

Using the above list of opcodes, one can scan the Android source code for ARMv4T-incompatible instruction sequences.

'''Code:'''
{{scroll box|height=240px|text=
<pre>
#!/bin/sh

# $1 is the android directory

if [ $# -ne 1 ]; then
exit -1
fi

cd "${1}"

opcodes="blx clz ldrd pld smlabb smlabt smlatt
smlal smlawb smlawt smulbb smulbt smultt smulwb
smulwt qadd qdadd qdsub qsub strd"

for op in ${opcodes}; do

echo "* ${op} ====================================="

if [ ! -e .files.${op} ]; then

files="$(grep -R -i "${op} " * 2>/dev/null)"
files="$(echo $files | grep -v "^Binary file" | sed -e 's/:.*//')"
files="$(echo $files| grep -v "CREDIT\|README\|^$kernel/\|.git/$\|$\.txt$$" | sort -u)"

echo "${files}" > .files.${op}

else
files="$(cat .files.${op})"
fi

for fil in ${files}; do
lines="$(grep -n -i "${op} " ${fil} | sed -e 's/:.*//g' )"
lines="$(echo $lines | sed -e 's/ /,/g')"
echo "** ${fil}: lines {${lines}}"
done
done
</pre>
}}

=== Source Files in Android that Use the ARMv5TE ISA ===

The list of files below may or may not be complete. There might also be some assembly code that is generated with a python script (verification?).

{{scroll box|height=150px|text=
* blx =====================================
** bionic/libc/tools/gensyscalls.py: lines {168,186}
** bootloader/legacy/nandwrite/init.S: lines {77}
** bootloader/legacy/usbloader/init.S: lines {95}
** dalvik/vm/arch/arm/CallEABI.S: lines {239}
** dalvik/vm/arch/arm/CallOldABI.S: lines {145}
** development/emulator/qtools/thumbdis.cpp: lines {187,265}
** external/qemu/target-arm/translate.c: lines {1151,1971,2444}
** external/qemu/trace.c: lines {774,1353,1358}
** system/core/libpixelflinger/codeflinger/disassem.c: lines {416}
* clz =====================================
** development/emulator/qtools/armdis.cpp: lines {654}
** external/opencore/codecs_v2/audio/aac/dec/src/pv_normalize.h: lines {67,84}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/norm_l.h: lines {137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/normalize_amr_wb.h: lines {78,95}
** external/opencore/codecs_v2/audio/mp3/dec/src/pvmp3_normalize.h: lines {67,84}
** external/opencore/codecs_v2/video/avc_h264/dec/src/vlc.cpp: lines {23}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/vlc_encode_inline.h: lines {125,162,168,204,218}
** external/qemu/target-arm/translate.c: lines {1247}
** external/skia/libcorecg/Sk64.cpp: lines {340,341,343}
** external/skia/libcorecg/SkMatrix.cpp: lines {500,501}
** external/skia/libsgl/effects/SkColorMatrixFilter.cpp: lines {135}
** external/skia/libsgl/sgl/SkBitmap.cpp: lines {945,946,947}
** external/skia/libsgl/sgl/SkBitmapShader.cpp: lines {32,33,34}
** external/skia/libsgl/sgl/SkGraphics.cpp: lines {429,437}
* ldrd =====================================
** dalvik/vm/mterp/armv5/OP_AGET_WIDE.S: lines {28}
** dalvik/vm/mterp/armv5/OP_IGET_WIDE.S: lines {37}
** dalvik/vm/mterp/armv5/OP_IGET_WIDE_QUICK.S: lines {10}
** dalvik/vm/mterp/armv5/OP_SGET_WIDE.S: lines {17}
** dalvik/vm/mterp/out/InterpAsm-armv5.S: lines {2653,7464,8318,8390}
** system/core/libpixelflinger/rotate90CW_4x4_16v6.S: lines {40,41,42,43}
* pld =====================================
** bionic/libc/arch-arm/bionic/memcmp.S: lines {37,44,45,56,57,107,108,195,196}
** bionic/libc/arch-arm/bionic/memcmp16.S: lines {37,44,45,67,68,116,117,198,199}
** bionic/libc/arch-arm/bionic/memcpy.S: lines {55,56,57,145,266,293,320}
** bionic/libc/arch-arm/bionic/strlen.c: lines {59,65}
** bionic/libc/kernel/arch-arm/asm/arch/irqs.h: lines {162}
** external/elfutils/src/Makefile: lines {243}
** external/elfutils/src/Makefile.am: lines {32}
** external/elfutils/src/Makefile.in: lines {243}
** external/jpeg/jidctfst.S: lines {69,235,247}
** external/qemu/target-arm/translate.c: lines {1149}
** system/core/libpixelflinger/codeflinger/ARMAssembler.cpp: lines {368}
** system/core/libpixelflinger/codeflinger/ARMAssemblerInterface.cpp: lines {104,108,117}
** system/core/libpixelflinger/t32cb16blend.S: lines {111,112,134,143}
* smlabb =====================================
** external/jpeg/jidctfst.S: lines {110,115,155,156}
** external/neven/Embedded/common/src/b_BasicEm/Math.c: lines {584,589}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {147,166}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {120,129}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {514,533}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {418,429}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {202}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {250}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h: lines {119,155,167,278,326,341}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h: lines {178,225,437,517}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {405,436}
* smlabt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {184}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {138}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h: lines {131,143,294,310}
* smlatt =====================================
** external/neven/Embedded/common/src/b_BasicEm/Math.c: lines {585,590}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {157}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {441}
* smlal =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4.h: lines {179,223,236,257,267}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4_gcc.h: lines {264,341}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {178,188,198}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9.s: lines {84,90,96,101,109,114,116,118,121,132,138,150,163,165,167,174,176,178}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9_gcc.s: lines {73,79,86,90,98,103,105,107,110,121,127,139,152,154,156,163,165,167}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.asm: lines {143,162,178,188,192,199,207,217,225,231,237,241,244}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.s: lines {145,164,180,190,194,201,209,219,227,233,239,243,246}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18_gcc.s: lines {143,162,178,188,192,199,207,217,225,231,237,241,244}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.asm: lines {62,63,66,72,76,77,81,82,85,90,94,97,99,100,103,108,113,114,118,119,122,129,136,137,176,179,183,187,190,193}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.s: lines {67,68,71,77,81,82,86,87,90,95,99,102,104,105,108,113,118,119,123,124,127,134,141,142,181,184,188,192,195,198}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window_gcc.s: lines {65,66,69,75,79,80,84,85,88,93,97,100,102,103,106,111,116,117,121,122,125,132,139,140,179,182,186,190,193,196}
** external/opencore/codecs_v2/audio/mp3/dec/src/pv_mp3dec_fxd_op_arm.h: lines {148}
** external/qemu/trace.c: lines {813}
** frameworks/base/opengl/libagl/iterators.S: lines {66,67}
** frameworks/base/opengl/libagl/matrix.h: lines {67,68,96,126,127,282,283,314,315,316}
* smlawb =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {203,259}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {166,416}
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {93,109}
** frameworks/base/opengl/libagl/matrix.h: lines {163,203}
* smlawt =====================================
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {114}
** frameworks/base/opengl/libagl/matrix.h: lines {162,202,243,244}
* smulbb =====================================
** external/jpeg/jidctfst.S: lines {109,114,151,153}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {79}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {71,81}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {207,251,297,348,361,375,427,440,487}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {199,234,274,314,316,326,367,369,404}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h: lines {121,137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h: lines {123,142}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h: lines {122,140}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h: lines {132,134,138,164,177,191}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h: lines {127,129,150,163}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mult.h: lines {121,141}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {115,139,151,163,189,190,212}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {112,113,164,183,201,218,265}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h: lines {250,457,531}
** external/skia/include/corecg/SkMath.h: lines {170}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {420,462}
** system/core/libpixelflinger/t32cb16blend.S: lines {39,66,74,82}
* smulbt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {115}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {109}
** system/core/libpixelflinger/codeflinger/texturing.cpp: lines {1091}
** system/core/libpixelflinger/t32cb16blend.S: lines {47,55}
* smultt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {131}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {100}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {467}
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {73}
* smulwb =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {221}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {373}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {222}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {283}
** external/opencore/codecs_v2/audio/sbc/enc/src/sbcenc_filter.h: lines {33}
** frameworks/base/opengl/libagl/matrix.h: lines {161,201,242}
* smulwt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {202,240}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {385,415}
* qadd =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {64}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {60}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {130,256}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {128,235}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_add.h: lines {122,137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h: lines {123,145}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {71,102,152,176,192}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {91,115,148,202,234}
** external/openssl/crypto/bn/bn_prime.c: lines {454,455}
* qdadd =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/calc_sbr_synfilterbank.cpp: lines {116,162}
** external/opencore/codecs_v2/audio/aac/dec/src/trans4m_freq_2_time_fxp.cpp: lines {472,494}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {212,356,370,385,435,449}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {200,315,321,331,368,371}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h: lines {122,142}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h: lines {133,136,140,172,186,201}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h: lines {128,131,158,172}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {116}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {184}
* qdsub =====================================
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {302}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {275}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h: lines {124,147}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {140}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {165}
* qsub =====================================
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {167}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {162}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_sub.h: lines {121,138}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {88,127}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {70,133}
* strd =====================================
** dalvik/vm/mterp/armv5/OP_APUT_WIDE.S: lines {31}
** dalvik/vm/mterp/armv5/OP_IPUT_WIDE.S: lines {39}
** dalvik/vm/mterp/armv5/OP_IPUT_WIDE_QUICK.S: lines {14}
** dalvik/vm/mterp/armv5/OP_SPUT_WIDE.S: lines {21}
** dalvik/vm/mterp/out/InterpAsm-armv5.S: lines {2834,7530,8331,8542}
** dalvik/vm/oo/Object.h: lines {589}
** external/opencore/fileformats/avi/parser/include/pv_avifile_streamlist.h: lines {179}
** external/opencore/fileformats/avi/parser/src/pv_avifile_streamlist.cpp: lines {153}
** system/core/libpixelflinger/rotate90CW_4x4_16v6.S: lines {47,52,56,60}
}}

=== Discussion ===
=== Notes ===
The file
<pre>
system/core/libpixelflinger/codeflinger/ARMAssembler.cpp
</pre>

will need special attention. It's responsible for dynamic generation of DSP code.

== Suggestions ==
* [[User:Cfriedt]] 20081024 I'm not sure how feasible this is, given that the [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#SMedia_3362_Documentation_.26_OpenGL_ES_Drivers SMedia 3362 is heavily NDA'd]. However, since the arm920t lacks a floating-point unit / DSP core, is it possible to use the SMedia chip for general-purpose math? This would help in the Android platform, at least, for things like audio and video codecs. Aside from an OpenGL ES driver, OpenMoko documentation for the SMedia would be highly appreciated.

= Important Links =
(Please Update Me)

== Documentation ==
* [http://source.android.com/documentation Android Documentation]
* [http://www.arm.com/documentation/ ARM Documentation], (keywords: armv4t, armv5t, armv5te, arm920t, arm926ej-s)
* [http://www.arm.com/miscPDFs/9658.pdf ARM Assembly Language Programming]
* [http://www.cse.unsw.edu.au/~cs3221/labs/assembler-intro.pdf An Introduction to the GNU Assembler]
* [http://www.heyrick.co.uk/assembler/apcsintro.html ARM Procedure Call Standard], [http://en.wikipedia.org/wiki/Calling_convention#ARM ARM Calling Conventions]

== Instruction Set References ==
* [http://www.arm.com/miscPDFs/14128.pdf ARM Architecture Reference Manual], The definitive ISA documentation
* [http://www.simplemachines.it/doc/QRC0001H_rvct_v2.1_arm.pdf ARM Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.qrc0001l/QRC0001_UAL.pdf ARM and Thumb -2 Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0025b/DVI0025.pdf ARMv4T] (See section 1.4.13)
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0014a/DVI0014A_ARM10T_PO.pdf ARMv5T] (See section 4.16)
* [http://www.arm.com/pdfs/ARM-DSP.pdf ARM DSP Enhanced Instruction Set]
* [http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042c/IHI0042C_aapcs.pdf Procedure Call Standard for the ARM Architecture]

== Hardware Reference ==

* [[Neo1973 Hardware]]
* [[Neo FreeRunner GTA02 Hardware]]

== Communities ==
* [http://source.android.com/discuss Android Public Mailing Lists]
** Specifically, [http://groups.google.com/group/android-porting android-porting]
* [http://lists.openmoko.org/mailman/listinfo OpenMoko Mailing Lists]
** Specifically, [http://lists.openmoko.org/mailman/listinfo/openmoko-kernel openmoko-kernel]
* [http://forum.koolu.org/viewforum.php?f=10 Android on FreeRunner] at KoolU.com
* [[Openmoko Local Groups]]
* [[Openmoko:Community_Portal]]

= See also =

* [[Debug_Board]]

= External Links =

[[Category:Distributions]]

User:Seanmcneil3

2008-11-02T14:54:26Z

C7: /* Binutils 2.18 */ added <pre> for readability

== Android on Freerunner ==

Google has released their open source version of the Android phone software distribution. In order to use it on the Freerunner, a number of patches need to be applied and a compiler with armv4 java exception support needs to be used to compile the software.

== Compiler suite ==

Android is a little picky about the version of gcc compiler. It also requires some java exception support that isn't available for armv4 without a minor modification. The following tools are what I use to build Android:

=== Binutils 2.18 ===

At one time I had some armv5t code that was compiled into Android which would cause the linker to generate these blx instructions which fail on armv4. I'm not sure if this is still necessary, but I still have the following change applied to binutils:

<pre>
diff -urN binutils-2.18-orig/bfd/elf32-arm.c binutils-2.18/bfd/elf32-arm.c 
--- binutils-2.18-orig/bfd/elf32-arm.c 2007-08-07 02:59:23.000000000 +0700 
+++ binutils-2.18/bfd/elf32-arm.c 2008-03-15 11:30:17.000000000 +0700 
@@ -3093,8 +3093,8 @@ 
static void check_use_blx(struct elf32_arm_link_hash_table *globals) 
{ 
if (bfd_elf_get_obj_attr_int (globals->obfd, OBJ_ATTR_PROC, 
- Tag_CPU_arch) > 2) 
- globals->use_blx = 1; 
+ Tag_CPU_arch) >= TAG_CPU_ARCH_V5T) 
+ globals->use_blx = 0; 
} 
 
bfd_boolean 
</pre>

configure --prefix={devel path}/android/cross --target=arm-eabi

=== gcc 4.2.4 with gcc41-java-arm4.patch ===

configure --prefix={devel path}/android/cross --target=arm-eabi --with-arch=armv4t --enable-shared --enable-threads --disable-nls --disable-libmudflap --enable-target-optspace --with-abi=aapcs --enable-multilib --disable-libssp --disable-libstdcxx --enable-languages=c,c++

=== java-6-sun ===

This is the standard Linux package available for most (all?) distributions.

== Patches ==

Coming soon. I've posted a number of them on the devel mailing list so far. Eventually, I expect to provide everything necessary for people to build Android for themselves.

== Images ==

Coming soon.

Openmoko Local Groups: Switzerland

2008-10-29T23:53:56Z

C7: /* OpenExpo'09 Bern */

__NOTOC__
== Upcoming Events ==
=== OpenExpo'09 Bern ===
1/2 april 2009

some ideas:

* community meeting (grill, party?)
* ...

== Past Activities ==
* [http://www.openexpo.ch/openexpo-2008-zuerich OpenExpo'08 Winterthur]
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* Openmoko booth at the OpenExpo'07 Zurich

== Buying Openmoko Neo FreeRunner in Switzerland ==
=== Group Sales ===
[[GroupSales#Switzerland]]
=== Distributors ===
see http://openmoko.com/distributors-europe-switzerland.html

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]
*[[User:DarkAngel|DarkAngel]]
*[[User:Agh|Agh]]
*[[User:Anakron|Anakron]]
*[[User:Nowic|Nowic]]
*[[User:Magbeat|Magbeat]]
*[[User:darktim|darktim]]
*[[User:nickik|nickik]]
*[[User:Skarhand|Skarhand]]
*[[User:mat|mat]]
*[[User:psal|psal]]
*[[User:Tuxfux.ch|Tuxfux.ch]]
*[[User:claude-elrond740|claude-elrond740]]
*[[User:DrYak|DrYak]]
*[[User:bernulli|bernulli]]
*[[User:jecuendet|jecuendet]]
*[[User:fbianco|fbianco]] (Geneva & Valais)
*[[User:dontinelli|dontinelli]]

[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Switzerland

2008-10-29T23:44:12Z

C7: /* Distributors */

__NOTOC__
== Upcoming Events ==
=== OpenExpo'09 Bern ===

== Past Activities ==
* [http://www.openexpo.ch/openexpo-2008-zuerich OpenExpo'08 Winterthur]
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* Openmoko booth at the OpenExpo'07 Zurich

== Buying Openmoko Neo FreeRunner in Switzerland ==
=== Group Sales ===
[[GroupSales#Switzerland]]
=== Distributors ===
see http://openmoko.com/distributors-europe-switzerland.html

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]
*[[User:DarkAngel|DarkAngel]]
*[[User:Agh|Agh]]
*[[User:Anakron|Anakron]]
*[[User:Nowic|Nowic]]
*[[User:Magbeat|Magbeat]]
*[[User:darktim|darktim]]
*[[User:nickik|nickik]]
*[[User:Skarhand|Skarhand]]
*[[User:mat|mat]]
*[[User:psal|psal]]
*[[User:Tuxfux.ch|Tuxfux.ch]]
*[[User:claude-elrond740|claude-elrond740]]
*[[User:DrYak|DrYak]]
*[[User:bernulli|bernulli]]
*[[User:jecuendet|jecuendet]]
*[[User:fbianco|fbianco]] (Geneva & Valais)
*[[User:dontinelli|dontinelli]]

[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Switzerland

2008-10-29T23:43:15Z

C7: some cleanup

__NOTOC__
== Upcoming Events ==
=== OpenExpo'09 Bern ===

== Past Activities ==
* [http://www.openexpo.ch/openexpo-2008-zuerich OpenExpo'08 Winterthur]
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* Openmoko booth at the OpenExpo'07 Zurich

== Buying Openmoko Neo FreeRunner in Switzerland ==
=== Group Sales ===
[[GroupSales#Switzerland]]
=== Distributors ===
[http://openmoko.com/distributors-europe-switzerland.html]

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]
*[[User:DarkAngel|DarkAngel]]
*[[User:Agh|Agh]]
*[[User:Anakron|Anakron]]
*[[User:Nowic|Nowic]]
*[[User:Magbeat|Magbeat]]
*[[User:darktim|darktim]]
*[[User:nickik|nickik]]
*[[User:Skarhand|Skarhand]]
*[[User:mat|mat]]
*[[User:psal|psal]]
*[[User:Tuxfux.ch|Tuxfux.ch]]
*[[User:claude-elrond740|claude-elrond740]]
*[[User:DrYak|DrYak]]
*[[User:bernulli|bernulli]]
*[[User:jecuendet|jecuendet]]
*[[User:fbianco|fbianco]] (Geneva & Valais)
*[[User:dontinelli|dontinelli]]

[[Category:Openmoko Local Groups]]

Android

2008-10-29T23:38:09Z

C7: /* Current State */

{{Distributions|Android}}

= Updates =

* 20081021 [[User:Cfriedt]] Android -> FreeRunner updates on my [http://perpetual-notion.blogspot.com/search/label/android blog]
* 20081022 [[User:Cfriedt]] I was able to 'trivially' compile all of the Android source code without error for the ARMv4T architecture by removing v5TE instructions. Although it will definitely not run anything predictably, at least now that I know the build system will work with a few simple substitutions in build/core/combo/arm-linux.mk. At this point I am able to go ahead and re-implement v5TE instructions as v4T instruction sequences instead (or re-implement entire sections of assembly with hand-optimized v4T instructions).
* 20081023 [[User:Bricode]] To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw
* 20081029 [[User:Cfriedt]] [http://benno.id.au Benno] has modified Android's build system so that it will output a JFFS2 image instead of YAFFS . Unlike JFFS2, which [http://64.233.169.104/search?q=cache:e8czlAdKTn0J:gentoo-wiki.com/JFFS2/Mounting+gentoo+jffs2&hl=en&ct=clnk&cd=1&gl=ca&client=firefox-a can be mounted read-only from an image], mounting a YAFFS image is not possible unless it's already been written to flash (it complains about the block device being of type '1' and not 'NAND'). JFFS2 also has the benefit that it's a standard OpenMoko image format (See [[Flashing the Neo FreeRunner]] or [[Flashing the Neo 1973]])

= Introduction =
This page is dedicated to porting the [http://www.android.com Android OS] to the [[Neo 1973]] and [[Neo FreeRunner]] handsets. Since the Android OS was [http://source.android.com/posts/opensource publically released] on 20081021, [http://benno.id.au/blog/2007/11/21/android-neo1973 work] [http://perpetual-notion.blogspot.com/search/label/android is] [http://groups.google.com/group/android-porting currently underway] to port Android to the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

== Goals ==
# Systematically introduce patches for ARMv4T in the Android codebase
# Provide Neo1973 and Neo FreeRunner hardware-dependent patches in the Android codebase, leveraging the work already done by the Openmoko developers, without forcing Android-specific changes upstream
# Provide a useable Android filesystem and kernel on the [[Distributions]] page that conform to current Openmoko installation routines

== Early Attempts ==
As [http://benno.id.au Ben Leslie] had pointed out on his [http://benno.id.au/blog/2007/11/21/android-neo1973 blog] far before the source code was released, [http://www.android.com Android] was originally designed to work with the ARMv5TE [http://en.wikipedia.org/wiki/Instruction_set_architecture instruction set architecture] (ISA), which allows for [http://en.wikipedia.org/wiki/ARM_architecture#DSP_Enhancement_Instructions DSP enhanced instructions]. Contrary to the ARMv5TE ISA, the Neo1973 and FreeRunner handsets both feature an arm920t core, which comply to the ARMv4T ISA.

Before the source code was released, kernel trap handlers were implemented to 'emulate' the ARMv5TE ISA. Although the results worked in many cases, trapping is costly and performance suffered as a result. Moreover, without explicitly knowing which conditions were set by various instructions, such as Thumb Mode execution, the result became nondeterministic.

== Current State ==

With the release of the Android [http://source.android.com source code], the Open Source community is no longer limited to dealing with a binary-only product. The Open Handset Alliance (OHA) has let their source code become their product for everyone enrich and benefit from.

Currently, porting efforts are underway in many circles. Patches should be submitted via the [http://source.android.com/submit-patches official Android channels].

To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw [[User:Bricode]]

[[User:Seanmcneil3|Sean McNeil]] said that he was able to get Androind running (including telephony) in his Freerunner [http://3v1n0.tuxfamily.org/tumblelog/post/368 source].

Ben Leslie mentioned on the android-porting list that he was able to get the 'Android' logo to appear on his Neo 1973.

= How to Help =

== Getting Started ==

You can start by following the instructions to download and build the Android source from scratch. Please see [http://source.android.com/download http://source.android.com/download] and follow the instructions for your architecture.

== Publicize Your Efforts ==

It's generally a good idea to make your efforts known via wiki systems, public mailing lists, forums, and publically open version control systems.

Always take credit for your work but please don't do it in the form of comments. Some code is already hard enough to read without comments polluting the text. The best thing to do is to create a patch and put a header with your information at the top. Collaboration systems such as git might already do this for you (??).

If you create something new and have the ability to designate the license for it, please consider license compatibility issues.

== Porting Strategy ==

* Analysis and leverage of the existing build system
** buid/core/combo/arm-linux.mk
*** -D__ARCH_ARM_4__ -D__ARCH_ARM_4T__
*** -march=armv4t -mcpu=arm920t
** fix various static references to 'armv5'
* Isolating ARMv5TE ISA dependent code
** e.g. grep -n -R -i "${armv5te_isa_pattern}" ~/android
* Abstracting
** ( C/C++ )
*** Use inlined functions / #ifdef statments to implement functions in a portable manner
*** For inlined assembler calls, it's acceptable for now to use generic C code instead, so long as later on we optimize it by hand.
** ( ASM )
*** Proprocessor statements based on ISA / architecture, e.g. #ifdef __ARCH_ARM_5__ ... #endif #ifdef __ARCH_ARM_4__ ... #endif
*** It's highly suggested that preprocessor statements should not be nested (i.e. make them mutually exclusive)
*** Some people have suggested that we should not do #ifdef's based on ARCH or ISA, but rather based on an AndroidConfig.h which would define macros like PLD(...) #ifdef HAVE_ARM_PLD pld #else ... #endif .

For each ARMv5TE instruction, one could potentially
* Implement the instruction using general registers instead of DSP calls (i.e. eabi / softfloat)
* If that is a) nondeterministic, or b) slow, then sections of code need to be analyzed and hand-optimized for the ARMv4T isa

== List of Unsupported Instructions ==

This is a list of opcodes, extracted from the Android source, that are unsupported for ARMv4T compliant processors (specifically the arm920t). The opcodes represent instructions available for ARMv5, ARMv5T, and ARMv5TE architectures, which are not present in the ARMv4T ISA. The list was obtained by exhaustively editing the recompiling the Android source code until it compiled without error.

Please keep in mind, that in some cases, translating these instructions into a sequence of ARMv4T instructions will be impossible and / or result in nondeterministic execution because of
* the requirement of additional context
* the tendencies of certain opcodes to change condition registers that may or may not be present in the arm920t core

=== Opcodes ===

{{scroll box|height=480px|text=
<TABLE BORDER="1">
<TR>
<TH>Opcode</TH>
<TH>Desription</TH>
<TH>[[http://www.arm.com/miscPDFs/14128.pdf PDF]] Page Number</TH>
<TH>C</TH>
<TH>ASM</TH>
</TR>
<TR>
<TH VALIGN="TOP">BLX(1)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>166</TD>
<TD>N/A (Unused in Android)</TD>
<TD>N/A (Unused in Android)</TD>
</TR>
<TR>
<TH VALIGN="TOP">BLX(2)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>168</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_BLX
... (inline asm) ...
#else
... (inline asm with equivalent blx code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_BLX
#define BLX(a) \
blx a
#else
#define BLX(a) \
mov pc,lr \
bx a
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">CLZ</TH>
<TD>Count Leading Zeros</TD>
<TD>175</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_CLZ
... (inline asm) ...
#else
... (inline asm with equivalent clz code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081029
<pre>
#ifdef HAVE_CLZ
#define CLZ(Rd,Rm) \
clz Rd,Rm
#else
#define CLZ(Rd,Rm) \
...
#endif
...
CLZ(Rd,Rm)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">LDRD</TH>
<TD>Load Registers Doubleword</TD>
<TD>200</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_LDRD
... (inline asm) ...
#else
... (inline asm with ldrd substituted) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_LDRD
#define LDRD(a,b) \
ldrd a,b
#else
#define LDRD(a,b) \
...
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">PLD</TH>
<TD>Preload Data</TD>
<TD>240</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_PLD
... (inline asm) ...
#else
... (inline asm with pld removed) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove or substitute with a macro reference such as
<pre>
#ifdef HAVE_PLD
#define PLD(a,b) \
pld a,b
#else
#define PLD(a,b)
#endif
...
PLD(r0,#0)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLA<x><y></TH>
<TD>Signed Multiply-Accumulate</TD>
<TD>291</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAL<x><y></TH>
<TD>Signed Multiply Accumulate Long</TD>
<TD>298</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAW<y></TH>
<TD>Signed Multiply-Accumulate Word</TD>
<TD>302</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMUL<x><y></TH>
<TD>Signed Multiply</TD>
<TD>316</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMULW<y></TH>
<TD>Signed Multiply Word</TD>
<TD>320</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QADD</TH>
<TD>Saturating Add</TD>
<TD>242</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDADD</TH>
<TD>Saturating Double and Add</TD>
<TD>249</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDSUB</TH>
<TD>Saturating Double and Subtract</TD>
<TD>251</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QSUB</TH>
<TD>Saturating Subtract</TD>
<TD>253</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">STRD</TH>
<TD>Store Registers Doubleword</TD>
<TD>349</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_STRD
... (inline asm) ...
#else
... (inline asm without strd) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_STRD
#define STRD(a,b) \
strd a,b
#else
#define STRD(a,b) \
...
#endif
</pre>

</TD>
</TR>
</TABLE>
}}

=== Scanning for Files That Use the ARMv5TE ISA ===

Using the above list of opcodes, one can scan the Android source code for ARMv4T-incompatible instruction sequences.

'''Code:'''
<pre>
opcodes="blx clz ldrd pld smlabb smlabt smlatt smlal smlawb smlawt smulbb smulbt smull smultt smulwb smulwt qadd qdadd qsub qdsub strd"

opcodePat="$(echo ${opcodes} | sed -e 's/ /\\\|/g')"

fileList="$(grep -R -i "$${opcodePat}$ " * 2>/dev/null | grep -v "^Binary file" | sed -e 's/:.*//' | grep -v "CREDITS\|README\|^$kernel/$\|$\.txt$$" | sort -u)"

for i in ${fileList}; do
echo "* ${i}"
done
</pre>

=== Source Files in Android that Use the ARMv5TE ISA ===

The list of files below may or may not be complete. There might also be some assembly code that is generated with a python script (verification?).

{{scroll box|height=150px|text=
* bionic/libc/arch-arm/bionic/memcmp.S
* bionic/libc/arch-arm/bionic/memcmp16.S
* bionic/libc/arch-arm/bionic/memcpy.S
* bionic/libc/arch-arm/bionic/strlen.c
* bionic/libc/kernel/arch-arm/asm/arch/irqs.h
* bionic/libc/tools/gensyscalls.py
* bootloader/legacy/nandwrite/init.S
* bootloader/legacy/usbloader/init.S
* dalvik/vm/arch/arm/CallEABI.S
* dalvik/vm/arch/arm/CallOldABI.S
* dalvik/vm/mterp/armv5/OP_AGET_WIDE.S
* dalvik/vm/mterp/armv5/OP_APUT_WIDE.S
* dalvik/vm/mterp/armv5/OP_IGET_WIDE.S
* dalvik/vm/mterp/armv5/OP_IGET_WIDE_QUICK.S
* dalvik/vm/mterp/armv5/OP_IPUT_WIDE.S
* dalvik/vm/mterp/armv5/OP_IPUT_WIDE_QUICK.S
* dalvik/vm/mterp/armv5/OP_SGET_WIDE.S
* dalvik/vm/mterp/armv5/OP_SPUT_WIDE.S
* dalvik/vm/mterp/out/InterpAsm-armv5.S
* dalvik/vm/oo/Object.h
* development/emulator/qtools/armdis.cpp
* development/emulator/qtools/thumbdis.cpp
* external/elfutils/src/Makefile
* external/elfutils/src/Makefile.am
* external/elfutils/src/Makefile.in
* external/freetype/include/freetype/config/ftconfig.h
* external/jpeg/jidctfst.S
* external/neven/Embedded/common/src/b_BasicEm/Math.c
* external/opencore/codecs_v2/audio/aac/dec/src/calc_sbr_synfilterbank.cpp
* external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h
* external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4.h
* external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4_gcc.h
* external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h
* external/opencore/codecs_v2/audio/aac/dec/src/pv_normalize.h
* external/opencore/codecs_v2/audio/aac/dec/src/trans4m_freq_2_time_fxp.cpp
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_add.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_sub.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mult.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/norm_l.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/normalize_amr_wb.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_16_gcc.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9_gcc.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.asm
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18_gcc.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.asm
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window_gcc.s
* external/opencore/codecs_v2/audio/mp3/dec/src/pv_mp3dec_fxd_op_arm.h
* external/opencore/codecs_v2/audio/mp3/dec/src/pv_mp3dec_fxd_op_arm_gcc.h
* external/opencore/codecs_v2/audio/mp3/dec/src/pvmp3_normalize.h
* external/opencore/codecs_v2/audio/sbc/enc/src/sbcenc_filter.h
* external/opencore/codecs_v2/video/avc_h264/dec/src/vlc.cpp
* external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h
* external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h
* external/opencore/codecs_v2/video/m4v_h263/enc/src/vlc_encode_inline.h
* external/opencore/fileformats/avi/parser/include/pv_avifile_streamlist.h
* external/opencore/fileformats/avi/parser/src/pv_avifile_streamlist.cpp
* external/openssl/crypto/bn/bn_prime.c
* external/qemu/target-arm/translate.c
* external/qemu/trace.c
* external/skia/include/corecg/SkFixed.h
* external/skia/include/corecg/SkMath.h
* external/skia/libcorecg/Sk64.cpp
* external/skia/libcorecg/SkMatrix.cpp
* external/skia/libsgl/effects/SkColorMatrixFilter.cpp
* external/skia/libsgl/sgl/SkBitmap.cpp
* external/skia/libsgl/sgl/SkBitmapShader.cpp
* external/skia/libsgl/sgl/SkGraphics.cpp
* external/srec/config/en.us/dictionary/c0.6.ok
* frameworks/base/libs/audioflinger/AudioMixer.cpp
* frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp
* frameworks/base/opengl/libagl/iterators.S
* frameworks/base/opengl/libagl/matrix.h
* system/core/include/private/pixelflinger/ggl_fixed.h
* system/core/libpixelflinger/codeflinger/ARMAssembler.cpp
* system/core/libpixelflinger/codeflinger/ARMAssemblerInterface.cpp
* system/core/libpixelflinger/codeflinger/disassem.c
* system/core/libpixelflinger/codeflinger/texturing.cpp
* system/core/libpixelflinger/rotate90CW_4x4_16v6.S
* system/core/libpixelflinger/t32cb16blend.S
}}

=== Discussion ===
=== Notes ===
* (ASM) In order to return from a subroutine, use methods that are known to work from ARMv4T onwards <pre>mov pc,lr ==> bx lr</pre>

== Suggestions ==
* [[User:Cfriedt]] 20081024 I'm not sure how feasible this is, given that the [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#SMedia_3362_Documentation_.26_OpenGL_ES_Drivers SMedia 3362 is heavily NDA'd]. However, since the arm920t lacks a floating-point unit / DSP core, is it possible to use the SMedia chip for general-purpose math? This would help in the Android platform, at least, for things like audio and video codecs. Aside from an OpenGL ES driver, OpenMoko documentation for the SMedia would be highly appreciated.

= Important Links =
(Please Update Me)

== Documentation ==
* [http://source.android.com/documentation Android Documentation]
* [http://www.arm.com/documentation/ ARM Documentation], (keywords: armv4t, armv5t, armv5te, arm920t, arm926ej-s)
* [http://www.arm.com/miscPDFs/9658.pdf ARM Assembly Language Programming]
* [http://www.cse.unsw.edu.au/~cs3221/labs/assembler-intro.pdf An Introduction to the GNU Assembler]
* [http://www.heyrick.co.uk/assembler/apcsintro.html ARM Procedure Call Standard], [http://en.wikipedia.org/wiki/Calling_convention#ARM ARM Calling Conventions]

== Instruction Set References ==
* [http://www.arm.com/miscPDFs/14128.pdf ARM Architecture Reference Manual], The definitive ISA documentation
* [http://www.simplemachines.it/doc/QRC0001H_rvct_v2.1_arm.pdf ARM Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.qrc0001l/QRC0001_UAL.pdf ARM and Thumb -2 Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0025b/DVI0025.pdf ARMv4T] (See section 1.4.13)
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0014a/DVI0014A_ARM10T_PO.pdf ARMv5T] (See section 4.16)
* [http://www.arm.com/pdfs/ARM-DSP.pdf ARM DSP Enhanced Instruction Set]
* [http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042c/IHI0042C_aapcs.pdf Procedure Call Standard for the ARM Architecture]

== Hardware Reference ==

* [[Neo1973 Hardware]]
* [[Neo FreeRunner GTA02 Hardware]]

== Communities ==
* [http://source.android.com/discuss Android Public Mailing Lists]
** Specifically, [http://groups.google.com/group/android-porting android-porting]
* [http://lists.openmoko.org/mailman/listinfo OpenMoko Mailing Lists]
** Specifically, [http://lists.openmoko.org/mailman/listinfo/openmoko-kernel openmoko-kernel]
* [http://forum.koolu.org/viewforum.php?f=10 Android on FreeRunner] at KoolU.com
* [[Openmoko Local Groups]]
* [[Openmoko:Community_Portal]]

= See also =

* [[Debug_Board]]

= External Links =

[[Category:Distributions]]

Openmoko Local Groups: Switzerland

2008-08-12T22:41:09Z

C7: __NOTOC__

__NOTOC__
== Upcoming Events ==
=== OpenExpo 2008 ===
* Booth at the [http://www.openexpo.ch/openexpo-2008-zuerich/ OpenExpo 2008] Winterthur (Zurich) '''24./25. September 2008''' <-- help needed!
* Community Grill proposed after the OpenExpo (25. September?)

Es sind genügend '''Schlafplätze''' während und nach der OpenExpo vorhanden (Pfadiheim Breite). Mehr Infos folgen. Bis dann einfach [[User:C7|Ben]] ankicken. '''Hilfe''' ist übrigens jederzeit mehr als willkommen ;) Vor allem auch am Stand.

==== Wer ist wann am Stand? ====
Diese Tabelle darf gerne noch ergänzt werden ;) Ich denke 3-4 Leute wären optimal. Dann haben wir auch Zeit zwischendurch was Essen zu gehen.

{| class="wikitable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
! !! Mittwoch 24. !! Donnerstag 25.
|-
| Morgen || [[User:C7|Ben]], Andy? || [[User:C7|Ben]], Andy?
|-
| Nachmittag || [[User:C7|Ben]], Andy? || [[User:C7|Ben]], Andy?
|}

== Past Activities ==
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* OpenMoko booth at the OpenExpo'07 Zurich

== Buying Openmoko Neo FreeRunner in Switzerland ==
===Group Sales===
[[GroupSales#Switzerland]]

===Distributors===
If you are interested in getting an OpenMoko in your post box, drop me a mail at jec at jesc dot ch . I'm making a grouped order for Switzerland people.

Website: http://www.jesc.ch/openmoko

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]
*[[User:DarkAngel|DarkAngel]]
*[[User:Agh|Agh]]
*[[User:Anakron|Anakron]]
*[[User:Nowic|Nowic]]
*[[User:Magbeat|Magbeat]]
*[[User:darktim|darktim]]
*[[User:nickik|nickik]]
*[[User:Skarhand|Skarhand]]
*[[User:mat|mat]]
*[[User:psal|psal]]
*[[User:Tuxfux.ch|Tuxfux.ch]]
*[[User:claude-elrond740|claude-elrond740]]
*[[User:DrYak|DrYak]]

[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Switzerland

2008-08-12T17:54:13Z

C7: /* Buying OpenMoko FreeRunner in Switzerland */

== Upcoming Events ==
=== OpenExpo 2008 ===
* Booth at the [http://www.openexpo.ch/openexpo-2008-zuerich/ OpenExpo 2008] Winterthur (Zurich) '''24./25. September 2008''' <-- help needed!
* Community Grill proposed after the OpenExpo (25. September?)

Es sind genügend '''Schlafplätze''' während und nach der OpenExpo vorhanden (Pfadiheim Breite). Mehr Infos folgen. Bis dann einfach [[User:C7|Ben]] ankicken. '''Hilfe''' ist übrigens jederzeit mehr als willkommen ;) Vor allem auch am Stand.

==== Wer ist wann am Stand? ====
Diese Tabelle darf gerne noch ergänzt werden ;) Ich denke 3-4 Leute wären optimal. Dann haben wir auch Zeit zwischendurch was Essen zu gehen.

{| class="wikitable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
! !! Mittwoch 24. !! Donnerstag 25.
|-
| Morgen || [[User:C7|Ben]], Andy? || [[User:C7|Ben]], Andy?
|-
| Nachmittag || [[User:C7|Ben]], Andy? || [[User:C7|Ben]], Andy?
|}

== Past Activities ==
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* OpenMoko booth at the OpenExpo'07 Zurich

== Buying Openmoko Neo FreeRunner in Switzerland ==
===Group Sales===
[[GroupSales#Switzerland]]

===Distributors===
If you are interested in getting an OpenMoko in your post box, drop me a mail at jec at jesc dot ch . I'm making a grouped order for Switzerland people.

Website: http://www.jesc.ch/openmoko

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]
*[[User:DarkAngel|DarkAngel]]
*[[User:Agh|Agh]]
*[[User:Anakron|Anakron]]
*[[User:Nowic|Nowic]]
*[[User:Magbeat|Magbeat]]
*[[User:darktim|darktim]]
*[[User:nickik|nickik]]
*[[User:Skarhand|Skarhand]]
*[[User:mat|mat]]
*[[User:psal|psal]]
*[[User:Tuxfux.ch|Tuxfux.ch]]
*[[User:claude-elrond740|claude-elrond740]]
*[[User:DrYak|DrYak]]

[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Switzerland

2008-08-12T17:51:44Z

C7:

== Upcoming Events ==
=== OpenExpo 2008 ===
* Booth at the [http://www.openexpo.ch/openexpo-2008-zuerich/ OpenExpo 2008] Winterthur (Zurich) '''24./25. September 2008''' <-- help needed!
* Community Grill proposed after the OpenExpo (25. September?)

Es sind genügend '''Schlafplätze''' während und nach der OpenExpo vorhanden (Pfadiheim Breite). Mehr Infos folgen. Bis dann einfach [[User:C7|Ben]] ankicken. '''Hilfe''' ist übrigens jederzeit mehr als willkommen ;) Vor allem auch am Stand.

==== Wer ist wann am Stand? ====
Diese Tabelle darf gerne noch ergänzt werden ;) Ich denke 3-4 Leute wären optimal. Dann haben wir auch Zeit zwischendurch was Essen zu gehen.

{| class="wikitable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
! !! Mittwoch 24. !! Donnerstag 25.
|-
| Morgen || [[User:C7|Ben]], Andy? || [[User:C7|Ben]], Andy?
|-
| Nachmittag || [[User:C7|Ben]], Andy? || [[User:C7|Ben]], Andy?
|}

== Past Activities ==
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* OpenMoko booth at the OpenExpo'07 Zurich

== Buying OpenMoko FreeRunner in Switzerland ==
===Group Sales===
[[GroupSales#Switzerland]]

===Distributors===
If you are interested in getting an OpenMoko in your post box, drop me a mail at jec at jesc dot ch . I'm making a grouped order for Switzerland people.

Website: http://www.jesc.ch/openmoko

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]
*[[User:DarkAngel|DarkAngel]]
*[[User:Agh|Agh]]
*[[User:Anakron|Anakron]]
*[[User:Nowic|Nowic]]
*[[User:Magbeat|Magbeat]]
*[[User:darktim|darktim]]
*[[User:nickik|nickik]]
*[[User:Skarhand|Skarhand]]
*[[User:mat|mat]]
*[[User:psal|psal]]
*[[User:Tuxfux.ch|Tuxfux.ch]]
*[[User:claude-elrond740|claude-elrond740]]
*[[User:DrYak|DrYak]]

[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Switzerland

2008-08-12T17:51:01Z

C7: /* OpenExpo 2008 */ Stand

== Upcoming Events ==
=== OpenExpo 2008 ===
* Booth at the [http://www.openexpo.ch/openexpo-2008-zuerich/ OpenExpo 2008] Winterthur (Zurich) '''24./25. September 2008''' <-- help needed!
* Community Grill proposed after the OpenExpo (25. September?)

Es sind genügend '''Schlafplätze''' während und nach der OpenExpo vorhanden (Pfadiheim Breite). Mehr Infos folgen. Bis dann einfach [[User:C7|Ben]] ankicken. '''Hilfe''' ist übrigens jederzeit mehr als willkommen ;) Vor allem auch am Stand.

==== Wer ist wann am Stand? ====
Diese Tabelle darf gerne noch ergänzt werden ;) Ich denke 3-4 Leute wären optimal. Dann haben wir auch Zeit zwischendurch was Essen zu gehen.

{| class="wikitable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
! !! Mittwoch 24. !! Donnerstag 25.
|-
| Morgen || [[User:C7|Ben]], Andy? || [[User:C7|Ben]], Andy?
|-
| Nachmittag || [[User:C7|Ben]], Andy? || [[User:C7|Ben]], Andy?
|}

== Past Activities ==
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* OpenMoko booth at the OpenExpo'07 Zurich

== Buying OpenMoko FreeRunner in Switzerland ==
===Group Sales===
[[GroupSales#Switzerland]]

===Distributors===
If you are interested in getting an OpenMoko in your post box, drop me a mail at jec at jesc dot ch . I'm making a grouped order for Switzerland people.

Website: http://www.jesc.ch/openmoko

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]
*[[User:DarkAngel|DarkAngel]]
*[[User:Agh|Agh]]
*[[User:Anakron|Anakron]]
*[[User:Nowic|Nowic]]
*[[User:Magbeat|Magbeat]]
*[[User:darktim|darktim]]
*[[User:nickik|nickik]]
*[[User:Skarhand|Skarhand]]
*[[User:mat|mat]]
*[[User:psal|psal]]
*[[User:Tuxfux.ch|Tuxfux.ch]]
*[[User:claude-elrond740|claude-elrond740]]
*[[User:DrYak|DrYak]]

[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Switzerland

2008-08-12T17:32:34Z

C7: some reoarganising

Openmoko Local Groups: Switzerland

2008-08-12T17:29:07Z

C7: removed the "Buying Interest List"

Accelerometer data retrieval

2008-08-09T13:42:16Z

C7: /* Test application */

==Scope==

This document describes a way to access the data provided by the
accelerometers. Furthermore the format of the acquired datastream is explained
in detail. This document does not cover the physical basics of acceleration or
the mathematical details on this subject.

==Axis orientation==

To understand the values provided by the accelerometers it is crucial to
understand how the sensors are oriented. In the following I will refer to the
sensors as first and second sensor. The way to access the data sources of
these two will be described later on in this document.

The Z axis is pointing from the display downwards to to the back of the
openmoko. This applies to both of the sensors.

===Orientation of the first sensor===

To explain the axis orientation I have created some images for easier
understanding.

[[Image:Accelerometer_orientation1.png|Axis orientation of the first accelerometer]]

===Orientation of the second sensor===

In contrast to the first sensor the second one is turned 45 degrees around the
Z axis. See the attached image to get a clue about its orientation.

[[Image:Accelerometer_orientation2.png|Axis orientation of the second accelerometer]]

==Data acquisition==

The information from both of the accelerometers is exported through two
different input event based file mappings. These device nodes can be found at
''/dev/input/event2'' and ''/dev/input/event3''.

The sensor I am refering to as the first one is ''event2''. Therefore the second
one is accessible through the ''event3'' device.

These device nodes can be opened by the default filesystems calls for reading
files. The data can be read from the stream as soon as the sensor measures it.

==Data structure==

To be able to use the measured data it is important to understand the format
in which the data is provided.
The structure of the given data is based on the kernel input event message
system which exports the following data structure:

struct input_event {
struct timeval time;
__u16 type;
__u16 code;
__s32 value;
};

The data is written to the stream message by message. Therefore the minimal
used blocksize is 128 bit (16 byte).

Lets have a look at an example readout of the accelerometer data, divided into
the used sections.

|----- time ------| |type| |code| |-value-|
8c66 4819 721c 0006 0002 0002 03a8 0000
8c66 4819 7222 0006 0000 0000 0000 0000
8c66 4819 99e6 0006 0002 0000 0048 0000
8c66 4819 9a36 0006 0002 0001 0024 0000
8c66 4819 9a50 0006 0002 0002 0396 0000
8c66 4819 9a57 0006 0000 0000 0000 0000

I think the time structure does not need further explaination. A lot more
interesting is the type, code and value part of every message. Lets take a
closer look at these parts.

===Event types===

The types categorize the incoming messages. All possible types can be found in
the kernel sources or include files in ''INCLUDEDIR/linux/input.h''
During the tests with the accelerometers I observed the fact that only two
different message types are used.

;0x00:
:According to ''linux/input.h'' this event is called ''EV_SYN''. It signals the wish to ''syncronize''. Normally this event is used in combination with code 0x00 to mark the send data complete and therefore applyable.

;0x02:
:This event is called ''EV_REL'' and signals ''relative movement''. It is used to transmit the acceleration the sensors encounter.

The definition should not be taken too seriously in this context, because the
data values provided by the accelerometer always represent the absolute
acceleration measured at the given time.

===Event codes===

Both types of event may supply different codes. These codes can be understood
as some kind of further specification about the specified data values

====Syncronization event codes====

The syncronization event may use quite a lot of codes, as ''linux/input.h''
shows. However the only used one seems to be the 0x00 code.

;0x00:
:This code is refered to as SYN_REPORT. It means that the last dataset was completely transmitted. Therefore the before transmitted set of data values can be considered complete. This means if this message is recieved you may process the given data further.

====Relative movement event codes====

The amount of possible codes for this event type is quite big. The only used
ones are the following ones.

;0x00:
:REL_X - Acceleration in x direction

;0x01:
:REL_Y - Acceleration in y direction

;0x02:
:REL_Z - Acceleration in z direction

The X, Y and Z axis are to be understand as defined in the chapter about [[#Axis_orientation|Axis orientation]].

===A typical message block===

A typical message block consists of 3 messages containing the acceleration
data for every of the three axis followed by a syncronization message to
signal the end of the block.

The following example is such a message block with detailed explanation of its
different messages and data sections.

8c66 4819 99e6 0006 0002 0000 0048 0000
|------Time-------| EV_REL REL_X |-Value-|
(Measured acceleration in x axis direction of 72)

8c66 4819 9a36 0006 0002 0001 0024 0000
|------Time-------| EV_REL REL_Y |-Value-|
(Measured acceleration in y axis direction of 36)

8c66 4819 9a50 0006 0002 0002 0396 0000
|------Time-------| EV_REL REL_Z |-Value-|
(Measured acceleration in z axis direction of 918)

8c66 4819 9a57 0006 0000 0000 0000 0000
|------Time-------| EV_SYN SYN_REPORT |-Value-|
(The transmitted data block is complete you may process the given data)

==Test application==

A simple test application written in ruby:
#!/usr/bin/env ruby
x = 0
y = 0
z = 0
File.open("/dev/input/event3") do |f|
while true
event = f.read(16).unpack("llSSl")
time = event[0] + event[1] / 1000000.0
type = event[2]
code = event[3]
value = event[4]
if type == 2
x = value if code == 0
y = value if code == 1
z = value if code == 2
end
if type == 0 && code == 0
sum = Math::sqrt(x*x + y*y + z*z).to_i
printf("%5d %5d %5d %5d\n", x, y, z, sum)
end
end
end

Equivalent version in python:

<pre>
#!/usr/bin/python
import struct
from math import sqrt

x = 0
y = 0
z = 0
secondsensorfile = "/dev/input/event3"
#int, int, short, short, int
fmt = 'iihhi'
#open file in binary mode
in_file = open(secondsensorfile,"rb")
event = in_file.read(16)
while event:
(time1,time2, type, code, value) = \
struct.unpack(fmt,event)
time = time1 + time2 / 1000000

if type == 2:
if code == 0:
x = value
if code == 1:
y = value
if code == 2:
z = value
if type == 0 and code == 0:
sum = int(sqrt(x*x + y*y + z*z))
print x, y, z, sum
event = in_file.read(16)
in_file.close()

</pre>

==External Links==
[[Accelerometer_Fundamentals]]

[http://projects.openmoko.org/projects/gestures/ Openmoko Motion Gestures]

[http://en.wikipedia.org/wiki/Accelerometer Wikipedia - Accelerometer]

[http://dev.borza.ro/demo/Motion-based%20Gesture%20Recognition%20with%20an%20Accelerometer/Paper.pdf Motion-based Gesture Recognition with an Accelerometer - Paper]

[[Category:Hardware]]
[[Category:Accelerometer]]
[[Category:Guides]]

Users Repositories

2008-08-09T13:32:41Z

C7: /* Community repository */ fixed link

Here you can find prebuilt kernels and root file systems.

==Official downloads==

===Recent/latest builds===
* Framework Testing Images (FSO)
:http://downloads.openmoko.org/framework/
* OM2007.2
:http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/neo1973/?C=M;O=D
* OM2007.1 (Obsolete)
:http://buildhost.openmoko.org/OM2007.1/tmp/deploy/images/?C=M;O=D

===Snapshots [http://downloads.openmoko.org/snapshots/]===
* 2007.11 - the latest (2nd Dec) snapshot ([http://lists.openmoko.org/pipermail/community/2007-December/011980.html from Mickey])
:http://downloads.openmoko.org/snapshots/2007.11/images/
* 2007.08 snapshot, as announced by Sean on August 19
:http://downloads.openmoko.org/snapshots/2007.08/images/

===Daily===
* Unstable Daily-builds
:http://buildhost.openmoko.org/daily/

===[[CommunityRepository|Community repository]]===
:http://downloads.openmoko.org/repository/Multiverse/

==Unofficial builds==

=== Angstrom Repository ===

Angstrong is the base distribution of OpenMoko Linux distribution. It contains the basic set of Linux applications and they should be compatible with OpenMoko. [http://www.angstrom-distribution.org/repo/ The repository package listing].

To add the unstable Angstrom feed, update your ''/etc/ipkg/base-feeds.conf'' to include a line:

<pre>
src/gz base http://www.angstrom-distribution.org/feeds/2007/ipk/glibc/armv4t/base/
</pre>

===[[User:ChooseOpen|ChooseOpen]]===
:http://chooseopen.com/openmoko/build/2007.2/?M=D (2007.2)
:http://chooseopen.com/openmoko/build/qtopia/?M=D (Qtopia)

===[[User:Kevin_Dean|Kevin_Dean]]===
:http://downloads.openmoko.org/recommended/ (only gta01)
:Latest recommended [[Snapshot review|snapshot review]]

===[[User:ScaredyCat|ScaredyCat]]===
:http://buildhost.automated.it/OM2007.2/?M=D

ScaredyCat also has a ipkg repository for 2007.2 where e.g. gpe-filemanager and a lot more (e.g. ntpd) can be installed from. On the Neo do:

cd /etc/opkg
wget http://buildhost.automated.it/scaredycat.conf
opkg update
opkg install gpe-filemanager
opkg install gpe-timesheet
opkg install gpe-todo
opkg install mysql
opkg install mtpaint
opkg install sqlite
opkg install ntp
#(you get the idea)
/etc/init.d/xserver-nodm restart # to make the new applications appear in the menu

==='''mwester''' unofficial builds===
:http://moko.mwester.net/

===celtune===
:http://rabenfrost.net/celtune/?C=M;O=D
:http://rabenfrost.net/celtune/ipk/

Celtune offers Standard-Builds (.jffs2, .tar.gz, .bin, .ipk) and several special-images with additional packages (e.g. monster-images,navigation-images,...)
For more info take a look at http://rabenfrost.net/celtune/1-NEWS-WARNING-INFO
You can find images, kernels and packages for other devices too on http://rabenfrost.net/celtune/ (e.g. HTC-Blueangel, Asus730W ...)
A huge number of packages is located at http://rabenfrost.net/celtune/ipk/
Use the following line to add celtune's feed to your neo:
cd /etc/opkg && wget http://rabenfrost.net/celtune/celtune-rabenfrost.conf

If you want to add a link, it would be nice to enforce a standard format of these feeds so that they can be browsed automatically.

[[Category:Openmoko]]

Openmoko Local Groups: Switzerland

2008-08-08T00:46:44Z

C7: /* OpenExpo 2008 */

== Upcoming Events ==
=== OpenExpo 2008 ===
* Booth at the [http://www.openexpo.ch/openexpo-2008-zuerich/ OpenExpo 2008] Winterthur (Zurich) '''24./25. September 2008''' <-- help needed!
* Community Grill proposed after the OpenExpo (25. September?)

Es sind genügend '''Schlafplätze''' während und nach der OpenExpo vorhanden (Pfadiheim Breite). Mehr Infos folgen. Bis dann einfach [[User:C7|Ben]] ankicken. '''Hilfe''' ist übrigens jederzeit mehr als willkommen ;) Vor allem auch am Stand.

== Past Activities ==
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* OpenMoko booth at the OpenExpo'07 Zurich

== NEO FreeRunner (aka GTA02) Group Order ==

[[GroupSales#Switzerland]]
=== Buying Interest List ===

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
! Quantity !! Nick
|-
| 1 || [[User:emonkey|emonkey]]
|-
| 1 || [[User:anthraxx|anthraxx]]
|-
| 1 || [[User:Gr33b|Gr33b]]
|-
| 1 || [[User:Megalomaniac|Megalomaniac]]
|-
| 1 || [[User:toldap|toldap]]
|-
| 1 || [[User:Philgood|Philgood]]
|-
| 1 || [[User:cgjusten|cgjusten]]
|-
| 1 || [[User:DarkAngel|DarkAngel]]
|-
| 1 || [[User:Agh|Agh]]
|-
| 1 || [[User:Anakron|Anakron]]
|-
| 1 || [[User:Onsonic|Onsonic]]
|-
| 1 || [[User:Mat|mat]]
|-
| 1 || [[User:JOn02|Jon02]]
|-
| 3 || [[User:darktim|darktim]]
|-
| 1 || [[User:Skarhand|Skarhand]]
|-
| 1 || [[User:Buz|Buz]]
|-
| 1 || [[User:none|None]]
|-
| 1 || [[User:cimi|cimi]]
|-
| 1 || [[User:jecuendet|jecuendet]]
|-
| 1 || [[User:Sigi|Sigi]]
|}

== Buying OpenMoko FreeRunner in Switzerland ==

If you are interested in getting an OpenMoko in your post box, drop me a mail at jec at jesc dot ch . I'm making a grouped order for Switzerland people.

Website: http://www.jesc.ch/openmoko

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]
*[[User:DarkAngel|DarkAngel]]
*[[User:Agh|Agh]]
*[[User:Anakron|Anakron]]
*[[User:Nowic|Nowic]]
*[[User:Magbeat|Magbeat]]
*[[User:darktim|darktim]]
*[[User:nickik|nickik]]
*[[User:Skarhand|Skarhand]]
*[[User:mat|mat]]
*[[User:psal|psal]]
*[[User:Tuxfux.ch|Tuxfux.ch]]
*[[User:claude-elrond740|claude-elrond740]]
*[[User:DrYak|DrYak]]

[[Category:Openmoko Local Groups]]

User:C7

2008-08-08T00:45:46Z

C7: /* OpenExpo 2008 Winterthur (Zurich), Switzerland */

== Contact ==
* Name: Ben Hagen
* Email: ben.hagen ( at ) ch-open.ch
* IRC: irc.freenode.net #openmoko (nick: C7)

== OpenExpo 2008 Winterthur (Zurich), Switzerland ==

I'm organising the Openmoko booth at the [http://www.openexpo.ch/openexpo-2008-zuerich/ OpenExpo 2008] in Winterthur, Switzerland. Any help welcome ;) More infos [[OpenMoko_Local_Groups: Switzerland#OpenExpo_2008|here]].

User:C7

2008-08-08T00:44:43Z

C7: /* OpenExpo 2008 Winterthur (Zurich), Switzerland */

User:C7

2008-08-08T00:42:00Z

C7: /* Contact */

== Contact ==
* Name: Ben Hagen
* Email: ben.hagen ( at ) ch-open.ch
* IRC: irc.freenode.net #openmoko (nick: C7)

== OpenExpo'08 Bern, Switzerland ==

I'm organising an OpenMoko booth at the [http://www.openexpo.ch/openexpo-2008-bern/ OpenExpo'08] in Bern, Switzerland. Any help welcome ;) More infos [[OpenMoko_Local_Groups: Switzerland|here]].

Openmoko Local Groups: Switzerland

2008-08-08T00:39:24Z

C7: /* Upcoming Events */

== Upcoming Events ==
=== OpenExpo 2008 ===
* Booth at the [http://www.openexpo.ch/openexpo-2008-zuerich/ OpenExpo 2008] Winterthur(Zürich) '''24./25. September 2008''' <-- help needed!
* Community Grill proposed after the OpenExpo (25. September?)

Es sind genügend '''Schlafplätze''' während und nach der OpenExpo vorhanden (Pfadiheim Breite). Mehr Infos folgen. Bis dann einfach [[User:C7|Ben]] ankicken. '''Hilfe''' ist übrigens jederzeit mehr als willkommen ;) Vor allem auch am Stand.

== Past Activities ==
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* OpenMoko booth at the OpenExpo'07 Zurich

== NEO FreeRunner (aka GTA02) Group Order ==

[[GroupSales#Switzerland]]
=== Buying Interest List ===

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
! Quantity !! Nick
|-
| 1 || [[User:emonkey|emonkey]]
|-
| 1 || [[User:anthraxx|anthraxx]]
|-
| 1 || [[User:Gr33b|Gr33b]]
|-
| 1 || [[User:Megalomaniac|Megalomaniac]]
|-
| 1 || [[User:toldap|toldap]]
|-
| 1 || [[User:Philgood|Philgood]]
|-
| 1 || [[User:cgjusten|cgjusten]]
|-
| 1 || [[User:DarkAngel|DarkAngel]]
|-
| 1 || [[User:Agh|Agh]]
|-
| 1 || [[User:Anakron|Anakron]]
|-
| 1 || [[User:Onsonic|Onsonic]]
|-
| 1 || [[User:Mat|mat]]
|-
| 1 || [[User:JOn02|Jon02]]
|-
| 3 || [[User:darktim|darktim]]
|-
| 1 || [[User:Skarhand|Skarhand]]
|-
| 1 || [[User:Buz|Buz]]
|-
| 1 || [[User:none|None]]
|-
| 1 || [[User:cimi|cimi]]
|-
| 1 || [[User:jecuendet|jecuendet]]
|-
| 1 || [[User:Sigi|Sigi]]
|}

== Buying OpenMoko FreeRunner in Switzerland ==

If you are interested in getting an OpenMoko in your post box, drop me a mail at jec at jesc dot ch . I'm making a grouped order for Switzerland people.

Website: http://www.jesc.ch/openmoko

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]
*[[User:DarkAngel|DarkAngel]]
*[[User:Agh|Agh]]
*[[User:Anakron|Anakron]]
*[[User:Nowic|Nowic]]
*[[User:Magbeat|Magbeat]]
*[[User:darktim|darktim]]
*[[User:nickik|nickik]]
*[[User:Skarhand|Skarhand]]
*[[User:mat|mat]]
*[[User:psal|psal]]
*[[User:Tuxfux.ch|Tuxfux.ch]]
*[[User:claude-elrond740|claude-elrond740]]
*[[User:DrYak|DrYak]]

[[Category:Openmoko Local Groups]]

Openmoko:Current events

2008-08-08T00:13:32Z

C7: /* Upcoming */ OpenExpo 2008 - Zürich

This ''Current Events'' page provides information on both [[Current events#Past | past ]] and [[Current events#Upcoming | future]] events where FIC or [[Openmoko]] had or will have a presence.

== Upcoming ==
* 2008-08-04: [http://www.linuxworldexpo.com/live/12/ LinuxWorld 2008] August 04-07, 2008 | Moscone Center, San Francisco, CA | in booth 1625 and in the Linux Garage Pavilion booth 1234 in the Moscone Center North Hall | Michael, Harry, Steve, and Sean will be there
* 2008-08-23: [http://www.froscon.org FrOSCon 2008] August 23-24, 2008 | Bonn / St.Augustin, Germany | [[User:Mickey|Mickey]] will have a talk.
* 2008-09-24: [http://www.openexpo.ch/openexpo-2008-zuerich/ OpenExpo 2008 Zürich] September 24-25, 2008 | Winterthur, Switzerland | Booth organised by the [[Openmoko Local Groups: Switzerland|Openmoko Local Group Switzerland]]

== Past ==
* 2008-07-10: [http://wiki.oreillynet.com/foocamp08/ O'Reilly Foo Camp] July 11-13, 2008 | Sebastopol, CA | Michael Shiloh will be there
* 2008-06-24: [http://www.campus-party.com.co/ Campus Party in Colombia] June 23-29, 2008 | Bogota, Colombia | Sean gave a speech on 25th
* 2008-05-28: [http://www.linuxtag.org LinuxTag 2008] May 27-31, 2008 | Berlin, Germany | LinuxTag | [[User:Mickey|Mickey]] had a talk, Openmoko had a booth.
* 2008-05-16: [http://www.bsdcan.org/2008/ BSDCan] May 16-18, 2008 | Ottawa, CA | [[User:Idarwin|Ian Darwin]] presented Openmoko FreeRunner to the BSD crowd.
* 2008-04-09: Wednesday April 9, 2008 | London, UK | [http://ole.tange.dk Ole Tange] presented Openmoko / Freerunner to the [http://www.ukuug.org/events/openmoko/ UK Unix Users Group]
* 2008-04-08: [https://www.linux-foundation.org/events/collaboration The Linux Foundation Spring 2008 Collaboration Summit] April 8-10, 2008 | University of Texas Commons Center, Austin, TX | Sean is invited as one of the speakers
* 2008-03-28: [[Openmoko Education/zh tw]] - Friday March 28, 2008. | Hualien, Taiwan | Taiwan School promotion: Openmoko concepts will be presented at National Dong Hwa University
* 2008-03-26: [[Openmoko Education/zh tw]] - Wednesday March 26, 2008. | Chung Li, Taiwan | Taiwan School promotion: Openmoko concepts will be presented at Yuan Ze University
* 2008-03-16: [http://www.bossaconference.indt.org/ Bossa'08] - March 16-19, 2008 | Porto de Galinhas, Brazil| [[User:Raster|Raster]] is attending and will give a talk
* 2008-03-12: [http://www.openexpo.ch/openexpo-2008-bern/ OpenExpo'08] - March 12-13, 2008 | Bern, Switzerland | [[User:Mickey|Mickey]] is giving a talk about Openmoko | [[User:C7|C7]] is organising an OpenMoko booth
* 2008-03-06: [http://en.oreilly.com/et2008/public/schedule/detail/3330 OpenMoko and Ubiquitous Computing] - March 6, 2008 | San Diego, California | [[User:Michaelshiloh|Michael Shiloh]] is attending and will give a talk at ETech
* 2008-03-03: [[Openmoko Education/zh tw]] - Monday March 3, 2008. | Chung Li, Taiwan | Taiwan School promotion: Openmoko concepts will be presented at Chung Yuan Christian University
* 2008-02-27: [[Openmoko Education/zh tw]] - Wednesday February 27, 2008. | Hsinzhu, Taiwan | Taiwan School promotion: OpenMoko concepts will be presented at National Chiao Tung University
* 2008-02-23: [http://www.fosdem.org Fosdem'08] - February 23-24, 2008 | Brussels, Belgium | OpenMoko will be present at the [http://www.openembedded.org OpenEmbedded] booth, lots of OpenMoko developers will be present. [[Events:FOSDEM_2008 | Will you be there?]]
* 2008-02-22: [[Openmoko Education/zh tw]] - Friday February 22, 2008. | Tainan, Taiwan | Taiwan School promotion: OpenMoko concepts will be presented at National Cheng Kung University
* 2008-02-19: [http://www.oss.org.cn/index.php?option=com_content&task=view&id=677&Itemid=162 2008 Linux Developer Symposium-China] - February 19, 2008 | Beijing, China | Neo1973 was presented in a booth by Sun Liantao from [http://www.csip.org.cn CSIP] and [http://www.beijinglug.org BLUG]
* 2008-02-08: [http://www.socallinuxexpo.org/ SCALE'08] - February 8-10, 2008 | Los Angeles, USA | [[User:Raster|Raster]] is attending and will man the OpenMoko and Enlightenment booths
* 2008-01-07: Consumer Electronics Trade Show. [[Neo FreeRunner]] was presented. Links to stories, pictures, and videos: 
[[http://gizmodo.com/341755/openmoko-neo-freerunner-linux-smartphone-hands+on gizmodo]] 
[[http://takezero.net/3g-and-mobile-news/hands-on-with-fics-openmoko-powered-freerunner-2 takezero ]] 
[[http://youtube.com/watch?v=SZsps3bj6yE youtube]] 
[[http://www.reghardware.co.uk/2008/01/11/ces_video_openmoko_handset/ reghardware]] 
* 2007-12-19: [[OpenLab 2nd Event/zh tw]] - December 19, Wed. | Taipei, Taiwan | OpenLab 2nd Event: GPL & Apache License Talk and Discussion.
* 2007-11-17: [[Openmoko OpenLab Opening]] - November 17, Sat. | Taipei, Taiwan | OpenLab for OpenMoko Community is going to open.
* 2007-11-04: [http://coscup.org/2007/ Conference for Open Source Coders, Users and Promoters] - November 04 | Taipei, Taiwan | Jollen gave a talk about OpenMoko and OpenLab ideas.
* 2007-10-13: [http://onlinux.ca OnLinux Ontario Linux Fest 2007] - October 13 | Toronto, Canada | [[User:Idarwin|Ian Darwin]] gave a talk about Openmoko (slides [http://www.darwinsys.com/openmoko/ here]).
* 2007-10-02: [http://www.coss.fi/web/openmind/programme Openmind Conference] - October 02-03, 2007 | Tampere, Finland | Michael Shiloh as a speaker
* 2007-09-26: [http://imm.dtu.dk/ IMM at Danish Technical University] - [http://ole.tange.dk Ole Tange] is giving a talk.
* 2007-09-23: [http://www.barcamporlando.org/ BarCamp Orlando] Orlando, FL, USA | [[User:Writchie|Wally Ritchie]] will show Neos and talk about Openmoko project
* 2007-09-20: [http://www.openexpo.ch/openexpo-2007-zuerich/ OpenExpo'07] - September 19-20, 2007 | Zurich, Switzerland | [[User:Mickey|Mickey]] gave a talk about OpenMoko | [[User:C7|C7]] was organising an OpenMoko booth
* 2007-09-15: [http://mrmcd110b.metarheinmain.de metarheinmain chaosdays 110b] - ixs igave a [https://mrmcd110b.metarheinmain.de/fahrplan/events/2107.en.html talk]
* 2007-09-12: [http://dmusyd.edu/ Datamatikeruddannelsen i Nykøbing Falster] - [http://ole.tange.dk Ole Tange] gave a talk.
* 2007-08-30: [http://mobiledevices.kom.aau.dk/team_and_organization/events/mobile_developer_days_2007/ Mobile Developer Days 2007] - August 30 - September 2, 2007 | at Aalborg University, Denmark | [[User:Mickey|Mickey]] was invited to give a speech
* 2007-08-25: [http://www.froscon.org/Home.2.0.html?L=1 FrosCon'07] - August 25-26, 2007 | Sankt Augustin, Bonn, Germany | Mickey gave a talk about OpenMoko
* 2007-08-21: [http://www.beijinglug.org/en/index.php Beijing LUG] - August 21, 2007 | Sean and other OpenMoko team members were there to talk and give a presentation
* 2007-08-08 till 08-12: [http://events.ccc.de/camp/2007/Chaos_Communication_Camp_2007 Chaos Communication Camp 2007] took place in Finowfurt (close to Berlin, Germany) featuring the [http://events.ccc.de/camp/2007/GSM_Village GSM Village]
* 2007-08-04: [http://barcamp.org/BarCampRDU BarCampRDU] Raleigh, NC, USA | [[User:Writchie|Wally Ritchie]] showed neos and talk about OpenMoko project
* 2007-08-03: [http://wikimania2007.wikimedia.org/wiki/Main_Page wikimania 2007] - August 03-05, 2007 | Taipei, Taiwan | OpenMoko has been invited to co-host with Wiki heads to promote open content in Taiwan.
* 2007-07-26 [http://conferences.oreillynet.com/os2007/ OSCON 2007] | OpenMoko Birds of a Feather session July 26th, Portland Oregon
* 2007-07-15: [http://www.guadec.org GUADEC, The GNOME Conference 2007] - July 15-21, 2007 | Birmingham, United Kingdom | [[User:Mickey|Mickey]] gave a talk about OpenMoko
* 2007-07-10: [http://www.rmll.info 8th Libre Software Meeting] - July 10-14, 2007 | Amiens, France | [http://datenfreihafen.org Stefan Schmidt] gave a [http://www.rmll.info/article136.html?lang=en talk] about OpenEZX and OpenMoko
* 2007-07-09: The [http://www.openmoko.com openmoko.com web shop] was opened; first sales of GTA01_v4 devices.
* 2007-06-05: [http://www.computextaipei.com.tw Computex Taipei 2007] - June 5-9, 2007 | Taipei World Trade Center, Taipei, Taiwan | OpenMoko was in the FIC Group's Booth
* 2007-06-01: [http://www.linuxtag.org/2007/en/home/welcome.html LinuxTag 2007] - May 30-June-2, 2007 | LinuxTag in Berlin, Germany | [[User:Mickey|Mickey]] gave a [http://www.linuxtag.org/2007/en/conf/events/vp-speakers/details.html?talkid=84 talk] about OpenMoko
* 2007-05-19: [http://www.makerfaire.com/ Maker Faire Events] -- May 19-May 20, 2007 | San Francisco Bay Area, San Mateo Expo Center, USA | Michael Shiloh and Jon Phillips presented at OpenMoko's booth on behalf of Sean
* 2007-05-08 [http://wiki.tossug.org/SignUp:2007-05 Taipei Open Source Software User Group (TOSSUG)] - Cafe Lumiere, Taipei, Taiwan | May 8, 2007
* 2007-04-04 [http://fostel2007.fostel.org/index.php/Main_Page FOSTEL] - European Institute of Technology, Paris, France | April 4-5, 2007
* 2007-03-16: On March 16, 2007 [[User:Mickey|Mickey]] presented the device at a Zaurus User Group Meeting in Düsseldorf, Germany.
* 2007-03-15: On March 15-18, 2007 there was a Polish Linux User Group conference [http://pingwinaria.linux.org.pl/PLUG/imprezy/pingwinaria/2007/agenda Pingwinaria 2007] in Krynica Zdrój, Poland. Tomasz Zieliński gave a talk about OpenMoko and two Neo1973 devices were present there. Also Marcin Juszkiewicz presented OpenEmbedded project there.
* 2007-03-05: 36 P0 devices shipped to developers.
* 2007-03-03: [http://www.linuxforum.dk/2007/program/saturday/Martin_Hansen.shtml Martin Hansen and Ole Tange] spoke at [http://www.linuxforum.dk LinuxForum]
* 2007-02-27: February 27th-March 1st the [http://conferences.oreillynet.com/etel2007/ O'Reilly Emerging Telephony conference] was held at the San Francisco Airport Mariott, Burlingame, CA. Open Phones are on the agenda: Sean presented a workshop on February 27; Surj Patel and Matt Hamrick of Tuxphone and the homebrew club also presented. An OpenMoko/Open Phones Social gathering was proposed on the evening of the last day, March 1. We hope Tuxphone and SVHMPC people will join us as well. [[ETel]]
* 2007-02-23: Meeting at [[Events:FOSDEM_2007|FOSDEM 2007]]
* 2007-02-14: The openmoko.org web site was [http://lists.openmoko.org/pipermail/announce/2007-February/000004.html opened to the public].
* 2007-01-06 [http://www.lunchat.com/ Lunch@Piero's] - CES, Las Vegas, NE | 7-9 January, 2007
* 2006-11-07: [http://www.informatm.com/NASApp/cs/ContentServer?pagename=marlin/home&MarlinViewType=MARKT_EFFORT&siteid=30000000861&marketingid=20001437372&proceed=true&MarEntityId=1162023598681&entHash=100595e9ac1 Open Source in Mobile] - Amsterdam, The Netherlands, 7-8 November 2006. Sean Moss-Pultz's "Mystery Guest" presentation can be found [http://www.openmoko.com/files/OpenMoko_Amsterdam.pdf here].

{{Languages|Openmoko:Current events}}

[[Category:Community]]
[[Category:Event]]

Openmoko Local Groups: Switzerland

2008-08-07T23:58:01Z

C7: 2 new events plus some cleanup

== Upcoming Events ==
* Booth at the OpenExpo '08 Winterthur(Zürich) 24./25. September 2008 <-- help needed!
* Community Grill proposed after the OpenExpo (25. September?)

== Past Activities ==
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* OpenMoko booth at the OpenExpo'07 Zurich

== NEO FreeRunner (aka GTA02) Group Order ==

[[GroupSales#Switzerland]]
=== Buying Interest List ===

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
! Quantity !! Nick
|-
| 1 || [[User:emonkey|emonkey]]
|-
| 1 || [[User:anthraxx|anthraxx]]
|-
| 1 || [[User:Gr33b|Gr33b]]
|-
| 1 || [[User:Megalomaniac|Megalomaniac]]
|-
| 1 || [[User:toldap|toldap]]
|-
| 1 || [[User:Philgood|Philgood]]
|-
| 1 || [[User:cgjusten|cgjusten]]
|-
| 1 || [[User:DarkAngel|DarkAngel]]
|-
| 1 || [[User:Agh|Agh]]
|-
| 1 || [[User:Anakron|Anakron]]
|-
| 1 || [[User:Onsonic|Onsonic]]
|-
| 1 || [[User:Mat|mat]]
|-
| 1 || [[User:JOn02|Jon02]]
|-
| 3 || [[User:darktim|darktim]]
|-
| 1 || [[User:Skarhand|Skarhand]]
|-
| 1 || [[User:Buz|Buz]]
|-
| 1 || [[User:none|None]]
|-
| 1 || [[User:cimi|cimi]]
|-
| 1 || [[User:jecuendet|jecuendet]]
|-
| 1 || [[User:Sigi|Sigi]]
|}

== Buying OpenMoko FreeRunner in Switzerland ==

If you are interested in getting an OpenMoko in your post box, drop me a mail at jec at jesc dot ch . I'm making a grouped order for Switzerland people.

Website: http://www.jesc.ch/openmoko

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]
*[[User:DarkAngel|DarkAngel]]
*[[User:Agh|Agh]]
*[[User:Anakron|Anakron]]
*[[User:Nowic|Nowic]]
*[[User:Magbeat|Magbeat]]
*[[User:darktim|darktim]]
*[[User:nickik|nickik]]
*[[User:Skarhand|Skarhand]]
*[[User:mat|mat]]
*[[User:psal|psal]]
*[[User:Tuxfux.ch|Tuxfux.ch]]
*[[User:claude-elrond740|claude-elrond740]]
*[[User:DrYak|DrYak]]

[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Switzerland

2008-01-30T18:24:32Z

C7: fixed layout

== Upcoming Events ==
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]

== Past Activities ==

=== OpenMoko Presentation at ZHAW Winterthur===
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]

=== OpenMoko booth at the OpenExpo'07 Zurich ===

* Date: 19./20. September 2007
* Website: [http://www.openexpo.ch/openexpo-2007-zuerich/ link]
* Brochure: [http://www.openexpo.ch/fileadmin/documents/OpenExpo_2007Zuerich_Prospekt.pdf link]

== GTA02 Group Order ==
=== Buying Interest List ===
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
! Quantity !! Base or Advanced? !! Color !! Nick
|-
| 1 || Advanced || Black/Silver || [[User:C7|C7]]
|-
| 1 || Base|| Black/Silver (If possible Black/Orange) || [[User:emonkey|emonkey]]
|-
| 1 || Base|| Black/Silver || [[User:anthraxx|anthraxx]]
|-
| 1 || Advanced|| White/Orange || [[User:Gr33b|Gr33b]]
|-
| 1 || Base|| Black/Silver || [[User:Megalomaniac|Megalomaniac]]
|-
| 1 || Advanced|| White/Orange || [[User:toldap|toldap]]
|-
| 1 || Advanced|| Black/Silver || [[User:Philgood|Philgood]]
|-
| 1 || Advanced|| Black/Silver || [[User:cgjusten|cgjusten]]
|}

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]

User:C7

2007-12-05T12:25:06Z

C7: /* OpenExpo'08 Bern, Switzerland */

== Contact ==
* Name: Ben Hagen
* Email: akvo ( at ) hispeed.ch
* IRC: irc.freenode.net #openmoko (nick: C7)

== OpenExpo'08 Bern, Switzerland ==

I'm organising an OpenMoko booth at the [http://www.openexpo.ch/openexpo-2008-bern/ OpenExpo'08] in Bern, Switzerland. Any help welcome ;) More infos [[OpenMoko_Local_Groups: Switzerland|here]].

User:C7

2007-12-05T12:24:39Z

C7: /* OpenExpo'08 Bern, Switzerland */

== Contact ==
* Name: Ben Hagen
* Email: akvo ( at ) hispeed.ch
* IRC: irc.freenode.net #openmoko (nick: C7)

== OpenExpo'08 Zurich, Switzerland ==

I'm organising an OpenMoko booth at the [http://www.openexpo.ch/openexpo-2008-bern/ OpenExpo'08] in Bern, Switzerland. Any help welcome ;) More infos [[OpenMoko_Local_Groups: Switzerland|here]].

Openmoko:Current events

2007-12-05T12:22:53Z

C7: /* Upcoming */ OpenExpo'08 - Bern

This ''Current Events'' page provides information on both [[Current events#Past | past ]] and [[Current events#Upcoming | future]] events where FIC or [[OpenMoko]] had or will have a presence.

== Upcoming ==
* 2007-12-19: [[OpenLab 2nd Event/zh tw]] - December 19, Wed. | Taipei, Taiwan | OpenLab 2nd Event: GPL & Apache License Talk and Discussion.
* 2008-03-12: [http://www.openexpo.ch/openexpo-2008-bern/ OpenExpo'08] - March 12-13, 2008 | Bern, Switzerland | [[User:Mickey|Mickey]] is giving a talk about OpenMoko | [[User:C7|C7]] is organising an OpenMoko booth

== Past ==
* 2007-11-17: [[OpenMoko OpenLab Opening]] - November 17, Sat. | Taipei, Taiwan | OpenLab for OpenMoko Community is going to open.
* 2007-11-04: [http://coscup.org/2007/ Conference for Open Source Coders, Users and Promoters] - November 04 | Taipei, Taiwan | Jollen gave a talk about OpenMoko and OpenLab ideas.
* 2007-10-13: [http://onlinux.ca OnLinux Ontario Linux Fest 2007] - October 13 | Toronto, Canada | [[User:Idarwin|Ian Darwin]] gave a talk about OpenMoko (slides [http://www.darwinsys.com/openmoko/ here]).
* 2007-10-02: [http://www.coss.fi/web/openmind/programme Openmind Conference] - October 02-03, 2007 | Tampere, Finland | Michael Shiloh as a speaker
* 2007-09-26: [http://imm.dtu.dk/ IMM at Danish Technical University] - [http://ole.tange.dk Ole Tange] is giving a talk.
* 2007-09-23: [http://www.barcamporlando.org/ BarCamp Orlando] Orlando, FL, USA | [[User:Writchie|Wally Ritchie]] will show Neos and talk about OpenMoko project
* 2007-09-20: [http://www.openexpo.ch/openexpo-2007-zuerich/ OpenExpo'07] - September 19-20, 2007 | Zurich, Switzerland | [[User:Mickey|Mickey]] gave a talk about OpenMoko | [[User:C7|C7]] was organising an OpenMoko booth
* 2007-09-15: [http://mrmcd110b.metarheinmain.de metarheinmain chaosdays 110b] - ixs igave a [https://mrmcd110b.metarheinmain.de/fahrplan/events/2107.en.html talk]
* 2007-09-12: [http://dmusyd.edu/ Datamatikeruddannelsen i Nykøbing Falster] - [http://ole.tange.dk Ole Tange] gave a talk.
* 2007-08-30: [http://mobiledevices.kom.aau.dk/team_and_organization/events/mobile_developer_days_2007/ Mobile Developer Days 2007] - August 30 - September 2, 2007 | at Aalborg University, Denmark | [[User:Mickey|Mickey]] was invited to give a speech
* 2007-08-25: [http://www.froscon.org/Home.2.0.html?L=1 FrosCon'07] - August 25-26, 2007 | Sankt Augustin, Bonn, Germany | Mickey gave a talk about OpenMoko
* 2007-08-21: [http://www.beijinglug.org/en/index.php Beijing LUG] - August 21, 2007 | Sean and other OpenMoko team members were there to talk and give a presentation
* 2007-08-08 till 08-12: [http://events.ccc.de/camp/2007/Chaos_Communication_Camp_2007 Chaos Communication Camp 2007] took place in Finowfurt (close to Berlin, Germany) featuring the [http://events.ccc.de/camp/2007/GSM_Village GSM Village]
* 2007-08-04: [http://barcamp.org/BarCampRDU BarCampRDU] Raleigh, NC, USA | [[User:Writchie|Wally Ritchie]] showed neos and talk about OpenMoko project
* 2007-08-03: [http://wikimania2007.wikimedia.org/wiki/Main_Page wikimania 2007] - August 03-05, 2007 | Taipei, Taiwan | OpenMoko has been invited to co-host with Wiki heads to promote open content in Taiwan.
* 2007-07-26 [http://conferences.oreillynet.com/os2007/ OSCON 2007] | OpenMoko Birds of a Feather session July 26th, Portland Oregon
* 2007-07-15: [http://www.guadec.org GUADEC, The GNOME Conference 2007] - July 15-21, 2007 | Birmingham, United Kingdom | [[User:Mickey|Mickey]] gave a talk about OpenMoko
* 2007-07-10: [http://www.rmll.info 8th Libre Software Meeting] - July 10-14, 2007 | Amiens, France | [http://datenfreihafen.org Stefan Schmidt] gave a [http://www.rmll.info/article136.html?lang=en talk] about OpenEZX and OpenMoko
* 2007-07-09: The [http://www.openmoko.com openmoko.com web shop] was opened; first sales of GTA01_v4 devices.
* 2007-06-05: [http://www.computextaipei.com.tw Computex Taipei 2007] - June 5-9, 2007 | Taipei World Trade Center, Taipei, Taiwan | OpenMoko was in the FIC Group's Booth
* 2007-06-01: [http://www.linuxtag.org/2007/en/home/welcome.html LinuxTag 2007] - May 30-June-2, 2007 | LinuxTag in Berlin, Germany | [[User:Mickey|Mickey]] gave a [http://www.linuxtag.org/2007/en/conf/events/vp-speakers/details.html?talkid=84 talk] about OpenMoko
* 2007-05-19: [http://www.makerfaire.com/ Maker Faire Events] -- May 19-May 20, 2007 | San Francisco Bay Area, San Mateo Expo Center, USA | Michael Shiloh and Jon Phillips presented at OpenMoko's booth on behalf of Sean
* 2007-05-08 [http://wiki.tossug.org/SignUp:2007-05 Taipei Open Source Software User Group (TOSSUG)] - Cafe Lumiere, Taipei, Taiwan | May 8, 2007
* 2007-04-04 [http://fostel2007.fostel.org/index.php/Main_Page FOSTEL] - European Institute of Technology, Paris, France | April 4-5, 2007
* 2007-03-16: On March 16, 2007 [[User:Mickey|Mickey]] presented the device at a Zaurus User Group Meeting in Düsseldorf, Germany.
* 2007-03-15: On March 15-18, 2007 there was a Polish Linux User Group conference [http://pingwinaria.linux.org.pl/PLUG/imprezy/pingwinaria/2007/agenda Pingwinaria 2007] in Krynica Zdrój, Poland. Tomasz Zieliński gave a talk about OpenMoko and two Neo1973 devices were present there. Also Marcin Juszkiewicz presented OpenEmbedded project there.
* 2007-03-05: 36 P0 devices shipped to developers.
* 2007-03-03: [http://www.linuxforum.dk/2007/program/saturday/Martin_Hansen.shtml Martin Hansen and Ole Tange] spoke at [http://www.linuxforum.dk LinuxForum]
* 2007-02-27: February 27th-March 1st the [http://conferences.oreillynet.com/etel2007/ O'Reilly Emerging Telephony conference] was held at the San Francisco Airport Mariott, Burlingame, CA. Open Phones are on the agenda: Sean presented a workshop on February 27; Surj Patel and Matt Hamrick of Tuxphone and the homebrew club also presented. An OpenMoko/Open Phones Social gathering was proposed on the evening of the last day, March 1. We hope Tuxphone and SVHMPC people will join us as well. [[ETel]]
* 2007-02-23: Meeting at [[Events:FOSDEM_2007|FOSDEM 2007]]
* 2007-02-14: The openmoko.org web site was [http://lists.openmoko.org/pipermail/announce/2007-February/000004.html opened to the public].
* 2007-01-06 [http://www.lunchat.com/ Lunch@Piero's] - CES, Las Vegas, NE | 7-9 January, 2007
* 2006-11-07: [http://www.informatm.com/NASApp/cs/ContentServer?pagename=marlin/home&MarlinViewType=MARKT_EFFORT&siteid=30000000861&marketingid=20001437372&proceed=true&MarEntityId=1162023598681&entHash=100595e9ac1 Open Source in Mobile] - Amsterdam, The Netherlands, 7-8 November 2006. Sean Moss-Pultz's "Mystery Guest" presentation can be found [http://www.openmoko.com/files/OpenMoko_Amsterdam.pdf here].

[[Category:Events]]
[[Category:Community]]

Openmoko Local Groups: Switzerland

2007-11-14T08:17:13Z

C7: fixed link

== Upcoming Events ==
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]

== Past Activities ==

=== OpenMoko booth at the OpenExpo'07 Zurich ===

* Date: 19./20. September 2007
* Website: [http://www.openexpo.ch/openexpo-2007-zuerich/ link]
* Brochure: [http://www.openexpo.ch/fileadmin/documents/OpenExpo_2007Zuerich_Prospekt.pdf link]

== GTA02 Group Order ==

=== Buying Interest List ===
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
! Quantity !! Base or Advanced? !! Color !! Nick
|-
| 1 || Advanced || Black/Silver || [[User:C7|C7]]
|-
|}

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
* you?

Openmoko Local Groups: Switzerland

2007-11-10T04:20:25Z

C7: GTA02 Group Order (draft)

== Upcoming Events ==
* [http://lug.zhaw.ch/wiki/index.php/Distro-Bash_2007 Distro-Bash Winterthur]
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]

== Past Activities ==

=== OpenMoko booth at the OpenExpo'07 Zurich ===

* Date: 19./20. September 2007
* Website: [http://www.openexpo.ch/openexpo-2007-zuerich/ link]
* Brochure: [http://www.openexpo.ch/fileadmin/documents/OpenExpo_2007Zuerich_Prospekt.pdf link]

== GTA02 Group Order ==

=== Buying Interest List ===
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
! Quantity !! Base or Advanced? !! Color !! Nick
|-
| 1 || Advanced || Black/Silver || [[User:C7|C7]]
|-
|}

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
* you?

Openmoko Local Groups: Switzerland

2007-11-10T03:39:19Z

C7: some updates + upcoming events

Community Updates

2007-11-06T08:37:20Z

C7: fixed link to michael's profile

'''Community Updates'''

As we strive to make our development progress as open as possible, we do not provide delivery dates. Instead, we continuously report on the project status here and on our mailing list.

The status is usually updated at least twice a month, usually by [[User:Michaelshiloh|Michael Shiloh]]. Updates are also mailed to the community mailing list (see below for previous updates), and major updates are also sent to the announce list.

You are invited to add questions or topics you think should be included in the Community Updates.

==Current Status==

===GTA02 hardware production and qualification===
GTA02v3 is quite solid, but a flaw in power distribution required another revision. A very small number of GTA02v4 have been manufactured. Evaluation by internal OpenMoko engineers should start any day now (relative to October 31, 2007).

===gllin GPS driver for GTA01===
We have received permission to distribute this driver in binary-only form, however the binary format is different from what we now use (OABI vs EABI in 2007.2 vs 2007.1 OpenMoko). There are various work-arounds (chroot, wrapper) but they raise legal questions. We are in the process of sorting out these legal issues.

===850 MHz band not supported in USA+Canada (e.g. comment 24 on bug #256)===

The GSM chip set is capable of quad band operation but the circuit implemented only supports 3 bands. So, 850Mhz is not supported on the GTA01 board. Instead we support 900/1800/1900MHz.

Anyone interested in more details is welcome to email me.

===Delivery of a GSM firmware update for the 3G SIM bug (#666)===
I believe the problem has been solved and we have permission to update the firmware, but there is a question as to how to legally update in the field.

==Questions or Topics you think are missing==

=== SMedia 3362 Documentation & OpenGL ES Drivers ===
There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and OpenMoko developers will not be writing one in the near future (although they have not ruled it out in the long-term).

Documentation for the SMedia 3362 has been promised ([http://lists.openmoko.org/pipermail/community/2007-September/010175.html see this post]). However, this refers to documentation OpenMoko developers will be writing themselves, not the technical documentation SMedia have provided OpenMoko with. The OpenMoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See [http://lists.openmoko.org/pipermail/community/2007-November/011349.html this post] for details)

==Previous Community Updates==
*[[September 28, 2007 Community Update]]
*[[October 12, 2007 Community Update]]
*[[October 13, 2007 Community Update]]
*[[October 15, 2007 Community Update]]
*[[October 16, 2007 Community Update]]
*[[October 25, 2007 Community Update]]
*[[October 31, 2007 Community Update]]
*[[November 6, 2007 Community Update]]

[[Category:Community]]

Openmoko:Current events

2007-11-05T13:03:04Z

C7: /* Past */

This ''Current Events'' page provides information on both [[Current events#Past | past ]] and [[Current events#Upcoming | future]] events where FIC or [[OpenMoko]] had or will have a presence.

== Upcoming ==

* 2007-11-17: [[OpenMoko OpenLab Opening]] - November 17, Sat. | Taipei, Taiwan | OpenLab for OpenMoko Community is going to open.

== Past ==

* 2007-10-13: [http://onlinux.ca OnLinux Ontario Linux Fest 2007] - October 13 | Toronto, Canada | [[User:Idarwin|Ian Darwin]] gave a talk about OpenMoko (slides [http://www.darwinsys.com/openmoko/ here]).
* 2007-10-02: [http://www.coss.fi/web/openmind/programme Openmind Conference] - October 02-03, 2007 | Tampere, Finland | Michael Shiloh as a speaker
* 2007-09-26: [http://imm.dtu.dk/ IMM at Danish Technical University] - [http://ole.tange.dk Ole Tange] is giving a talk.
* 2007-09-23: [http://www.barcamporlando.org/ BarCamp Orlando] Orlando, FL, USA | [[User:Writchie|Wally Ritchie]] will show Neos and talk about OpenMoko project
* 2007-09-20: [http://www.openexpo.ch/openexpo-2007-zuerich/ OpenExpo'07] - September 19-20, 2007 | Zurich, Switzerland | [[User:Mickey|Mickey]] gave a talk about OpenMoko | [[User:C7|C7]] was organising an OpenMoko booth
* 2007-09-15: [http://mrmcd110b.metarheinmain.de metarheinmain chaosdays 110b] - ixs igave a [https://mrmcd110b.metarheinmain.de/fahrplan/events/2107.en.html talk]
* 2007-09-12: [http://dmusyd.edu/ Datamatikeruddannelsen i Nykøbing Falster] - [http://ole.tange.dk Ole Tange] gave a talk.
* 2007-08-30: [http://mobiledevices.kom.aau.dk/team_and_organization/events/mobile_developer_days_2007/ Mobile Developer Days 2007] - August 30 - September 2, 2007 | at Aalborg University, Denmark | [[User:Mickey|Mickey]] was invited to give a speech
* 2007-08-25: [http://www.froscon.org/Home.2.0.html?L=1 FrosCon'07] - August 25-26, 2007 | Sankt Augustin, Bonn, Germany | Mickey gave a talk about OpenMoko
* 2007-08-21: [http://www.beijinglug.org/en/index.php Beijing LUG] - August 21, 2007 | Sean and other OpenMoko team members were there to talk and give a presentation
* 2007-08-08 till 08-12: [http://events.ccc.de/camp/2007/Chaos_Communication_Camp_2007 Chaos Communication Camp 2007] took place in Finowfurt (close to Berlin, Germany) featuring the [http://events.ccc.de/camp/2007/GSM_Village GSM Village]
* 2007-08-04: [http://barcamp.org/BarCampRDU BarCampRDU] Raleigh, NC, USA | [[User:Writchie|Wally Ritchie]] showed neos and talk about OpenMoko project
* 2007-08-03: [http://wikimania2007.wikimedia.org/wiki/Main_Page wikimania 2007] - August 03-05, 2007 | Taipei, Taiwan | OpenMoko has been invited to co-host with Wiki heads to promote open content in Taiwan.
* 2007-07-26 [http://conferences.oreillynet.com/os2007/ OSCON 2007] | OpenMoko Birds of a Feather session July 26th, Portland Oregon
* 2007-07-15: [http://www.guadec.org GUADEC, The GNOME Conference 2007] - July 15-21, 2007 | Birmingham, United Kingdom | [[User:Mickey|Mickey]] gave a talk about OpenMoko
* 2007-07-10: [http://www.rmll.info 8th Libre Software Meeting] - July 10-14, 2007 | Amiens, France | [http://datenfreihafen.org Stefan Schmidt] gave a [http://www.rmll.info/article136.html?lang=en talk] about OpenEZX and OpenMoko
* 2007-07-09: The [http://www.openmoko.com openmoko.com web shop] was opened; first sales of GTA01_v4 devices.
* 2007-06-05: [http://www.computextaipei.com.tw Computex Taipei 2007] - June 5-9, 2007 | Taipei World Trade Center, Taipei, Taiwan | OpenMoko was in the FIC Group's Booth
* 2007-06-01: [http://www.linuxtag.org/2007/en/home/welcome.html LinuxTag 2007] - May 30-June-2, 2007 | LinuxTag in Berlin, Germany | [[User:Mickey|Mickey]] gave a [http://www.linuxtag.org/2007/en/conf/events/vp-speakers/details.html?talkid=84 talk] about OpenMoko
* 2007-05-19: [http://www.makerfaire.com/ Maker Faire Events] -- May 19-May 20, 2007 | San Francisco Bay Area, San Mateo Expo Center, USA | Michael Shiloh and Jon Phillips presented at OpenMoko's booth on behalf of Sean
* 2007-05-08 [http://wiki.tossug.org/SignUp:2007-05 Taipei Open Source Software User Group (TOSSUG)] - Cafe Lumiere, Taipei, Taiwan | May 8, 2007
* 2007-04-04 [http://fostel2007.fostel.org/index.php/Main_Page FOSTEL] - European Institute of Technology, Paris, France | April 4-5, 2007
* 2007-03-16: On March 16, 2007 [[User:Mickey|Mickey]] presented the device at a Zaurus User Group Meeting in Düsseldorf, Germany.
* 2007-03-15: On March 15-18, 2007 there was a Polish Linux User Group conference [http://pingwinaria.linux.org.pl/PLUG/imprezy/pingwinaria/2007/agenda Pingwinaria 2007] in Krynica Zdrój, Poland. Tomasz Zieliński gave a talk about OpenMoko and two Neo1973 devices were present there. Also Marcin Juszkiewicz presented OpenEmbedded project there.
* 2007-03-05: 36 P0 devices shipped to developers.
* 2007-03-03: [http://www.linuxforum.dk/2007/program/saturday/Martin_Hansen.shtml Martin Hansen and Ole Tange] spoke at [http://www.linuxforum.dk LinuxForum]
* 2007-02-27: February 27th-March 1st the [http://conferences.oreillynet.com/etel2007/ O'Reilly Emerging Telephony conference] was held at the San Francisco Airport Mariott, Burlingame, CA. Open Phones are on the agenda: Sean presented a workshop on February 27; Surj Patel and Matt Hamrick of Tuxphone and the homebrew club also presented. An OpenMoko/Open Phones Social gathering was proposed on the evening of the last day, March 1. We hope Tuxphone and SVHMPC people will join us as well. [[ETel]]
* 2007-02-23: Meeting at [[Events:FOSDEM_2007|FOSDEM 2007]]
* 2007-02-14: The openmoko.org web site was [http://lists.openmoko.org/pipermail/announce/2007-February/000004.html opened to the public].
* 2007-01-06 [http://www.lunchat.com/ Lunch@Piero's] - CES, Las Vegas, NE | 7-9 January, 2007
* 2006-11-07: [http://www.informatm.com/NASApp/cs/ContentServer?pagename=marlin/home&MarlinViewType=MARKT_EFFORT&siteid=30000000861&marketingid=20001437372&proceed=true&MarEntityId=1162023598681&entHash=100595e9ac1 Open Source in Mobile] - Amsterdam, The Netherlands, 7-8 November 2006. Sean Moss-Pultz's "Mystery Guest" presentation can be found [http://www.openmoko.com/files/OpenMoko_Amsterdam.pdf here].

[[Category:Events]]
[[Category:Community]]

USB Networking

2007-10-31T20:06:05Z

C7: /* Automatic method */ Ubuntu Gutsy Gibbon

= Neo1973 side =

== Name resolution ==

By default Neo1973 has usb0 interface working due to Ethernet gadget (g_ether) compiled into kernel.

On the Neo, if you want to reach out to the internets using full qualified hostnames, you need to define your DNS server. Create a file /etc/resolv.conf with at least one line saying

nameserver xxx.xxx.xxx.xxx

e.g. nameserver 192.168.1.1

Then you can also easily update your 2007.2 OpenMoko packages with "ipkg update && ipkg upgrade" on the Neo.

A better aproach is to symlink

ln -s /var/run/resolv.conf /etc/resolv.conf

and fill the file at bootup with a script /etc/network/if-up.d/08setupdns containing:

#!/bin/sh -e
echo nameserver 192.168.0.200 > /var/run/resolv.conf

this way the file is correctly handled from ppp package when dialing into gprs.

== Routing ==

You need a additional route for traffic to the internet. This traffic can be routed through your pc (see below) if the pc is the default route destination. you can achieve this by adding

gateway 10.10.10.21

to your /etc/network/interfaces in the usb0 section.

= Desktop side =

== Manual method ==

With the device connected, modprobe usbnet module and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo
# ssh root@192.168.0.202

If you don't have the necessary modules to get usb0 going, make sure you have the following kernel options enabled:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER
Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatic method ==

Took from [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] post by Marcin 'Hrw' Juszkiewicz.

'''For Debian or similar distros:'''
Edit /etc/network/interfaces file ():
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

'''For Ubuntu (Tested with Feisty and Gutsy):'''
Edit /etc/network/interfaces file ():
<pre>
auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/net/ipv4/ip_forward &
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
</pre>

If you are doing the echo 1 > /proc/... command manually, sudo may not be enough, then you will have to execute it from a sudo bash.

Ubuntu Feisty and Gutsy appear to have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted.
One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:
<pre>
SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

# Bring devices up and down only if they're marked auto.
# Use start-stop-daemon so we don't wait on dhcp
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"

LABEL="net_end"

ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"
</pre>

the bug is that the LABEL="net_end" is at the wrong position

'''For Red Hat or similar distros'''
Edit /etc/sysconfig/network-scripts/net.hotplug:

After this statement:
<pre>
case $INTERFACE in
# interfaces that are registered after being "up" (?)
</pre>

Add the following:
<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
exit 0
;;
</pre>

'''For Gentoo or similar distros:'''

* Edit /etc/conf.d/net by adding:
<pre>
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
</pre>
* Create a new init script:
<pre>
# cd /etc/init.d
# ln -s net.lo net.usb0
</pre>

And now when you connect phone (which has 192.168.0.202 IP) it gets connection to world automatically.

'''For MacOS X:'''

there are no files to edit since hotplugging configuration is done automatically by default. Of course, the interface has been initialized once. Install the AJZaurusUSB driver as described on [[MacOS_X]] and then open System Preferences / Networks which will show the new interface. Configure for Manual DHC with Host address 192.168.0.200 and Gateway 192.168.0.202.

= Mobile development =

== Proxying DNS requests ==

If, like me, you move about quite a lot, connecting to various networks as you go and getting your ip via dhcp, you'll probably be annoyed at having to constantly update your resolv.conf on the Neo 1973.

To get round this, as part of my setup script, I run a proxy dns on the ip address the neo comes in on at the usb0 port. This means that my Neo /etc/resolv.conf only contains:

nameserver 192.168.0.200

and my laptop will proxy all dns requests based on it's own /etc/resolv.conf

'''note that we only run the dns proxy on the usb0 interface so that we don't break any other networking'''

=== Proxying with dnrd ===

The script is designed to use [http://dnrd.sourceforge.net/ dnrd] as the dns proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available from my site. The script also performs the initial setup of the connection as per the [[USB_Networking#Manual_method]] above.

=== Proxying with a UDP forwarder ===
Another easy setup is using a udp forwarder like the one from http://www.tapor.com/udpf/ - is use it with the command

udpf-elf\
-p=53\
-f=`cat /etc/resolv.conf|awk '$1 == "nameserver"{print $2; exit(0);}'`:53

=== Proxying with iptables ===
Its is possible to forward DNS requests with iptables using the DNAT target

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

where <tt>192.168.0.1</tt> is the IP of your residential gateway (router). This is the easiest method, but its not recommended if you have a direct connection to the Internet as ISP DNS servers can change, and this does no load-balancing.

= Connecting to phone =

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

NOTE: the ssh daemon (dropbear 0.49) on the OpenMoko appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

===SSH Extras===

If you get fed up with typing root@192.168.0.202, on your PC edit /etc/hosts and add an entry for 'phone'

192.168.0.202 phone

then edit ~/.ssh/config (or create it) and add

host phone
user root

then all you need to do is type

# ssh phone

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

You might want to use keys to bypass the login prompt too.

===SSH Keys===
====From host to phone====

To generate ssh keys for use as a login mechanism type

ssh-keygen -t rsa

when prompted for a password either hit enter for no password (''not really a good idea'') or enter a password for this key. ssh into the phone and create ~/.ssh

# mkdir ~/.ssh

then from your PC copy the '''.pub''' file to the phone.

# scp ~/.ssh/id_rsa.pub phone:.ssh/authorized_keys

You should now be able to ssh directly into the phone.

To disable password logins ('''after setting up key access''') edit /etc/init.d/dropbear and change the following line:

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

You will need to restart dropbear for this to take effect.

====From phone to host====
Generate the key

dropbearkey -t rsa -f id_rsa

The output will look something like this:

Will output 1024 bit rsa secret key to 'id_rsa'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3Nza[...]
Fingerprint: md5 ca:e8:f0:b7:f6:7b:c2:b6:b9:71:e4:45:86:a9:ff:b8

Copy and paste the one line (in this example, starting with 'ssh-rsa' onto the end of the host's authorized_keys file (often in ~/.ssh/).

From the phone, ssh with -i:

ssh -i id_rsa user@host

This works for me. I ripped off these instructions from: [[http://forum.openwrt.org/viewtopic.php?pid=53705]]

===GUI on desktop through SSH===

If you need to get the GUI on the phone onto the desktop via usb, you can use ssh as follows

ssh -l root -X -v 192.168.0.202

Login, and run openmoko-finger-demo for example, and it will open up on the desktop. To get landscape view, just resize the GUI window on the desktop.

===Remote apps on neo===

To get desktop apps to show up on your neo, first log in to the phone

ssh -l root 192.168.0.202

Then once inside, run:

DISPLAY=:0 xhost +192.168.0.200

After this you can close the ssh session. Back on the desktop computer, run:

DISPLAY=moko:0 xclock

Note that the xhost command will allow remote applications on 192.168.0.200 to access the X server. It will allow anyone on the desktop machine to access the X server of the neo, including snooping anything you type on it. To disallow remote applications again, run this in the neo:

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]

Qtopia on Neo1973

2007-09-29T18:06:19Z

C7: Qtopia AND OpenMoko ;)

{{Languages|Qtopia_on_Neo_1973}}

== Installation ==

=== Qtopia image ===
Get "Qtopia on Neo Flash Image and kernel" [http://www.qtopia.net/modules/devices/openmoko.php from here]. Currently the flash tarball has the 2.6.21 openmoko kernel and a Qtopia phone edition jffs2 flash image cross-compiled for the Neo.

It appears you must clear the flash chunks first (if you have not updated your uboot. If you have, you may skip this step). Get into uboot console [http://wiki.openmoko.org/wiki/Uboot#Accessing_the_bootloader_prompt] and enter

nand erase kernel
nand erase rootfs

Download and use dfu-util as [[Flashing_openmoko|normal]] and the ip address and cidr are the same as the openmoko build (192.168.0.202/24) :D - Simple, Eh?

=== Qtopia AND OpenMoko ===
Why choose when you can have both ;)

I assume you allready have some recent version of OpenMoko on your Neo1973. If not, have a look [[Flashing_openmoko|here]].

First backup everything on your micro-sd card you don't want to loose as we are going to create a new filesystem on it. This is necessary beacause vfat doesnt support links. Then ssh to your neo and do:
umount /dev/mmcblk0p1
mkfs.ext3 /dev/mmcblk0p1
mount /dev/mmcblk0p1

On your desktop: Get "Developer root filesystem" [http://www.qtopia.net/modules/devices/openmoko.php from here]. Get the opt/Qtopia folder plus the qpe init script out of the archive repack and copy it to your neo. One could do this like this:
tar xzf ficgta01-qtopia-developer-rootfs.tgz opt/Qtopia etc/init.d/qpe
mv opt/Qtopia etc/init.d/qpe . && rm -r opt etc
tar czf Qtopia.tar.gz Qtopia qpe
scp Qtopia.tar.gz root@192.168.0.202:/media/card/

On your neo again: unpack the archive you just copied and link the Qtopia folder to /opt/Qtopia. Then move the init script to /etc/init.d/:
cd /media/card
tar xzf Qtopia.tar.gz
mkdir -p /opt
ln -s /media/card/Qtopia /opt/Qtopia
mv qpe /etc/init.d

Now kill the x server and gsmd and start Qtopia (this can take some time):
/etc/init.d/xserver-nodm stop
/etc/init.d/gsmd stop
/etc/init.d/qpe start

Where from here? You could put the last step in a script and start it from a terminal on your phone. But much nicer would be if you could choose between both interfaces on init time and have some small application in Qtopia/OpenMoko to switch.

=== Build your own ===
If you want to build qtopia for yourself you can download the [ftp://ftp.trolltech.com/qtopia/tech-preview/ technical preview] or [ftp://ftp.trolltech.com/qtopia/snapshots/ snapshots]

== Tips ==
Most things seem to work out of the box, however you may need to use the following command to get audio:
alsactl -f /etc/alsa/gsmhandset.state restore
Or put this command in /etc/init.d/qpe line 64

Do not switch themes. Only the default theme is usable. For example, once you switch themes, the lock feature continues to work, but only if you unlock using the smallest # keypad in the world.

Suspend support is very flaky. The neo often shuts off from a suspend state. It will not wake from suspend for an incoming call or text message (someone try setting an alarm and report results here). To turn suspend off (this will of course use the batteries very quickly), hit the down arrow next to the suspend setting in the power management until it says "Off".

When using the virtual keyboard, do a quick flick up or down over the keyboard to access numbers/symbols/capitals.

In summary, Qtopia on the Neo1973 is much closer to being ready than OpenMoko as of this writing. However, sound and suspend support prevent it from being at all useful as a cell phone (as a landline that doesn't ring but instead vibrates, it works ok).

== Screenshots ==

Here are some screenshots of Qtopia runing on a Neo 1973. Personally I find it very impressive...

[[Image:Qtopia001.png]]

[[Image:Qtopia002.png]]

[[Image:Qtopia003.png]]

[[Image:Qtopia004.png]]

[[Image:Qtopia005.png]]

[[Image:Qtopia006.png]]

== Videos ==

http://www.youtube.com/watch?v=YW5q8SpY7t4
http://www.youtube.com/watch?v=iOG_mtSEMgs

For full size videos, 346 MiB:

http://linuxtracker.org/download.php?id=4613&name=qt_on_neo1973_videos.torrent

Qtopia on Neo1973

2007-09-29T17:03:13Z

C7: reorganisation

Qtopia on Neo1973

2007-09-29T16:56:40Z

C7: added tips section

{{Languages|Qtopia_on_Neo_1973}}

== Where to get it ==
You can get everything you need [http://www.qtopia.net/modules/devices/openmoko.php from here]. Currently the flash tarball has the 2.6.21 openmoko kernel and a Qtopia phone edition jffs2 flash
image cross-compiled for the Neo.

If you want to build qtopia for yourself you can download the [ftp://ftp.trolltech.com/qtopia/tech-preview/ technical preview] or [ftp://ftp.trolltech.com/qtopia/snapshots/ snapshots]

It appears you must clear the flash chunks first (if you have not updated your uboot. If you have, you may skip this step). Get into uboot console [http://wiki.openmoko.org/wiki/Uboot#Accessing_the_bootloader_prompt] and enter

# nand erase kernel
# nand erase rootfs

Download and use dfu-util as normal [http://wiki.openmoko.org/wiki/Flashing_openmoko] and the ip address and cidr are the same as the openmoko build (192.168.0.202/24) :D - Simple, Eh?

== Tips ==
Most things seem to work out of the box, however you may need to use the following command to get audio:

# alsactl -f /etc/alsa/gsmhandset.state restore
Or put this command in /etc/init.d/qpe line 64

Do not switch themes. Only the default theme is usable. For example, once you switch themes, the lock feature continues to work, but only if you unlock using the smallest # keypad in the world.

Suspend support is very flaky. The neo often shuts off from a suspend state. It will not wake from suspend for an incoming call or text message (someone try setting an alarm and report results here). To turn suspend off (this will of course use the batteries very quickly), hit the down arrow next to the suspend setting in the power management until it says "Off".

When using the virtual keyboard, do a quick flick up or down over the keyboard to access numbers/symbols/capitals.

In summary, Qtopia on the Neo1973 is much closer to being ready than OpenMoko as of this writing. However, sound and suspend support prevent it from being at all useful as a cell phone (as a landline that doesn't ring but instead vibrates, it works ok).

== Screenshots ==

Here are some screenshots of Qtopia runing on a Neo 1973. Personally I find it very impressive...

[[Image:Qtopia001.png]]

[[Image:Qtopia002.png]]

[[Image:Qtopia003.png]]

[[Image:Qtopia004.png]]

[[Image:Qtopia005.png]]

[[Image:Qtopia006.png]]

== Videos ==

http://www.youtube.com/watch?v=YW5q8SpY7t4
http://www.youtube.com/watch?v=iOG_mtSEMgs

For full size videos, 346 MiB:

http://linuxtracker.org/download.php?id=4613&name=qt_on_neo1973_videos.torrent

User:C7

2007-09-18T20:13:29Z

C7: /* Contact */

== Contact ==
* Name: Ben Hagen
* Email: akvo ( at ) hispeed.ch
* IRC: irc.freenode.net #openmoko (nick: C7)

== OpenExpo'07 Zurich, Switzerland ==

I'm organising an OpenMoko booth at the [http://www.openexpo.ch/openexpo-2007-zuerich/ OpenExpo'07] in Zurich, Switzerland. Any help welcome ;) More infos [[OpenMoko_Local_Groups: Switzerland|here]].

Openmoko Local Groups: Switzerland

2007-09-18T20:11:52Z

C7: /* todo */

== Current Activities ==

=== OpenMoko booth at the OpenExpo'07 Zurich ===

* Date: 19./20. September 2007
* Website: [http://www.openexpo.ch/openexpo-2007-zuerich/ link]
* Brochure: [http://www.openexpo.ch/fileadmin/documents/OpenExpo_2007Zuerich_Prospekt.pdf link]

==== who? ====
*[[User:C7|C7]]
*[[User:Mickey|Mickey]] (is giving a talk about OpenMoko on Thursday 11.00h)
*[[User:Obri|Obri]]?
* ...you?

==== done ====
*Schedule
*Flyers ([[:Image:Openexpo-flyer-draft.png|draft]])
*List of hardware needed (Phones, Laptop, ...)
*T-Shirts

Any help welcome ;)

== User in Switzerland ==

*[[User:yvanxxx|yvanxxx]]
*

OpenMoko2007.2

2007-08-19T20:16:07Z

C7: /* How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) */ added a link to MokoMakefile

== FAQ ==
=== What is 2007.2? ===

As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun.

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.

An official announcement is expected soon (Aug 19).

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

=== What are differences between 2007.1 and 2007.2? ===

=== Where to get images? ===

[[OpenMoko2007.2#Pre-built_snapshot_images|Unofficial images]]

=== Where are official images? ===

No official images yet.

=== My mrxvt (terminal) fonts are huge. ===

Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:
#define MIN_XFT_FONT_SIZE (2)
and rebuild mrxvt & openmoko-devel-image.

End edit /etc/mrxvt/mrxvt.conf
Mrxvt.xftSize: 4
Mrxvt.xftHint: 1

== How to build ==

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.

'''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.'''

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.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

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.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

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. :-)

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

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.

==== openmoko-libs FTBFS ====
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:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

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.

==== gtk+ fails building w/ gtkcombobox.c ====

If you get these errors:

gtkcombobox.c: In function 'gtk_combo_box_size_request':
gtkcombobox.c:1859: warning: unused variable 'font_desc'
gtkcombobox.c:1858: warning: unused variable 'metrics'
gtkcombobox.c:1857: warning: unused variable 'context'
gtkcombobox.c:1855: warning: unused variable 'arrow_size'
gtkcombobox.c:1854: warning: unused variable 'font_size'
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once
gtkcombobox.c:1962: error: for each function it appears in.)
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function)

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:

Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )

--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200
@@ -1948,6 +1948,12 @@
gtk_combo_box_size_allocate (GtkWidget *widget,
GtkAllocation *allocation)
{
+ gint font_size;
+ gint arrow_size;
+ PangoContext *context;
+ PangoFontMetrics *metrics;
+ PangoFontDescription *font_desc;
+
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);
gint focus_width, focus_pad;
GtkAllocation child;

==== Building glibc fails with a segfault in QEMU ====

If your build aborts and you see something like this:

NOTE: package glibc-2.5: started
NOTE: package glibc-2.5-r6: task do_package: started
NOTE: preparing tree for binary locale generation
NOTE: generating locale en_US (UTF-8)
qemu: uncaught target signal 11 (Segmentation fault) - exiting

...

NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed

Try editing your local.conf file. Change:

ENABLE_BINARY_LOCALE_GENERATION = "1"

to

ENABLE_BINARY_LOCALE_GENERATION = "0"

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.

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:

PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"
SRCDATE_qemu-native = 20070701

==== libxml2-native fails with xmlCatalogPtr errors ====

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:

--- xmlversion.h 2007-08-17 10:45:42.000000000 +0100
+++ xmlversion.h 2007-08-17 10:51:36.000000000 +0100
@@ -219,7 +219,7 @@
*
* Whether the Catalog support is configured in
*/
-#if 0
+#if 1
#define LIBXML_CATALOG_ENABLED
#endif

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.

=== Flashing with MokoMakefile ===
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:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

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. :-)

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:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==

'''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.
'''

'''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):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
sudo apt-get install \
autoconf automake automake1.9 \
bison \
ccache cogito \
cvs \
diffstat \
docbook \
flex \
gcc g++ gawk gcj gettext git-core \
help2man \
libc6-dev libglib2.0-dev libtool libxext-dev\
m4 make \
patch pkg-config \
python python-dev python2.4 python2.4-dev python-psyco \
sed \
sharutils \
texinfo texi2html \
unzip \
subversion \
sysutils \
texinfo \
bzip2

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.
mkdir -p monotone
wget http://www.openembedded.org/snapshots/\
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2
bunzip2 monotone/nslu2-linux.mtn.bz2

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.

(current directory(pwd) is /path/to/OM2007.2)
ln -s /path/to/OM2007.1/OE.mtn monotone/nslu2-linux.mtn

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.

(current directory(pwd) is /path/to/OM2007.2)
ln -s /path/to/OM2007.1/sources downloads

Go build ;)
make openmoko-devel-image

* If you an encounter an error with monotone similar to the following:

mtn: misuse: database monotone/nslu2-linux.mtn is laid out according to an old schema

Then you need to upgrade nslu2-linux.mtn Use the following command:

# mtn --db monotone/nslu2-linux.mtn db migrate

== Pre-built snapshot images ==
http://ipkg.nslu2-linux.org/feeds/openmoko/images/

http://people.openmoko.org/mickey/images/ (Confirmed working)

http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/fic-gta01/

[[Category:OpenMoko2007.2| ]]

OpenMoko2007.2

2007-08-19T20:12:21Z

C7: /* Pre-built snapshot images */ images from buildhost added

== FAQ ==
=== What is 2007.2? ===

As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun.

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.

An official announcement is expected soon (Aug 19).

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

=== What are differences between 2007.1 and 2007.2? ===

=== Where to get images? ===

[[OpenMoko2007.2#Pre-built_snapshot_images|Unofficial images]]

=== Where are official images? ===

No official images yet.

=== My mrxvt (terminal) fonts are huge. ===

Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:
#define MIN_XFT_FONT_SIZE (2)
and rebuild mrxvt & openmoko-devel-image.

End edit /etc/mrxvt/mrxvt.conf
Mrxvt.xftSize: 4
Mrxvt.xftHint: 1

== How to build ==

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.

'''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.'''

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.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

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.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

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. :-)

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

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.

==== openmoko-libs FTBFS ====
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:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

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.

==== gtk+ fails building w/ gtkcombobox.c ====

If you get these errors:

gtkcombobox.c: In function 'gtk_combo_box_size_request':
gtkcombobox.c:1859: warning: unused variable 'font_desc'
gtkcombobox.c:1858: warning: unused variable 'metrics'
gtkcombobox.c:1857: warning: unused variable 'context'
gtkcombobox.c:1855: warning: unused variable 'arrow_size'
gtkcombobox.c:1854: warning: unused variable 'font_size'
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once
gtkcombobox.c:1962: error: for each function it appears in.)
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function)

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:

Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )

--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200
@@ -1948,6 +1948,12 @@
gtk_combo_box_size_allocate (GtkWidget *widget,
GtkAllocation *allocation)
{
+ gint font_size;
+ gint arrow_size;
+ PangoContext *context;
+ PangoFontMetrics *metrics;
+ PangoFontDescription *font_desc;
+
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);
gint focus_width, focus_pad;
GtkAllocation child;

==== Building glibc fails with a segfault in QEMU ====

If your build aborts and you see something like this:

NOTE: package glibc-2.5: started
NOTE: package glibc-2.5-r6: task do_package: started
NOTE: preparing tree for binary locale generation
NOTE: generating locale en_US (UTF-8)
qemu: uncaught target signal 11 (Segmentation fault) - exiting

...

NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed

Try editing your local.conf file. Change:

ENABLE_BINARY_LOCALE_GENERATION = "1"

to

ENABLE_BINARY_LOCALE_GENERATION = "0"

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.

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:

PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"
SRCDATE_qemu-native = 20070701

==== libxml2-native fails with xmlCatalogPtr errors ====

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:

--- xmlversion.h 2007-08-17 10:45:42.000000000 +0100
+++ xmlversion.h 2007-08-17 10:51:36.000000000 +0100
@@ -219,7 +219,7 @@
*
* Whether the Catalog support is configured in
*/
-#if 0
+#if 1
#define LIBXML_CATALOG_ENABLED
#endif

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.

=== Flashing with MokoMakefile ===
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:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

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. :-)

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:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==

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.

[disclaimer]

'''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):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
sudo apt-get install \
autoconf automake automake1.9 \
bison \
ccache cogito \
cvs \
diffstat \
docbook \
flex \
gcc g++ gawk gcj gettext git-core \
help2man \
libc6-dev libglib2.0-dev libtool libxext-dev\
m4 make \
patch pkg-config \
python python-dev python2.4 python2.4-dev python-psyco \
sed \
sharutils \
texinfo texi2html \
unzip \
subversion \
sysutils \
texinfo \
bzip2

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.
mkdir -p monotone
wget http://www.openembedded.org/snapshots/\
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2
bunzip2 monotone/nslu2-linux.mtn.bz2

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.

(current directory(pwd) is /path/to/OM2007.2)
ln -s /path/to/OM2007.1/OE.mtn monotone/nslu2-linux.mtn

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.

(current directory(pwd) is /path/to/OM2007.2)
ln -s /path/to/OM2007.1/sources downloads

Go build ;)
make openmoko-devel-image

* If you an encounter an error with monotone similar to the following:

mtn: misuse: database monotone/nslu2-linux.mtn is laid out according to an old schema

Then you need to upgrade nslu2-linux.mtn Use the following command:

# mtn --db monotone/nslu2-linux.mtn db migrate

== Pre-built snapshot images ==
http://ipkg.nslu2-linux.org/feeds/openmoko/images/

http://people.openmoko.org/mickey/images/ (Confirmed working)

http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/fic-gta01/

[[Category:OpenMoko2007.2| ]]

OpenMoko2007.2

2007-08-13T21:17:23Z

C7: /* Pre-built snapshot images */ added buildhost.openmoko.org

As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun.

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.

An official announcement is expected soon.

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

== How to build ==
'''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.'''

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.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

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.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

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. :-)

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

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.

==== openmoko-libs FTBFS ====
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:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

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.

==== gtk+ fails building w/ gtkcombobox.c ====

If you get these errors:

gtkcombobox.c: In function 'gtk_combo_box_size_request':
gtkcombobox.c:1859: warning: unused variable 'font_desc'
gtkcombobox.c:1858: warning: unused variable 'metrics'
gtkcombobox.c:1857: warning: unused variable 'context'
gtkcombobox.c:1855: warning: unused variable 'arrow_size'
gtkcombobox.c:1854: warning: unused variable 'font_size'
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once
gtkcombobox.c:1962: error: for each function it appears in.)
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function)

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:

Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )

--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200
@@ -1948,6 +1948,12 @@
gtk_combo_box_size_allocate (GtkWidget *widget,
GtkAllocation *allocation)
{
+ gint font_size;
+ gint arrow_size;
+ PangoContext *context;
+ PangoFontMetrics *metrics;
+ PangoFontDescription *font_desc;
+
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);
gint focus_width, focus_pad;
GtkAllocation child;

=== Flashing with MokoMakefile ===
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:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

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. :-)

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:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==
[disclaimer]

'''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):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
sudo apt-get install \
autoconf automake automake1.9 \
bison \
ccache cogito \
cvs \
diffstat \
docbook \
flex \
gcc g++ gawk gcj gettext git-core \
help2man \
libc6-dev libglib2.0-dev libtool \
m4 make \
patch pkg-config \
python python-dev python2.4 python2.4-dev python-psyco \
sed \
sharutils \
texinfo texi2html \
unzip \
subversion \
sysutils \
texinfo \
bzip2

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.
mkdir -p monotone
wget http://www.openembedded.org/snapshots/\
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2
bunzip2 monotone/nslu2-linux.mtn.bz2

Go build ;)
make openmoko-image

* If you an encounter an error with monotone similar to the following:

mtn: misuse: database monotone/nslu2-linux.mtn is laid out according to an old schema

Then you need to upgrade nslu2-linux.mtn Use the following command:

# mtn --db monotone/nslu2-linux.mtn db migrate

== Pre-built snapshot images ==
http://ipkg.nslu2-linux.org/feeds/openmoko/images/

http://people.openmoko.org/mickey/images/ (Confirmed working)

http://buildhost.openmoko.org/tmp2/deploy/glibc/images/fic-gta01/

[[Category:OpenMoko2007.2| ]]

OpenMoko2007.2

2007-08-07T00:30:03Z

C7: /* How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) */ grrr should better go to bed now ;)

As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun.

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.

An official announcement is expected soon.

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

== How to build ==
'''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.'''

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.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

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.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

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. :-)

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

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.

==== openmoko-libs FTBFS ====
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:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

Now put a dash (''#'') 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.

=== Flashing with MokoMakefile ===
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:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

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. :-)

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:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==
[disclaimer]

'''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):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
sudo apt-get install \
autoconf automake automake1.9 \
bison \
ccache cogito \
cvs \
diffstat \
docbook \
flex \
gcc g++ gawk gcj gettext git-core \
libc6-dev libglib2.0-dev libtool \
m4 make \
patch pkg-config \
python python-dev python2.4 python2.4-dev python-psyco \
sed \
sharutils \
texinfo texi2html \
unzip \
subversion \
sysutils \
texinfo \
bzip2

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 downgrade to monotone 0.28.
sudo apt-get remove monotone #if there is one allready
sudo apt-get install \
libboost-date-time1.33.1 libboost-filesystem1.33.1 libboost-regex1.33.1
wget http://monotone.ca/downloads/0.28/monotone_0.28-dapper0.1_i386.deb
sudo dpkg -i monotone_0.28-dapper0.1_i386.deb
echo monotone "hold" | sudo dpkg --set-selections

Another possible solution for this is to download a suitable mtn db from http://www.openembedded.org/snapshots/ and use this.
mkdir -p monotone
wget http://www.openembedded.org/snapshots/\
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2
bunzip2 monotone/nslu2-linux.mtn.bz2

Go build ;)
make openmoko-image

[[Category:OpenMoko2007.2| ]]

OpenMoko2007.2

2007-08-07T00:28:39Z

C7: /* How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) */ needs sudo

As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun.

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.

An official announcement is expected soon.

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

== How to build ==
'''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.'''

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.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

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.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

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. :-)

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

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.

==== openmoko-libs FTBFS ====
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:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

Now put a dash (''#'') 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.

=== Flashing with MokoMakefile ===
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:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

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. :-)

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:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==
[disclaimer]

'''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):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
sudo apt-get install \
autoconf automake automake1.9 \
bison \
ccache cogito \
cvs \
diffstat \
docbook \
flex \
gcc g++ gawk gcj gettext git-core \
libc6-dev libglib2.0-dev libtool \
m4 make \
patch pkg-config \
python python-dev python2.4 python2.4-dev python-psyco \
sed \
sharutils \
texinfo texi2html \
unzip \
subversion \
sysutils \
texinfo \
bzip2

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 downgrade to monotone 0.28.
sudo apt-get remove monotone #if there is one allready
sudo apt-get install \
libboost-date-time1.33.1 libboost-filesystem1.33.1 libboost-regex1.33.1
wget http://monotone.ca/downloads/0.28/monotone_0.28-dapper0.1_i386.deb
sudo dpkg -i monotone_0.28-dapper0.1_i386.deb
sudo echo monotone "hold" | sudo dpkg --set-selections

Another possible solution for this is to download a suitable mtn db from http://www.openembedded.org/snapshots/ and use this.
mkdir -p monotone
wget http://www.openembedded.org/snapshots/\
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2
bunzip2 monotone/nslu2-linux.mtn.bz2

Go build ;)
make openmoko-image

[[Category:OpenMoko2007.2| ]]

OpenMoko2007.2

2007-08-07T00:25:19Z

C7: /* How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) */

As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun.

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.

An official announcement is expected soon.

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

== How to build ==
'''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.'''

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.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

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.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

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. :-)

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

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.

==== openmoko-libs FTBFS ====
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:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

Now put a dash (''#'') 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.

=== Flashing with MokoMakefile ===
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:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

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. :-)

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:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==
[disclaimer]

'''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):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
sudo apt-get install \
autoconf automake automake1.9 \
bison \
ccache cogito \
cvs \
diffstat \
docbook \
flex \
gcc g++ gawk gcj gettext git-core \
libc6-dev libglib2.0-dev libtool \
m4 make \
patch pkg-config \
python python-dev python2.4 python2.4-dev python-psyco \
sed \
sharutils \
texinfo texi2html \
unzip \
subversion \
sysutils \
texinfo \
bzip2

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 downgrade to monotone 0.28.
sudo apt-get remove monotone #if there is one allready
sudo apt-get install \
libboost-date-time1.33.1 libboost-filesystem1.33.1 libboost-regex1.33.1
wget http://monotone.ca/downloads/0.28/monotone_0.28-dapper0.1_i386.deb
sudo dpkg -i monotone_0.28-dapper0.1_i386.deb
echo monotone "hold" | dpkg --set-selections

Another possible solution for this is to download a suitable mtn db from http://www.openembedded.org/snapshots/ and use this.
mkdir -p monotone
wget http://www.openembedded.org/snapshots/\
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2
bunzip2 monotone/nslu2-linux.mtn.bz2

Go build ;)
make openmoko-image

[[Category:OpenMoko2007.2| ]]

OpenMoko2007.2

2007-08-06T19:22:27Z

C7: /* How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) */ get things in a logical order

As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun.

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.

An official announcement is expected soon.

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

== How to build ==
'''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.'''

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.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

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.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

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. :-)

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

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.

==== openmoko-libs FTBFS ====
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:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

Now put a dash (''#'') 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.

=== Flashing with MokoMakefile ===
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:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

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. :-)

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:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==
[disclaimer]

'''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):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
make setup-host-ubuntu && sudo apt-get install diffstat python-psyco

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 downgrade to monotone 0.28.
sudo apt-get remove monotone
wget http://monotone.ca/downloads/0.28/monotone_0.28-dapper0.1_i386.deb
sudo dpkg -i monotone_0.28-dapper0.1_i386.deb
echo monotone "hold" | dpkg --set-selections

Another possible solution for this is to download a suitable mtn db from http://www.openembedded.org/snapshots/ and use this.
mkdir -p monotone
wget http://www.openembedded.org/snapshots/OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2
bunzip2 monotone/nslu2-linux.mtn.bz2

Go build ;)
make openmoko-image

[[Category:OpenMoko2007.2| ]]

OpenMoko2007.2

2007-08-06T18:58:28Z

C7: /* How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) */ added link to the nslu2-linux wiki

As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun.

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.

An official announcement is expected soon.

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

== How to build ==
'''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.'''

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.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

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.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

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. :-)

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

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.

==== openmoko-libs FTBFS ====
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:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

Now put a dash (''#'') 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.

=== Flashing with MokoMakefile ===
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:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

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. :-)

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:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==
[disclaimer]

'''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):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

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 downgrade to monotone 0.28.
sudo apt-get remove monotone
wget http://monotone.ca/downloads/0.28/monotone_0.28-dapper0.1_i386.deb
sudo dpkg -i monotone_0.28-dapper0.1_i386.deb
echo monotone "hold" | dpkg --set-selections

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
make setup-host-ubuntu && sudo apt-get install diffstat python-psyco

Go build ;)
make openmoko-image

[[Category:OpenMoko2007.2| ]]

OpenMoko2007.2

2007-08-06T18:47:09Z

C7: How to build using nslu2-linux MasterMakefile (Ubuntu 7.04)

As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun.

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.

An official announcement is expected soon.

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

== How to build ==
'''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.'''

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.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

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.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

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. :-)

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

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.

==== openmoko-libs FTBFS ====
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:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

Now put a dash (''#'') 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.

=== Flashing with MokoMakefile ===
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:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

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. :-)

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:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ==
[disclaimer]

'''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):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

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 downgrade to monotone 0.28.
sudo apt-get remove monotone
wget http://monotone.ca/downloads/0.28/monotone_0.28-dapper0.1_i386.deb
sudo dpkg -i monotone_0.28-dapper0.1_i386.deb
echo monotone "hold" | dpkg --set-selections

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux MasterMakefile:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
make setup-host-ubuntu && sudo apt-get install diffstat python-psyco

Go build ;)
make openmoko-image

[[Category:OpenMoko2007.2| ]]

Ipkg

2007-08-04T11:43:44Z

C7: typo

The practical way to install software on OpenMoko is with the [http://handhelds.org/moin/moin.cgi/Ipkg Ipkg package manager], possibly via the graphical [[Application Manager]]. Naturally, you need to have obtained an OpenMoko system by other means initially.

For the latest ipk package files from buildhost put the following lines in your /etc/ipkg/base-feed.conf:
src/gz all http://buildhost.openmoko.org/tmp/deploy/ipk/all/
src/gz armv4t http://buildhost.openmoko.org/tmp/deploy/ipk/armv4t/
src/gz fic-gta01 http://buildhost.openmoko.org/tmp/deploy/ipk/fic-gta01/

In the shell, "ipkg update" will update the list of available packages, "ipkg upgrade" will download and install all packages that have a newer version available and "ipkg install new-app" will download and install "new-app".

== History ==

Ipkg re-implements for embedded systems the Debian tools dpkg, apt, and apt-get. For example, it uses much less disk space for the package metadata.

[[Category:OpenMoko]]
[[Category:Implemented]]

Ipkg

2007-08-04T11:39:38Z

C7: added ipk feed from buildhost

The practical way to install software on OpenMoko is with the [http://handhelds.org/moin/moin.cgi/Ipkg Ipkg package manager], possibly via the graphical [[Application Manager]]. Naturally, you need to have obtained an OpenMoko system by other means initially.

For the latest ipk package files from buildhost put the following lines in your /etc/ipkg/base-feed.conf:
src/gz all http://buildhost.openmoko.org/tmp/deploy/ipk/all/
src/gz armv4t http://buildhost.openmoko.org/tmp/deploy/ipk/armv4t/
src/gz fic-gta01 http://buildhost.openmoko.org/tmp/deploy/ipk/fic-gta01/

In the shell, "ipkg update" will update the list of available packages, "ipkg upgrade" will download and install all packages that have a newer version available" and "ipkg install new-app" will download and install "new-app".

== History ==

Ipkg re-implements for embedded systems the Debian tools dpkg, apt, and apt-get. For example, it uses much less disk space for the package metadata.

[[Category:OpenMoko]]
[[Category:Implemented]]

Openmoko Local Groups: Switzerland

2007-07-26T15:24:30Z

C7: /* who? */ you?

== Current Activities ==

=== OpenMoko booth at the OpenExpo'07 Zurich ===

* Date: 19./20. September 2007
* Website: [http://www.openexpo.ch/openexpo-2007-zuerich/ link]
* Brochure: [http://www.openexpo.ch/fileadmin/documents/OpenExpo_2007Zuerich_Prospekt.pdf link]

==== who? ====
*[[User:C7|C7]]
*[[User:Mickey|Mickey]] (is giving a talk about OpenMoko on Thursday 11.00h)
* ...you?

==== todo ====
*Schedule
*A1 Poster
*Flyers
*List of hardware needed (Phones, Laptop, ...)
*T-Shirts?
*...?

Any help welcome ;)

[[Category:Community]]

Openmoko Local Groups: Switzerland

2007-07-26T15:22:53Z

C7: /* OpenMoko booth at the OpenExpo'07 Zurich */ link to final version of the "brochure"

== Current Activities ==

=== OpenMoko booth at the OpenExpo'07 Zurich ===

* Date: 19./20. September 2007
* Website: [http://www.openexpo.ch/openexpo-2007-zuerich/ link]
* Brochure: [http://www.openexpo.ch/fileadmin/documents/OpenExpo_2007Zuerich_Prospekt.pdf link]

==== who? ====
*[[User:C7|C7]]
*[[User:Mickey|Mickey]] (is giving a talk about OpenMoko on Thursday 11.00h)

==== todo ====
*Schedule
*A1 Poster
*Flyers
*List of hardware needed (Phones, Laptop, ...)
*T-Shirts?
*...?

Any help welcome ;)

[[Category:Community]]

Openmoko Local Groups: Switzerland

2007-07-23T10:00:30Z

C7: /* OpenMoko booth at the OpenExpo'07 Zurich */ todo

== Current Activities ==

=== OpenMoko booth at the OpenExpo'07 Zurich ===

* Date: 19./20. September 2007
* Website: [http://www.openexpo.ch/openexpo-2007-zuerich/ link]

Draft text for the OpenExpo brochure:
<pre>OpenMoko ist ein Versuch, das erste Mobiltelefon der Welt zu erschaffen, das ausschliesslich auf
offener Software basiert. Wir glauben an Standards die von einer Community geschaffen wurden, anstatt von
einem grossen Unternehmen. OpenMoko ist so konzipiert, dass es auf allen Mobiltelefonen laufen wird, die
auf Linux basieren. Das erste komplett unterstützte ist das Neo1973.

http://www.openmoko.org</pre>

==== who? ====
*[[User:C7|C7]]
*[[User:Mickey|Mickey]] (is giving a talk about OpenMoko on Thursday 11.00h)

==== todo ====
*Schedule
*A1 Poster
*Flyers
*List of hardware needed (Phones, Laptop, ...)
*T-Shirts?
*...?

Any help welcome ;)

[[Category:Community]]

Openmoko Local Groups: Switzerland

2007-07-14T02:03:57Z

C7: OpenExpo