http://openmoko.org/api.php?action=feedcontributions&user=Youshe&feedformat=atomOpenmoko - User contributions [en]2024-03-28T16:31:54ZUser contributionsMediaWiki 1.19.24http://openmoko.org/wiki/User_talk:DrizztUser talk:Drizzt2008-09-23T15:11:21Z<p>Youshe: New page: == Sim cards == Hi, to complete your list, I have a french Orange card bought in 2003 I think. Calls and SMS worked fine. Maybe this link may help in something : http://www.forum.logos-...</p>
<hr />
<div>== Sim cards ==<br />
<br />
Hi, to complete your list, I have a french Orange card bought in 2003 I think. Calls and SMS worked fine. <br />
<br />
Maybe this link may help in something : http://www.forum.logos-et-sonneries-portable.com/1694_15-clone-iphone-cect-p168.html ?<br />
<br />
My sim card has a 98 at the 4th and 5th position (with J2RE S). I don't know if it can help ?</div>Youshehttp://openmoko.org/wiki/Openmoko_under_QEMU/frOpenmoko under QEMU/fr2008-09-13T18:49:53Z<p>Youshe: Début de traduction. La suite à venir !</p>
<hr />
<div>[http://en.wikipedia.org/wiki/Qemu QEMU] peut être utilisé de trois façons différentes pour tester Openmoko. Suivant le pourquoi de votre utilisation de l'émulateur, vous devriez choisir la plateforme cible.<br />
<br />
*''PC'' - Openmoko peut être utilisé pour s'exécuter sur du matériel i383, 32 ou 64 bits et est probablement la façon la plus rapide de procéder pour tester Openmoko dans le but d'évaluer ce à quoi il ressemble et ce que l'on peut en faire. Dans ce scénario, QEMU ne servirait qu'à isoler votre installation d'Openmoko du système normal de l'ordinateur (ou si vous n'utilisez pas un système UNIX). Qemu propose une façon non intrusive de disposer d'un linux fonctionnel rapidement. Plus d'informations sont disponibles dans la [[FAQ]] et [[Getting Openmoko working on host with Xoo|ici]].<br />
<br />
*''Integrator/CP'' - Ceci est la machine ARM par défaut que QEMU connait. Cette cible est utilisée avec MACHINE="qemuarm" et est suffisante pour exécuter l'image rootfs originelle d'Openmoko. Cependant, cela n'émule aucun [[:Category:Neo1973 Hardware | matériel du Neo1973]] à l'exception le CPU minimal. Plus d'informations dans la [[FAQ#Q:_Is_there_an_emulator_available_for_Openmoko.3F|FAQ]].<br />
<br />
*''Neo1973'' - L'arbre Qemu est disponible des débots Openmoko et est capable d'amuler la plupart (mais pas la totalité) du matériel actuel du [[Neo1973]] (GTA01). De plus, l'émulation du Neo FreeRunner est en cours de travail. Lorsque toutes les parties de l'émulateur seront matures, notre code sera uploadé et fusionné avec la branche principale de développement de l'arbre Qemu.<br />
<br />
== Emulation du Neo1973 ==<br />
<br />
Cette cible devrait normalement exécuter les images rootfs originelle d'Openmoko, mais devrait aussi être capable d'exécuter le u-boot et les images noyaux utilisés par le Neo 1973 (GTA01) sans modification. Hormis les autres différences, vous allez remarquer qu'entre cette approche et celle la cible Integrator/CP, vous aurez une résolution d'écran correcte, de (fausses) lecture de batterie, et d'autres joyeusetés. A l'heure actuelle, les points manquant à l'émulateur sont : [[Hardware:AGPS|AGPS]] et le [[Bluetooth]] - ces choses devraient fonctionner, tout comme l'utilisabilité générale. Même avec ces choses manquantes, Qemu devrait fournir une aide substentielle aux développeurs pour le deverminage du noyau et du u-boot.<br />
<br />
Ce que Qemu '''*ne peut pas*''' être utilisé pour, et probablement aucnu autre émulateur, sont les mesures de vitesses et l'évaluation du sentiment général de performance d'Openmoko. Le code s'exécute dans qemu avec la vitesse maximum que votre ordinateur hôte peut fournir avec une latence correspondant à la transmission du code de la cible au code de l'hôte, et ce surcoût n'est pas le même pour chaque instruction. Cela signifit que mêm esi votre Neo virtuel fournit environ 100 BogoMIPS (Qui est la vitesse d'un Neo réel), les différentes actions effectuées dans l'émulateur ne s'exécuteront pas à la même vitesse. Sur la plupart des PC, vous remarquerez que le Neo virtuel est plus rapide que le réel (Les opérations Audio devraient être l'une des exceptions).<br />
<br />
=== Quel matériel est supporté ? ===<br />
<br />
Ebauche du status pour chaque composant nécessitant une émulation est disponible sur la page : [[:Category:Neo1973 Hardware | Neo1973 Hardware]].<br />
{|<br />
! Matériel !! Status !! Notes d'utilisation<br />
|- style="background-color:#eeeedd;"<br />
! colspan="3"|S3C2410A Processeur<br />
|-<br />
|Coeur ARM920T || Fonctionne || Déjà dans la branche principale de QEMU.<br />
|-<br />
|Fonctionnalités de bas niveau || Fonctionne || Cela inclue l'interface GPIO, DMA, controlleur d'interruptions, Timers, controlleur NAND, hôte MMC/SD, interfaces [[I2C]] et IIS, Mémoire & horloge & contrôleur de gestion de batterie, RAM.<br />
|-<br />
|Port série || Fonctionne || Use the "-serial" switch (maybe be specified multiple times) to tell QEMU where serial input/output should go to. GSM module will be connected on UART0.<br />
|-<br />
|RTC || Fonctionne || On start QEMU will load it with current time/date - the Neo1973 [[kernel]] doesn't use it for time/date source currently.<br />
|-<br />
|SPI || Fonctionne || The guest kernel can drive it using either the SPI interface or raw GPIO bitbanging.<br />
|-<br />
|LCD || Fonctionne || The virtual LCD will display contents in QEMU window unless "-nographic" is specified on command line.<br />
|-<br />
|ADC || Fonctionne || Mouse events in QEMU window generate what would be touchscreen events on a Neo1973 and are passed to the guest OS through the on-chip ADC.<br />
|-<br />
|OHCI USB || Fonctionne || This part is in mainline QEMU. Use the "-usb" switch to enable the controller and "usb_add" in QEMU monitor to attach new virtual or physical USB devices.<br />
|-<br />
|Slave USB || Fonctionne || Linux's dummy HCD in conjunction with gadget filesystem API is used to make the virtual Neo appear as a real one connected to the host computer. See [[#Setting up USB connection|Setting up USB connection]] below. (Experimental)<br />
|-<br />
|Watchdog || Fonctionne || This is one of the less important on-chip peripherals in S3C2410. It is however used by Linux for rebooting the board.<br />
|- style="background-color:#eeeedd;"<br />
! colspan="3"|[[I2C]] bus peripherals<br />
|-<br />
|[[PCF50606]] || Fonctionne || (Aka PMU) Fakes the battery charge level (set at 88%), POWER button, etc. Also contains an RTC, also unused by Linux.<br />
|-<br />
|[[LM4857]] || Fonctionne<br />
|-<br />
|[[WM8753L]] || Fonctionne || The CODEC is also connect to the CPU's IIS port. Basic [[Neo1973 Audio Subsystem|audio functionality]] is supported - see QEMU documentation on getting audio input/output from the emulator. Volume control has no effects.<br />
|- style="background-color:#eeeedd;"<br />
! colspan="3"|Other peripherals<br />
|-<br />
|Flash NAND || Fonctionne || However, some pieces are not confirmed to be completely compatible with the real hardware because of lack thereof. Use "-mtdblock flashimagefilenamehere" switch to point QEMU to your flash image. The file should be at least 69206016 bytes big.<br />
|-<br />
|JBT6K74-AS(PI) || Fonctionne || (Aka LCM) Wired to the SPI channel 1<br />
|-<br />
|Boutons || Fonctionne || Enter is the AUX button, Space is the POWER button. Wired to on-chip GPIO and PCF50606.<br />
|-<br />
|Carte SD || Fonctionne || This part is already in mainline QEMU. Use the "-sd cardimagegoeshere" switch to point QEMU to the card image. The regular QEMU monitor commands for removable media can also be used. The card works, however the on-chip host controller gave block length errors on heavy I/O despite working as described in specification. I suspect the kernel driver. DMA operation is not tested.<br />
|-<br />
|Bluetooth<br />
|style="background-color:#ffffcc;"|Fonctionne<br />
|A generic Bluetooth HCI (just like the BlueCore4 chip) is connected to internal USB hub (just like the Delta DBFM dongle). Currently qemu emulates no other bluetooth devices, so the dongle behaves as if there was no BT-enabled slaves around, being the only device on the piconet, i.e. is not really useful. Likely a Bluetooth keyboard will be emulated. A physical Bluetooth dongle can also be attached to the emulator (see USB documentation in QEMU).<br />
|-<br />
|[[GSM]] || Fonctionne || A fake modem is connected to UART0 understanding a (currently quite limited) subset of AT commands. Ultimately it should support as much functionality as possible (basic AT command set, fake GPRS connections, dialing and SMS send/receive). This way all parts of the phone subsystem (CALYPSO, TWL3014, TRF6151) will not have to be emulated. There is a possibility to wire a real GSM modem to QEMU's serial port, or the [http://doc.trolltech.com/qtopia-4.3-snapshot/fd-ModemSimulator.html phonesim] modem simulator from the ''Qtopia'' project (use the --enable-phonesim switch to ./configure) as well as the [http://doc.trolltech.com/qtopia-4.3-snapshot/modem-emulator.html atinterface] modem emulator, also from Qtopia.<br />
|-<br />
|[[Hardware:AGPS|AGPS]]<br />
|style="background-color:#ffcccc;"|To Do<br />
|There are obvious difficulties emulating the chip, but hopefully it can be made to present the guest OS with some fixed coordinates later when more is known about the chip. Again a real chip could be connected to QEMU's serial port.<br />
|}<br />
<br />
Current development is aiming for [[:Category:Neo1973_Hardware#GTA01Bv4 | GTA01Bv4]] compatibility; [[:Category:Neo1973_Hardware#GTA01Bv3 | earlier revisions]] can also be emulated if needed. The differences between the hardware revisions currently only manifest themselves in GPIO wiring. Hardware emulation is implemented in a clean-room manner using official specifications where possible.<br />
<br />
== Emulation du Neo FreeRunner ==<br />
<br />
La seconde version des téléphones Openmoko, les Neo FreeRunner (GTA02) ont vu plusieurs changements et améliorations materiels depuis le Neo1973 (GTA01). Qemu a un support complet du GTA01 (premier modèle), mais une émulation partielle du GTA02 est aussi plannifiée. Ceci doit inclure seulement les composants qui ont été ajoutés dans GTA02 et qui n'étaient pas présents dans GTA01.<br />
<br />
* The u-blox GPS chip (i.e. raw NMEA protocol).<br />
* The Atheros AR6001 WLAN / WiFi chip (and SDIO bus).<br />
* The two LIS accelerometers.<br />
* 128MiB, 1.8V NAND chip instead of 64MiB.<br />
<br />
Ce que cela veut dire c'est que la machine émulée ne sera pas intérieurement exactement comme le NeoFreeRunner, mais sera fonctionnellement la même. Ceci signifie par ailleurs qu'il faut un noyau modifié puisqu'il s'agit plus d'un GTA01 à l'intérieur. La source du noyau sera fournie comme un composant de qemu. Le bootloader utilisé sera le u-boot du GTA01.<br />
<br />
Cette approche est appelée paravirtualisation et est souvent utilisée comme une solution d'émulation pour plateformes mobiles. Pour un programmeur en espace utilisateur (Développeurs d'applications), la machine sera visible comme un GTA02. Pour un kernel hacker, cela sera une plateforme modifiée.<br />
<br />
S'il y a une initiative parmis les utilisateurs pour émuler plus précisément qu'expliqué ici le matériel du GTA02, patches/amélioration seront toujours bienvenues puisque le projet Qemu cherche à émuler le matériel réel et être aussi proche que possible du matériel réel (en d'autres mots, l'émulation totale est préférée à la paravirtualisation dans Qemu).<br />
<br />
=== Quel matériel est supporté ? ===<br />
<br />
Below is a rough status information for each of the components.<br />
{|<br />
! Hardware !! Status !! Usage notes<br />
|- style="background-color:#eeeedd;"<br />
! colspan="3"|GTA01 hardware<br />
|-<br />
|Processor, on-chip and external peripherals || Work || See the GTA01 supported hardware chart above. This hardware is at the base of the Neo FreeRunner emualtor. The same usage notes apply.<br />
|- style="background-color:#eeeedd;"<br />
! colspan="3"|GTA02 components<br />
|-<br />
|GPS || Works || A virtual GPS chip is connected to the second serial port of the virtual machine, exactly like on the Neo FreeRunner.<br />
|-<br />
|WLAN<br />
|style="background-color:#ffffcc;"|Partial support<br />
|The Atheros AR6001 (second firmware revision) is emulated to an extent that it gets detected by the kernel SDIO stack and registered as a network interface by the Atheros driver. It doesn't allow for actual network communication yet. The basic SDIO bus emulation is complete.<br />
|-<br />
|Accelerometers || Work || Two dummy accelerometers are connected to the virtual machine's I2C bus. They provide a constant 1G reading at the moment. One improvement idea to be implemented when there's some software available for testing, is to pass Qemu's SDL window movements as input to the virtual accelerometers, i.e. dragging the X window around would generate motion sensor events. These events would be two-dimensional but should be enough for Application developers to test their programs' interactions with the movements.<br />
|}<br />
<br />
== Comment puis l'utiliser ? ==<br />
<br />
Ces instructions parlent de l'émulateur du GTA01 (par défaut).<br />
<br />
=== En utilisant MokoMakefile ===<br />
<br />
This is arguably the easiest way of building qemu-neo1973 since you won't need to deal with the compiling and flashing processes yourself. See [[Using_QEMU_with_MokoMakefile|MokoMakefile]] for details.<br />
<br />
If you *just* build QEMU and use the official images by typing "make qemu" only (as opposed to setting up monotone and openembedded and building an entire new image for yourself with MokoMakefile), then the build takes less time than the manual instructions below (since it's all done automatically).<br />
<br />
=== Installation manuelle ===<br />
<br />
To obtain the latest source code for the emulator, you will want to do something like the following:<br />
<pre><br />
$ svn checkout https://svn.openmoko.org/trunk/src/host/qemu-neo1973<br />
$ cd qemu-neo1973<br />
</pre><br />
Now, we're going to configure and build the emulator (Note [[#Requirements|Requirements]] below):<br />
<pre><br />
$ ./configure --target-list=arm-softmmu # GCC 3.x will be required, see --cc=<br />
$ make<br />
</pre><br />
If you dont want gcc-3.x then you can apply patch from here<br />
https://bugs.gentoo.org/show_bug.cgi?id=160627<br />
like so<br />
<pre><br />
$ patch -p2 < quemu-gcc4.patch<br />
</pre><br />
<br />
See other available options for the configure script by appending "--help".<br />
Now you should have a working emulator under the name "arm-softmmu/qemu-system-arm". To run Openmoko you will also need to somehow install Openmoko on your virtual phone, which is totally clean of any software at this moment. There are several block devices to choose from, the best option is probably to do exactly what the Neo1973 manufacturer does before it ships the device to the final user. This process is described in [[Bootloader]], [[Kernel]], [[NAND bad blocks]] and [[Devirginator]] but you don't need to know all the details. Two scripts are provided to generate a firmware for your phone, as realistic as possible. First run<br />
<pre>$ openmoko/download.sh</pre><br />
which will look up the list of latest available Openmoko snapshot builds from buildhost.openmoko.org and choose the most recent [[u-boot]], Kernel, and root filesystem images, and download the images (unless they are already found in the openmoko/ directory). These binaries will be used by the flash.sh script. First make sure you have the netpbm package installed for some graphics conversion utilities. On Ubuntu this can be done by:<br />
<pre>sudo apt-get install netpbm</pre><br />
Then run:<br />
<pre>$ openmoko/flash.sh</pre><br />
which runs the emulator, loads u-boot into it and then uses u-boot's capability to program the Flash memory to install all the necessary parts of the system into the virtual Flash. It will also set up all the bootloading process including a boot menu (ENTER is [AUX] and SPACE is [POWER]), splash, u-boot environment and some default kernel parameters. If everything goes OK, the script should print a command which you can use to start using the emulator.<br />
<br />
QEMU has '''*tons*''' of commandline switches and things that can be configured. You can look them up in [http://bellard.org/qemu/user-doc.html QEMU user docs]. You will probably want to use the "-snapshot" switch, among other ones. Saving and restoring emulation state at any point (unrelated to "-snapshot") should work as per QEMU user docs too. In addition the monitor commands "help" and "info" are of great help. The monitor usually sits in second virtual console, thus ctrl-alt-2 and ctrl-alt-1 switch to monitor and back.<br />
<br />
=== Binaires précompilés ===<br />
<br />
Win32 binaries shipped with firmware can be downloaded from [http://yorick.keymeulen.com/openmoko-emulator-bin-20070625.rar openmoko-emulator-win32-bin-20070625.zip]. Tested on MS Windows XP and Vista Business.<br />
<br />
=== Neo FreeRunner (GTA02) ===<br />
<br />
Les instructions pour exécuter l'émulateur sont les mêmes pour le FreeRunner, mais la ligne de commande finale pour invoquer Qemu change. Au lieu de "-M gta01" comme nom de machine "-M gta02fake" doit être utilisé.<br />
<br />
Le noyau supportant l'émulateur GTA02 est optenu en appliquant le patch ''openmoko/linux-gta02-pseudo.patch'' disponible dans les sources de qemu-neo1973 au noyau openmoko 2.6.24 (vanilla linux-2.6.24 + le patchset de [http://svn.openmoko.org/branches/src/target/kernel/2.6.24.x/patches/]). <br />
Comme le support du noyau GTA02 est toujours en développement intensif, référez vous au fichier openmoko/README dans les sources de qemu-neo1973 pour les dernières instructions sur comment construire le noyau.<br />
<br />
Si un noyau normal d'Openmoko est utilisé avec l'émulateur Neo FreeRunner, il s'exécutera simplement comme si la machine était un GTA01 sans détecter les nouveaux périphériques.<br />
<br />
== Scripts utiles ==<br />
<br />
* openmoko/qemu-auto.sh<br />
<br />
launches qemu and opens a unix socket for communication. All additional parameters are passed to qemu. (e.g. openmoko/qemu-auto.sh -nographic launches the virtual machine with no graphics etc.).<br />
<br />
* openmoko/qemu-upload.sh <filename><br />
<br />
produces a SD card image with one partition with the given file(s) on it (you can pass a list of files) and inserts it into the phone. The Openmoko kernel should detect the event and the automounter should mount the partition. openmoko/qemu-auto.sh must be running already. If you pass no parameters, it ejects the media (the OM kernel is too dumb to detect this unfortunately). This will only work with gta01 emulation because gta02 has no SD.<br />
<br />
* openmoko/qemu-quit.sh<br />
<br />
powers the VM down cleanly.<br />
<br />
* openmoko/qemu-gadget.sh<br />
<br />
attempts to connect target's S3C USB slave to host's dummy HCD (if present and gadgetfs is mounted).<br />
<br />
== Prérequis ==<br />
<br />
This QEMU tree has only been tested on GNU/Linux. To get graphical (not counting VNC) and/or audio output from the emulator you will need either SDL or Cocoa installed on your computer. To enable audio, see the available switches to the ./configure script.<br />
<br />
The scripts that sit in openmoko/ require lynx, wget, python, netpbm and most GNU base utilities installed in standard locations. The netpbm package contains tools necessary for bootsplash image conversion.<br />
<br />
All of the build-time and run-time requirements listed in [http://bellard.org/qemu/user-doc.html QEMU documentation] apply. This includes zlib, etc. On distributions that use binary packages, remember that you need the packages ending in '''-dev''' or '''-devel'''.<br />
<br />
== Qemu et Gnu debugger ==<br />
<br />
QEMU lets you debug operating system kernels and bootloaders like you debug all other programs. To do this you will need a debugger that speaks the GDB remote debugging protocol - [http://sourceware.org/gdb/ GDB] is the obvious choice. Some cross toolchains come with GDB already set up. Otherwise building cross-GDB yourself is quick and easy (compared to building binutils and cross-gcc).<br />
<br />
To debug u-boot, load the file "u-boot" into gdb (not "u-boot.bin") that is produced by "make" when building u-boot. To debug a Linux kernel, load the file "vmlinux" from the main source directory into gdb. These files are in ELF format and contain all the symbol information and are not stripped of debugging data until you run "strip" on them, unlike "u-boot.bin" and "Image"/"zImage"/"uImage". Next, tell QEMU to enable the gdbserver by appending the "-s" switch or issuing "gdbserver" in the monitor. Use the command <pre>(gdb) target remote localhost:1234</pre> to make a connection to the emulator. From there you should be able to use all the usual GDB commands, including stepping instructions, setting breakpoints, watchpoints, inspecting stack, variables, registers and more. If gdb is running in the same directory from which it grabbed the ELF executable, the "edit" command should work so you can jump right to the source line which is executing.<br />
<br />
== Connexion réseau simple avec pppd ==<br />
<br />
One simple way to get a network connection from the emulated Neo is via an emulated serial port and [[pppd]]. Add ''-serial vc -serial pty'' to the [[QEMU command line]], and QEMU prints a device name on a line like "char device redirected to /dev/pts/12".<br />
<br />
On the Neo side, open a terminal and run the command "pppd nodetach debug /dev/ttySAC1".<br />
<br />
On the host computer side, open a root terminal and run the command "pppd nodetach debug 192.168.68.1:192.168.68.2 noauth /dev/pts/12", substituting the actual device name from above.<br />
<br />
Now on the host computer side, you should be able to "ping 192.168.68.2" and "ssh root@192.168.68.2".<br />
<br />
NB : If you see in pppd trace something like this "Received bad configure-rej: 12 06 00 00 00 00" again and again, you will ping but no application will work. It is probably the compression protocol (ccp) negotiation which fail. Add "noccp" to the two pppd commands like "pppd nodetach debug noccp /dev/ttySAC1".<br />
<br />
== Etablir une connexion internet sur votre neo émulé ==<br />
Before you start, you have to have a working pppd or USB connection, ([[#Simple_network_connection_with_pppd|see the previous chapter]] and [[#Setting up USB connection|the next chapter]])<br />
<br />
(I assume that your local ip-adress is 192.168.0.100 and your router is 192.168.0.1)<br />
<br />
In qemu terminal (or via ssh) type:<br />
<br />
<pre><br />
$ ifdown usb0<br />
$ route add default gw 192.168.68.1<br />
</pre><br />
<br />
Edit /etc/resolv.conf:<br />
nameserver 192.168.0.1<br />
This will be your host-computer DNS server.<br />
<br />
On the host-computer type(as root , use sudo -i on ubuntu):<br />
<br />
<pre><br />
echo 1 >> /proc/sys/net/ipv4/ip_forward<br />
echo 1 >> /proc/sys/net/ipv4/ip_dynaddr<br />
<br />
modprobe ip_tables<br />
modprobe iptable_nat<br />
modprobe ipt_MASQUERADE<br />
<br />
iptables -t filter -F<br />
iptables -t nat -F<br />
<br />
iptables -t filter -P INPUT ACCEPT<br />
iptables -t filter -P FORWARD ACCEPT<br />
iptables -t filter -P OUTPUT ACCEPT<br />
iptables -t nat -P PREROUTING ACCEPT<br />
iptables -t nat -P POSTROUTING ACCEPT<br />
<br />
iptables -t nat -A POSTROUTING -o eth0 -s 192.168.68.0/24 -j MASQUERADE<br />
</pre><br />
<br />
(Where eth0 is your network interface connected to the router)<br />
<br />
Thats it - now you can enjoy internet in qemu.<br />
<br />
== Etablir une connexion USB ==<br />
<br />
It is possible (although not very straight forward, probably about the complexity of tun-tap networking) to connect the virtual, emulated Neo1973 to the Linux PC on which the emulator is running, and work with it as if a real Neo1973 was plugged into the computer's USB port, but no twiddling with cables is needed. If you're testing your applications on the Neo, it may be worth setting up this kind of connection because it lets you enable normal [[USB_Networking|networking between the PC and the phone and ssh into it]] (which is much more comfortable than typing commands into the Openmoko's terminal emulator via on-screen keyboard). Here's what you will need in order to get this working:<br />
<br />
A Linux host with a 2.6 series kernel. The following drivers compiled-in or in modules: dummy_hcd, gadgetfs, usbnet, cdc_ether. [[Building Gadget USB Module|A detailed guide to building the necessary modules is available (primarily Ubuntu focused).]] Generic instructions follow.<br />
<br />
Note that you need root access to perform most actions described here. Here's how to enable the drivers in menuconfig.<br />
<br />
Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''Support for USB Gadgets'''<br />
<br />
Find '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''USB Peripheral Controller''' and set it to '''Dummy HCD (DEVELOPMENT)'''<br />
<br />
Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''Gadget Filesystem (EXPERIMENTAL)''' (this one is good to have as a module)<br />
<br />
Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Network Adapters''' -> '''Multi-purpose USB Networking Framework'''<br />
<br />
(in 2.6.25 (from ???) '''Device Drivers''' -> '''Network device support''' -> '''USB Network Adapters''' -> '''Multi-purpose USB Networking Framework''')<br />
<br />
Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Network Adapters''' -> '''Multi-purpose USB Networking Framework''' -> '''CDC Ethernet support (smart devices such as cable modems)'''<br />
<br />
(in 2.6.25 (from ???) '''Device Drivers''' -> '''Network device support''' -> '''USB Network Adapters''' -> '''Multi-purpose USB Networking Framework''' -> '''CDC Ethernet support (smart devices such as cable modems)''')<br />
<br />
These last two drivers are the same [[Getting Started with your Neo1973#By using Ethernet emulation over a USB cable|drivers that you need to work with a real Neo over USB network]]. After you've built the drivers, make sure that the copy of kernel headers in /usr/include/linux is up to date. In particular the file /usr/include/linux/usb_gadgetfs.h needs to be present and if your distribution came with headers older than 2.6.18 or so, then you need tell the package manager to update them, or you can do that manually with<br />
<pre> # cp -a /usr/src/linux/include/linux/* /usr/include/linux/</pre><br />
(assuming that your kernel sources are in /usr/src/linux). It is important that this is done before building qemu because the build system checks if these headers are functional and in case they aren't found it will disable the USB Slave functionality. Run "grep CONFIG_GADGETFS config-host.h" in qemu build directory to make sure that the detection succeeded. If it didn't, correct your linux headers and reconfigure qemu.<br />
<br />
After building qemu and before running it, make sure that the modules are loaded into the kernel. I found it useful to load gadgetfs with the following command:<br />
<pre> # modprobe gadgetfs default_uid=1000 # assuming my User ID is 1000</pre><br />
and added the following line to my /etc/fstab:<br />
<pre>gadget /dev/gadget gadgetfs noauto,user,group 0 0</pre><br />
Make sure that the mountpoint /dev/gadget exists:<br />
<pre> # mkdir -p /dev/gadget</pre><br />
After that the rest of the procedure can be performed from your regular user account. Mounting gadgetfs is done with:<br />
<pre> $ mount /dev/gadget</pre><br />
The "default_uid" parameter changes the ownership on all files under /dev/gadget to your own and since the files there are created and destroyed dynamically, there's no easy way to have that performed by ''udev''. Now running qemu as you usually do but appending "-usb -usbgadget" (in the current version of the [[MokoMakefile]] this is not included) should enable the USB Slave functionality. The qemu monitor commands "info usbslave" and "usb_add gadget" will be useful. The former instruction asks the OS running under the emulator (Openmoko) to describe its slave features (that's what ''lsusb'' does after a Neo1973 is connected to a PC). You can see the available USB configurations in this command's output. Since gadgetfs allows only one configuration, we will need to choose the desired configuration - most device have only one such configuration, in which case you can use just "usb_add gadget" to connect to host; CDC ethernet devices however usually include a second configuration for RNDIS networking (i.e. Ms Windows compatibility) and so does Openmoko when using the g_ether driver. Hence, to get this right, wait for Openmoko to fully boot up and execute the following in QEMU monitor:<br />
<pre><br />
QEMU 0.9.0 monitor - type 'help' for more information<br />
(qemu) info usbslave <br />
USB2.2 device 1457:5122:<br />
Manufacturer: Linux 2.6.20.7-moko8/s3c2410_udc<br />
Product: RNDIS/Ethernet Gadget<br />
Configuration 0: RNDIS<br />
Configuration 1: CDC Ethernet<br />
(qemu) <br />
(qemu) usb_add gadget:1<br />
</pre><br />
If qemu gives "couldn't add device gadget:1", double-check that it was built against gadgetfs - the file config-host.h must contain the line "#define CONFIG_GADGETFS 1".<br />
<br />
The "1" in "usb_add gadget:N" is the number of the USB configuration that we want to use. If everything went correctly - you can check that in dmesg - you should now have a new network interface called ''usb0'' on the PC, through which you can talk to the Openmoko running in QEMU:<br />
<pre><br />
$ dmesg | tail<br />
<6>gadgetfs: bound to dummy_udc driver<br />
<7>hub 3-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101<br />
<6>usb 3-1: new high speed USB device using dummy_hcd and address 3<br />
<6>gadgetfs: connected<br />
<7>usb 3-1: default language 0x0409<br />
<7>usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0<br />
<6>usb 3-1: Product: RNDIS/Ethernet Gadget<br />
<6>usb 3-1: Manufacturer: Linux 2.6.20.7-moko8/s3c2410_udc<br />
<6>usb 3-1: configuration #1 chosen from 1 choice<br />
<7>usb 3-1: adding 3-1:1.0 (config #1, interface 0)<br />
<7>usb 3-1:1.0: uevent<br />
<7>cdc_ether 3-1:1.0: usb_probe_interface - got id<br />
<7>cdc_ether 3-1:1.0: status ep3in, 16 bytes period 14<br />
<7>usb 3-1: adding 3-1:1.1 (config #1, interface 1)<br />
<7>usb 3-1:1.1: uevent<br />
$ su -<br />
Password:<br />
# tail /var/log/everything/current<br />
May 8 19:25:32 [kernel] gadgetfs: connected<br />
May 8 19:25:32 [kernel] gadgetfs: disconnected<br />
May 8 19:25:32 [kernel] gadgetfs: configuration #1<br />
May 8 19:25:32 [kernel] usb0: register 'cdc_ether' at usb-dummy_hcd-1, CDC Ethernet Device, 52:e7:eb:76:0a:d0<br />
# lsusb -vvv<br />
Bus 003 Device 003: ID 1457:5122 <br />
Device Descriptor:<br />
bLength 18<br />
bDescriptorType 1<br />
bcdUSB 2.00<br />
bDeviceClass 2 Communications<br />
bDeviceSubClass 0 <br />
bDeviceProtocol 0 <br />
bMaxPacketSize0 64<br />
idVendor 0x1457 <br />
idProduct 0x5122 <br />
bcdDevice 2.12<br />
iManufacturer 1 Linux 2.6.20.7-moko8/s3c2410_udc<br />
iProduct 2 RNDIS/Ethernet Gadget<br />
iSerial 0 <br />
bNumConfigurations 1<br />
Configuration Descriptor:<br />
bLength 9<br />
bDescriptorType 2<br />
wTotalLength 80<br />
bNumInterfaces 2<br />
bConfigurationValue 1<br />
iConfiguration 7 CDC Ethernet<br />
bmAttributes 0xc0<br />
Self Powered<br />
MaxPower 0mA<br />
Interface Descriptor:<br />
bLength 9<br />
bDescriptorType 4<br />
bInterfaceNumber 0<br />
bAlternateSetting 0<br />
bNumEndpoints 1<br />
bInterfaceClass 2 Communications<br />
bInterfaceSubClass 6 Ethernet Networking<br />
bInterfaceProtocol 0 <br />
iInterface 5 CDC Communications Control<br />
CDC Header:<br />
bcdCDC 1.10<br />
CDC Union:<br />
bMasterInterface 0<br />
bSlaveInterface 1 <br />
CDC Ethernet:<br />
iMacAddress 3 52E7EB760AD0<br />
bmEthernetStatistics 0x00000000<br />
wMaxSegmentSize 1514<br />
wNumberMCFilters 0x0000<br />
bNumberPowerFilters 0<br />
Endpoint Descriptor:<br />
bLength 7<br />
bDescriptorType 5<br />
bEndpointAddress 0x83 EP 3 IN<br />
bmAttributes 3<br />
Transfer Type Interrupt<br />
Synch Type None<br />
Usage Type Data<br />
wMaxPacketSize 0x0010 1x 16 bytes<br />
bInterval 14<br />
Interface Descriptor:<br />
bLength 9<br />
bDescriptorType 4<br />
bInterfaceNumber 1<br />
bAlternateSetting 0<br />
bNumEndpoints 0<br />
bInterfaceClass 10 Data<br />
bInterfaceSubClass 0 Unused<br />
bInterfaceProtocol 0 <br />
iInterface 0 <br />
Interface Descriptor:<br />
bLength 9<br />
bDescriptorType 4<br />
bInterfaceNumber 1<br />
bAlternateSetting 1<br />
bNumEndpoints 2<br />
bInterfaceClass 10 Data<br />
bInterfaceSubClass 0 Unused<br />
bInterfaceProtocol 0 <br />
iInterface 4 Ethernet Data<br />
Endpoint Descriptor:<br />
bLength 7<br />
bDescriptorType 5<br />
bEndpointAddress 0x81 EP 1 IN<br />
bmAttributes 2<br />
Transfer Type Bulk<br />
Synch Type None<br />
Usage Type Data<br />
wMaxPacketSize 0x0040 1x 64 bytes<br />
bInterval 0<br />
Endpoint Descriptor:<br />
bLength 7<br />
bDescriptorType 5<br />
bEndpointAddress 0x02 EP 2 OUT<br />
bmAttributes 2<br />
Transfer Type Bulk<br />
Synch Type None<br />
Usage Type Data<br />
wMaxPacketSize 0x0040 1x 64 bytes<br />
bInterval 0<br />
Device Qualifier (for other device speed):<br />
bLength 10<br />
bDescriptorType 6<br />
bcdUSB 2.00<br />
bDeviceClass 2 Communications<br />
bDeviceSubClass 0 <br />
bDeviceProtocol 0 <br />
bMaxPacketSize0 64<br />
bNumConfigurations 1<br />
<br />
# ifconfig usb0 inet 192.168.0.200 netmask 255.255.255.0<br />
# exit<br />
$ ssh root@192.168.0.202<br />
The authenticity of host '192.168.0.202 (192.168.0.202)' can't be established.<br />
RSA key fingerprint is de:21:87:93:52:1c:6b:c7:69:29:6c:af:66:50:02:02.<br />
Are you sure you want to continue connecting (yes/no)? yes<br />
Warning: Permanently added '192.168.0.202' (RSA) to the list of known hosts.<br />
root@192.168.0.202's password: <br />
root@fic-gta01:~$ uname -a<br />
Linux fic-gta01 2.6.20.7-moko8 #1 PREEMPT Wed Apr 25 11:13:52 UTC 2007 armv4tl unknown<br />
</pre><br />
<br />
== Connexion par le port série/Communication avec le u-boot ==<br />
If you add the option ''-serial telnet:localhost:1200,server'' to QEMU will create a telnet server on port 1200 that you can connect to as the serial port.<br><br />
This will allow you to experiment with u-boot configuration without risking to brick the real device.<br><br />
<br><br />
Please note that QEMU will wait for you to connect to the telnet server at port 1200 before starting the emulation.<br><br />
(use the command ''telnet localhost 1200'' to establish the connection)<br />
<br />
== Voir aussi ==<br />
*[[Building Gadget USB Module]] - Helpful guide<br />
*[[Xephyr]] - Openmoko on i386<br />
*[[Xoo]] - Openmoko on i386<br />
<br />
{{Languages|Openmoko_under_QEMU}}<br />
<br />
[[Category:Emulation]]</div>Youshehttp://openmoko.org/wiki/TranslationTranslation2008-09-13T17:21:40Z<p>Youshe: /* French */</p>
<hr />
<div>{{todo|{{PAGENAME}}}}<br />
<br />
Let us spread the popularity of Openmoko by localization of the software and translation of documentation and wiki.<br />
<br />
Just as an overview who is able and willing to translate parts into other languages,<br />
please join and add your Language and name. The source for the translation will<br />
be English. If you have good English skills then you could contribute by correcting<br />
the sources :)<br />
<br />
A good point to start would be to continuous translating of <br />
http://en.wikipedia.org/wiki/Openmoko into more languages on the other language sites of wikipedia.<br />
<br />
"...it is easy to join and spend some minutes for translating,<br />
and when someone finds some mistakes in any languages don't<br />
blame the translator - just be productive and fix it yourself!" -[[User:RobertMichel|Robert Michel]]<br />
<br />
Please take a look at [[Translation HOWTO]] and improve it if possible.<br />
<br />
Languages already offered on our community mailinglist, please add your name yourself and join community mailinglist (until we'll have a proper mailinglist) to discuss about translations:<br />
<br />
== Afrikaans ==<br />
<br />
== Amharic ==<br />
* [[User:ethiopia|Ethiopia Alemayehu]]<br />
<br />
== Armenian ==<br />
* [[User:surenk|Suren Karapetyan]]<br />
<br />
== Arabic عربي == <br />
* Hossam Mahmoud حسام محمود<br />
* [[User:ترجمان05|ترجمان05]]<br />
* [[User:Lixy|Lixy]] 17:54, 21 July 2007 (CEST)<br />
* [[User:Waraqa|Waraqa]]<br />
<br />
== Bulgarian == <br />
* [[User:Mr700|Doncho Nicolaev Gunchev]]<br />
<br />
== Basque ==<br />
<br />
* [[User:garrop|Ugartemendia]]<br />
<br />
== Catalan ==<br />
<br />
* [[User:montxovs|Montxo Vicente i Sempere]]<br />
<br />
* [[User:Mandarino|Mandarino]]<br />
<br />
* [[User:RafaelCarreras|Rafael Carreras]]<br />
<br />
* [[User:JaumeI|JaumeI]]<br />
<br />
== Chinese (Simplified)== <br />
* [[User:JarodWang|JarodWang]]<br />
* [[User:Liuxf|Liuxf]]<br />
* [[User:sunlt|sunlt]]<br />
<br />
== Chinese (Traditional)==<br />
* [[User:coolcat|Brenda Wang]]<br />
<br />
== Czech ==<br />
* [[User:Mikesh|Michal Heczko]]<br />
* [[User:Vatoz|Vaclav Cerny]]<br />
* [[User:Fox|Pavel Kovář]] (wiki)<br />
<br />
== Danish == <br />
* [[User:EsbenDamgaard|Esben Damgaard]]<br />
* [[User:UlrikRasmussen|Ulrik Rasmussen]]<br />
* [[User:miki|Mikkel Kirkgaard Nielsen]]<br />
<br />
== Dutch == <br />
* [[User:MarcVerwerft|Marc Verwerft]]<br />
* [[User:Madjo|Marcel De Jong]]<br />
* [[User:LuitvD|Luit van Drongelen]]<br />
* [[User:reinouts|Reinout van Schouwen]]<br />
* [[User:Steamrunner|Koen De Voegt]]<br />
<br />
([[User:Madjo|Marcel]] 18/04) Misschien is het handig om alvast te beginnen met vertalen van de Wiki? Of hebben jullie andere ideeen? Ik heb al een start gemaakt van de voorpagina van de wiki, maar ben nog niet veel verder gekomen<br />
([[User:reinouts|Reinout]] 21/04) Valt er verder nog niks te vertalen? De wiki is niet echt boeiend.<br />
<br />
== Esperanto ==<br />
* [[User:Antono|Antono Vasiljev]]<br />
* [[User:Alekcxjo|Alekĉjo Rajmondo]]<br />
<br />
== Estonian ==<br />
* [[User:Hadara|Sven Petai]]<br />
* [[User:Myoldryn|Jaan Nigul]]<br />
* [[User:Yogiz|Yogiz]]<br />
<br />
== Finnish == <br />
<br />
See also [[Openmoko Local Groups: Finland]].<br />
<br />
Notes to Finnish translators: please use the dictionary at [http://lokalisointi.org/ lokalisointi.org], avoid anglisms, avoid capital letters where unnecessary etc., kiitos :) Also, send new, big translations to [http://lokalisointi.org/mailman/listinfo/laatu laatu] mailing list for review. Until openmoko specific lists, you may join [http://lokalisointi.org/mailman/listinfo/keskustelu keskustelu] list too (it can be used despite the fact it's been silent).<br />
<br />
* [[User:Jani-Matti_Hätinen|Jani-Matti Hätinen]]<br />
* [[User:TimoJyrinki|Timo Jyrinki]]<br />
* [[User:Eyec|Samuli Perttula]]<br />
* [[User:TuomoSipola|Tuomo Sipola]]<br />
<br />
== French ==<br />
* [[User:SebastienJolicoeur|Sebastien Jolicoeur]]<br />
* [[User:MarcSert|Marc Sert]]<br />
* [[User:FoucaultdeBonneval|Foucault deBonneval]]<br />
* [[User:Sufflope|Jean-Sébastien Bour]]<br />
* [[User:Ymahe|Yves Mahé]]<br />
* [[User:opampca|Richard Lussier, Canada]]<br />
* [[User:Kheldar|Guillaume Maiano]]<br />
* [[User:Thomas01|Thomas Leclere]]<br />
* [[User:fredlala|Frédéric Lasnier]]<br />
* [[User:alekcxjo|Alexandre Raymond]]<br />
* [[User:VdeGrandpré|Vincent de Grandpré, Montréal, Québec]]<br />
* [[User:youshe|Frédéric Bouquet, Grenoble, France]]<br />
<br />
== Galician ==<br />
* [[User:Fjrial|Frco. Javier Rial]]<br><br />
[http://www.mancomun.org Mancomun]<br><br />
Para poñerse en contacto enviar un correo-e a rolda http://listas.mancomun.org/mailman/listinfo/g11n<br />
<br />
== German ==<br />
* [[User:RobertMichel|Robert Michel]]<br />
* [[User:FabianOff|Fabian Off]]<br />
* [[User:Denis std|Denis]]<br />
* [[User:ktd85|Thomas Drewermann]]<br />
* Lars C.<br />
* [[User:AndreasHochsteger|Andreas Hochsteger]]<br />
* [[User:Christophloew|Christoph Löw]]<br />
* [[User:dFence|Daniel Zauner]]<br />
* [[User:Imitation|Thomas Sanladerer]]<br />
* [[User:Peter Santo|Peter Santo]]<br />
* [[User:Bartholomaus|Marco K.]]<br />
<br />
== Greek ==<br />
* [[User:Chronix|Polychronis Papadakis]]<br />
<br />
== Hebrew - עברית ==<br />
* [[User:YaronSh|Yaron Shahrabani]]<br />
* [[User:OlegSverdlov|Oleg Sverdlov]]<br />
* [[User:Any_Key|Any_Key]]<br />
* [[User:Koala|Koala]]<br />
<br />
== Hungarian ==<br />
* [[User:ZeD|Zoltán Balogh]]<br />
<br />
== Indonesian ==<br />
* [[User:Hcblue|Hcblue]]<br />
<br />
== Italian ==<br />
* per il momento useremo [http://www.openmokoboard.com/index.php?getforum=10 questo forum] per organizzarci. iscrivetevi e partecipate.<br />
* [[User:SergioTota|Sergio Tota]]<br />
* [[User:Franco|Franco Rimoldi]]<br />
* [[User:Filippo|Filippo]]<br />
* [[User:Massi|Massimiliano]]<br />
* [[User:Markk0|Marco Cattaneo]]<br />
* [[User:Cga|Callea Gaetano Andrea]]<br />
* [[User:Herod2k|Alessandro]]<br />
* [[User:shainer|Lisa Vitolo]]<br />
* [[User:tia1982|Mattia]]<br />
* [[User:azanutta|abe]]<br />
* [[User:Gualti|Gualtiero]]<br />
* [[User:Milo|Milo Casagrande]]<br />
* [[User:White|Marco Celeri]]<br />
* [[User:Aegis|Maurizio Scorianz]]<br />
<br />
== Japanese ==<br />
*[[User:WilliamLai|William Lai]]<br />
*[[Momoko Matsuzaki]]<br />
<br />
== Norwegian ==<br />
*[[User:Vegar|Vegar Storvann]]<br />
*[[User:Denniz|Denniz Fjerdingby]]<br />
*[[User:StianEllingsen|Stian Ellingsen]]<br />
<br />
== Polish ==<br />
* [[User:KrzysztofKajkowski|Krzysztof Kajkowski]]<br />
* Tomasz Zieliński<br />
* [[User:MaciejLigenza|Maciej Ligenza]]<br />
* [[User:PiotrDuda|Piotr Duda]]<br />
* [[User:Zbraniecki|Zbigniew Braniecki]]<br />
<br />
== Portuguese ==<br />
*[[User:Skull Death|James Côrtes]]<br />
* Sergio Bessa<br />
* Mario Costa<br />
*[[User:kuyky|Tiago Saraiva]]<br />
<br />
== Punjabi ==<br />
* [[User:aalam|A S Alam]]<br />
<br />
== Romanian ==<br />
<br />
* [[User:alexxed|Alexandru Szasz]]<br />
* [[User:sin|Lucian]]<br />
* [[User:Adrians|Adrians]]<br />
<br />
== Russian ==<br />
* [[User:OlegSverdlov|Oleg Sverdlov]]<br />
* [[User:DenisBY|Denis Kot]]<br />
* [[User:MikhailGusarov|Mikhail Gusarov]]<br />
* [[User:x-demon|Alexander Sokolow]]<br />
* [[User:Any_Key|Any_Key]]<br />
* [[User:Dmitri|Dmitri]]<br />
* [[User:Buffet|Denis Kaledin]]<br />
* [[User:Nes|Mike Drapolyuk]]<br />
* [[User:vase|Vasiliy Tolstov]]<br />
* [[User:Shadowjack|Shadowjack]]<br />
* [[User:Cray|Denis Parchenko]]<br />
* [[User:Vlad|Vladimir Orlov]]<br />
* [[User:xnike|Nikolay Khramchenkov]]<br />
* [[User:kainspb|Nikolay Kasatkin]]<br />
<br />
Можем начинать переводить wiki :)<br />
К любой странице добавляете /ru и переводите. В конце оригинальной страницы и переведенной добавляете ссылку на шаблон <br />
<nowiki>{{Languages|Имя_страницы_оригинала}}</nowiki><br />
<br />
== Slovak == <br />
* [[User:Cezz|Cezz]]<br />
* [[User:PipBoy2000|PipBoy2000]]<br />
* [[User:m4rtin.m|m4rtin.m]]<br />
<br />
== Spanish ==<br />
* [[User:RosangelaCaninoKoning|Rosangela CaninoKoning]]<br />
* [[User:kresp0|Santiago Crespo (kresp0)]]<br />
* [[User:José_Suárez|José Suárez]]<br />
* [[User:Rafa_Couto|Rafa Couto (caligari)]]<br />
* [[User:NeoMorfeo|Guillermo Santos (NeoMorfeo)]]<br />
* [[User:Mandarino|Mandarino]]<br />
* [[User:pptudela|Pepe Tudela]]<br />
* [[User:avathar|Fernando González (Avathar)]]<br />
* [[User:Rbruzz|Rbruzz]]<br />
* [[User:Saaib|Urivan Flores Saaib (Saaib)]]<br />
* [[User:mutrox|David Samblas Martinez (mutrox)]]<br />
<br />
== Swedish ==<br />
* [[User:yeager|Daniel Nylander]]<br />
* [[User:possan|Per-Olov Jernberg]]<br />
* [[User:C.M|Claes Mogren]]<br />
<br />
== Turkish ==<br />
* [[User:EnginErenturk|Engin Erenturk]]<br />
* [[User:Supernova|İsmail AŞCI]]<br />
<br />
== Welsh ==<br />
* [[User:Rhoslyn_Prys|Rhoslyn Prys]]<br />
<br />
<br />
And feel free to join and add an new language to this list above.<br />
<br />
{{Languages|Translation}}</div>Youshehttp://openmoko.org/wiki/Om_2008.8/frOm 2008.8/fr2008-08-13T10:08:16Z<p>Youshe: Traduction en Français</p>
<hr />
<div>{{Languages|Om 2008.8}}<br />
{{Om 2008.8}}<br />
<br />
{{Distributions|Om 2008.8}}<br />
<br />
=Introduction=<br />
<br />
'''Om 2008.8''' est le successeur de [[Om 2007.2]] et ajoute '''ASU''' comme nom de code. Cette version a été [http://list.openmoko.org/pipermail/community/2008-August/025619.html lancée] le '''8 août 2008'''. Om 2008.8 utilise le démarreur EFL, diverses applications utilisateurs personnalisées et [[QtopiaOnX11|Qtopia sur X11]] pour la téléphonie. Il s'agit du premier pas de GTK+ sur X11 pour utiliser une multitude de suites d'outils en collaboration. '''Om 2008.8''' supporte maintenant des applications [http/enlightenment.org EFL], [http://trolltech.com/products/qtopia Qtopia] et [http://www.gtk.org GTK+].<br />
<br />
''Pour voir comment tout a débuté, rendez-vous à la''' [[Om2008.8 Feature Plan|liste caractéristiques de Om 2008.8]].<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; width:100%;floating="center"; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om2008 uboot.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om2008 home.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Installer4.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om2008 installer1.png|200px|center]]<br />
|-<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Main.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Edit1.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om locations4.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:List.png|200px|center]]<br />
|}<br />
<br />
== Quoi de neuf ==<br />
'''Om 2008.8''' a été créé pour être vide, afin d'offrir une vitrine pour vos idées.<br />
<br />
Pensez à vos créations comme des galeries. Nous en construisons l'environnement. Chacune différente de la suivante. Vous pourrez prendre la liberté d'imaginer la votre parce que nous voulous que vous ajoutiez votre touche. Au choix : vous pouvez utiliser, créer ou les deux.<br />
<br />
Peu importe le chemin, vous créez à votre image. C'est à votre sujet.<br />
<br />
=== Personnalisation ===<br />
<br />
'''Om 2008.8''' vous permet de personnaliser votre Neo dans beaucoup d'aspects.<br />
<br />
* '''Utilisez l'[[Om2008.8_Installer|installeur]]''' pour trouver les applications et les modifications pour votre your Neo.<br />
* '''Ajustez les thèmes''' en personnalisant vos propres fichiers [[Edje]].<br />
* Les '''Codes source''' sont disponibles au public, permettant la personnalisation à toutes les couches logicielles, même le plus bas niveau.<br />
<br />
=== Partage ===<br />
* Partagez vos ([[Om2008.8_Locations|Locations]]) :<br />
Vous pouvez utiliser '''Locations''' pour sauvegarder vos endroits préférés et éventuellement les envoyer à vos amis par SMS. N'est-ce pas cool ?!<br />
* Partagez vos applications (cf. [[Om2008.8_Installer|Installeur]])<br />
:Partagez vos idées à travers le monde en ajoutant des packages au [http://wiki.openmoko.org/wiki/CommunityRepository répository communautaire]. Il s'agit d'une grosse base de donnée pour tous les projets openmoko et peut être accessible aisément à tout utilisateur par l'intermédiaire de l'[[Om2008.8 Installer|installeur]].<br />
<br />
=== Guide Om 2008.8 ===<br />
Un guide pour connaître Om2008.8 : [[Om 2008.8 Guide]]<br />
A guide for getting to know Om 2008.8 : [[Om 2008.8 Guide|Guide Om 2008.8]]<br />
<br />
= Téléchargement =<br />
<br />
== Images Flash Om 2008.8 ==<br />
<br />
'''Téléchargement d'images Om 2008.8'''<br />
<br />
Ces images doivent être flashées dans la mémoire NAND du FreeRunner.<br />
* [http://downloads.openmoko.org/releases/Om2008.8/Om2008.8.rootfs.jffs2 Om2008.8.rootfs.jffs2] (image du système de fichier racine)<br />
* [http://downloads.openmoko.org/releases/Om2008.8/Om2008.8.uImage.bin Om2008.8.uimage.bin] (noyau)<br />
<br />
'''Installation'''<br />
<br />
* Pour les instructions sur comment flasher l'appareil, rendez-vous à : [[Flashing the Neo FreeRunner|Flasher le Neo FreeRunner]].<br />
<br />
== Alternative : exécution depuis une carte microSD ==<br />
<br />
Vous pouvez installer cette distribution sur une carte microSD afin de pouvoir [[Boot from sd card|booter depuis une carte microSD]]. Les fichiers .tar sont disponibles [http://downloads.openmoko.org/releases/Om2008.8/ ici]. Cela permet de garder une autre distribution installée sur la mémoire NAND (pour tester 2008.8 tout en gardant 2007.2).<br />
<br />
<br />
= Problèmes connus =<br />
'''GSM'''<br />
<br />
* [http://docs.openmoko.org/trac/ticket/1662 Après x heures, le GSM ne fonctionne plus correctement]<br />
* [https://docs.openmoko.org/trac/ticket/1765 Pas de dialogue Pin, donc GSM inutilisable]<br />
<br />
'''WiFi'''<br />
<br />
* [http://docs.openmoko.org/trac/ticket/1625 Le WiFi ne se connecte qu'une fois]<br />
<br />
'''Qualité Audio'''<br />
<br />
* [http://docs.openmoko.org/trac/ticket/1721 le Dialer QT des fois muet pendant l'établissement d'un appel]<br />
* [http://docs.openmoko.org/trac/ticket/1640 Improve overall audio]<br />
<br />
'''Logiciels systèmes'''<br />
<br />
* [http://docs.openmoko.org/trac/ticket/1736 L'écran de boot se met en veille et ne se réveille jamais s'il n'est pas touché pendant le démarrage]<br />
* [http://docs.openmoko.org/trac/ticket/1597 Après une longue veille, évènements au niveau des threads kernel]<br />
* [http://docs.openmoko.org/trac/ticket/1315 xglamo : performance diminuée après un moment]<br />
* [http://docs.openmoko.org/trac/ticket/1682 Le Neo s'arrête avant d'avoir lancé X]<br />
<br />
'''Réseau'''<br />
* Pas d'installations/mises à jour possibles ou des pings vers des noms de domaines en raison d'une défaillance DNS. Ce problème survient parce que le fichier /etc/resolv.conf est vide par défaut.Ajoutez cette ligne dans in /etc/network/interfaces:<br />
<br />
<br />
up echo nameserver 192.168.0.200 >/etc/resolv.conf<br />
Cette ligne est à ajouter avant la ligne 'gateway address' et avant 'bluetooth networking'. Après la modification, il convient de redémarrer l'appareil. Ensuite, allez compléter manuellement /etc/resolv.conf en utilisant les données de ce fichier sur votre machine locale ou l'adresse DNS.<br />
<br />
Cela devrait résoudre la majeure partie de vos soucis de réseau. Si vous avez besoin d'autres aides, référez vous au [[USB Networking|réseau par USB]]<br />
<br />
{{note| [http://en.wikipedia.org/wiki/Resolvconf resolv.conf] est installé et devrait normalement être utilisé}}<br />
<br />
* Le réseau par USB ne devrait pas fonctionner après le boot initial.<br />
<br />
'''Utilisabilité'''<br />
<br />
* Le dialogue Pin par défaut ne montre que les lettres. Vous devez glisser vos doigts de haut en bas sur le clavier pour changer les caractères en nombre/lettres/spécial.<br />
<br />
* L'installeur ne rend pas les droits administrateur, ce qui résulte en une impossibilité d'utiliser opkg. Solution : exécuter "killall packagekitd" (sur le freeRunner ou lorsque vous y êtes connectés en ssh).<br />
<br />
<br />
[[Category:Openmoko]]<br />
[[Category:Om 2008.8]]</div>Youshehttp://openmoko.org/wiki/Manual_DebianManual Debian2008-08-12T10:03:30Z<p>Youshe: languages</p>
<hr />
<div>{{Languages|Debian}}<br />
<br />
[[Image:Debian.png|thumb|480px|''Debian on neo1973'']]<br />
This page is to explain how to run Debian armel port on Openmoko devices. You can do this from scratch, or download a prebuilt file system.<br />
The former will take some time, perhaps 2 hours, depending on your internet connection<br />
<br />
= Prebuilt Filesystem =<br />
<br />
Download and extract to an ext2/ext3 formatted filesystem on your SD card:<br />
<br />
wget http://rabenfrost.net/debian/debian-armel-xfce.tar.bz2<br />
<br />
Note that the above is just a bit too big to fit on a 512MB SD card. A smaller image will soon be provided.<br />
<br />
Access via SSH is much the same as under other images using [[USB Networking]], with the user accounts below:<br />
<br />
* root password: openmoko<br />
* First user and password: openmoko<br />
<br />
Note: If you upgrade your your debian and your touchscreen doesn't work any more, you most likely have to adjust /etc/udev/rules.d/50-udev.rules by applying the settings described later in this document for /etc/udev/udev.rules<br />
<br />
== (Optional) Install Known Good Kernel ==<br />
<br />
This kernel was build by Marcel_M and has some important patches in it such as removed sd debug symbols and build-in ext3 support.<br />
<br />
wget http://rabenfrost.net/celtune/uImage-2.6.24+svnr4194-r4165-r3-neo1973.bin<br />
./dfu-util -d 0x1457:0x5119 -a kernel -R -D ./uImage-2.6.24+svnr4194-r4165-r3-neo1973.bin<br />
<br />
<br />
== (Optional) Recompiling Kernel to Add Drivers ==<br />
(Based on http://lists.openmoko.org/pipermail/support/2008-August/001240.html)<br />
<br />
Steps to build the kernel standalone with the "moredrivers" config (to get additional drivers, such as the usb tether drivers that were moved out as kernel modules, compiled directly into the kernel).<br />
<br />
~ - git clone git://git.openmoko.org/git/kernel.git linux-2.6<br />
~ - cd linux-2.6<br />
~ - git checkout origin/stable<br />
~ - edit ./build to point to your compiler path<br />
~ - cp defconfig-2.6.24 .config<br />
~ - ./build<br />
<br />
That gets you a uImage.bin you can DFU or copy into your SD Card filesystem.<br />
<br />
== Configure booting from SD/SDHC ==<br />
<br />
Do as proposed here: [[Booting_from_SD]]<br />
<br />
Note that these instructions are in need a rewrite.<br />
<br />
= Build your own armel filesystem =<br />
<br />
== (Option 1) debootstrap your rootfs on Debian or Ubuntu host ==<br />
<br />
debootstrap --verbose --arch armel --foreign sid ./armel-chroot http://ftp.de.debian.org/debian/<br />
<br />
== (option 2) download ready to use armel rootfs ==<br />
<br />
If you don't have debootstrap on your system you can download the results here:<br />
<br />
wget http://rabenfrost.net/debian/armel-chroot-first-stage.tar.gz<br />
<br />
== Prepare SD card ==<br />
<br />
ssh to your neo and format your sd card appropriately. I'm using an 8GB SDHC card here.<br />
<br />
:''NOTE: it might be a good idea not to use ext3. This is because ext3 is a heavily journalising file system and on the freerunner (sd card) might cause premature death of the card. It is recommened you use ext2 or another similar file system. One also will need a vfat or ext2 (only vfat worked for me with the stock u-boot for the freerunner. On which to place the kernel to boot off. See the [[Booting_from_SD]] If you have not done so already.''<br />
<br />
fdisk /dev/mmcblk0<br />
We will now create a 8 mb partition for our kernel and another one for the rootfs which will take up all the <br />
remaining space.<br />
Command (m for help): d<br />
Selected partition 1<br />
Command (m for help): n<br />
Command action<br />
e extended<br />
p primary partition (1-4)<br />
p<br />
Partition number (1-4): 1<br />
First cylinder (1-983, default 1):<br />
Using default value 1<br />
Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M<br />
Command (m for help): n<br />
Command action<br />
e extended<br />
p primary partition (1-4)<br />
p<br />
Partition number (1-4): 2<br />
First cylinder (18-983, default 18):<br />
Using default value 18<br />
Last cylinder or +size or +sizeM or +sizeK (18-983, default 983):<br />
Using default value 983<br />
Command (m for help): w<br />
The partition table has been altered!<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
<br />
mkfs.vfat /dev/mmcblk0p1<br />
<br />
mkfs.ext3 /dev/mmcblk0p2<br />
mount /dev/mmcblk0p2 /media/card<br />
<br />
copy the armel chroot to your device by tar'ing it to circumvent symbolic link cycles (https://bugzilla.mindrot.org/show_bug.cgi?id=1059 <= WONTFIX)<br />
<br />
tar -C ./armel-chroot/ -c . | ssh root@192.168.0.202 tar -C /media/card -xv<br />
or if you downloaded the archive<br />
<br />
cat armel-chroot-first-stage.tar.gz | ssh root@192.168.0.202 tar -C /media/card -xzvf -<br />
<br />
== Complete debootstrap Process ==<br />
<br />
ssh to your device and execute the following commands (just copypaste everything below)<br />
<br />
echo "nameserver 192.168.0.200" > /media/card/etc/resolv.conf<br />
echo "fic-gta01" > /media/card/etc/hostname<br />
echo "127.0.0.1 localhost.localdomain localhost fic-gta01" > /media/card/etc/hosts<br />
echo -e "auto lo\n\<br />
iface lo inet loopback\n\<br />
auto usb0\n\<br />
iface usb0 inet static\n\<br />
address 192.168.0.202\n\<br />
netmask 255.255.255.0\n\<br />
network 192.168.0.0\n\<br />
gateway 192.168.0.200\n\<br />
up echo nameserver 192.168.0.200 >/etc/resolv.conf" > /media/card/etc/network/interfaces<br />
echo -e "rootfs / ext3 defaults,errors=remount-ro,noatime 0 1\n\<br />
proc /proc proc defaults 0 0\n\<br />
tmpfs /etc/network/run tmpfs defaults,noatime 0 0\n\<br />
tmpfs /tmp tmpfs defaults,noatime 0 0\n\<br />
tmpfs /var/lock tmpfs defaults,noatime 0 0\n\<br />
tmpfs /var/run tmpfs defaults,noatime 0 0\n\<br />
tmpfs /var/tmp tmpfs defaults,noatime 0 0" > /media/card/etc/fstab<br />
now chroot into your armel rootfs and finish the install<br />
chroot /media/card<br />
/debootstrap/debootstrap --second-stage<br />
make sure your internal clock is set to the correct date because aptitude will complain if otherwise (does not work on the gta02 at the moment: "Cannot access the Hardware Clock via any known method.")<br />
hwclock --set --date="MM/DD/YY hh:mm:ss"<br />
install openssh so you can login remotely<br />
echo "deb http://ftp.de.debian.org/debian sid main" > /etc/apt/sources.list<br />
aptitude update<br />
aptitude upgrade<br />
aptitude install openssh-server<br />
install and configure locales<br />
aptitude install locales<br />
dpkg-reconfigure locales<br />
install udev to dynamically create /dev<br />
aptitude install udev<br />
set a root password<br />
passwd<br />
create a normal user<br />
adduser <yournamehere><br />
<br />
== Get X Running ==<br />
Now reboot and start Debian. Login with ssh and start configuring xorg:<br />
<br />
aptitude install xorg<br />
<br />
configure /etc/X11/xorg.conf so that it looks like this:<br />
<br />
Section "InputDevice"<br />
Identifier "Configured Mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
EndSection<br />
Section "Device"<br />
Identifier "Configured Video Device"<br />
Driver "fbdev"<br />
EndSection<br />
Section "Monitor"<br />
Identifier "Configured Monitor"<br />
EndSection<br />
Section "Screen"<br />
Identifier "Default Screen"<br />
Monitor "Configured Monitor"<br />
EndSection<br />
Section "ServerLayout"<br />
Identifier "Default Layout"<br />
Screen "Default Screen"<br />
InputDevice "Configured Mouse"<br />
EndSection<br />
Start X in the first vt:<br />
startx -- vt1<br />
<br />
== Get touchscreen working ==<br />
Install the tslib driver:<br />
<br />
aptitude install xserver-xorg-input-tslib<br />
<br />
and edit the InputDevice section in your xorg.conf<br />
<br />
Section "InputDevice"<br />
Identifier "Configured Mouse"<br />
Driver "tslib"<br />
Option "CorePointer"<br />
Option "TslibDevice" "/dev/input/event1"<br />
Option "Protocol" "Auto"<br />
EndSection<br />
calibrate your touchscreen<br />
for gta01:<br />
echo -67 36365 -2733100 -48253 -310 45219816 65536 > /etc/pointercal<br />
<br />
calibration for the gta02<br />
echo -67 38667 -4954632 -51172 121 46965312 65536 > /etc/pointercal<br />
<br />
<br />
Start X and enjoy!<br />
startx -- vt1<br />
<br />
== Install GDM and xfce4 ==<br />
<br />
aptitude install gdm xfce4 xvkbd<br />
<br />
Configure gdm so xkvbd will allow you to put in your username and password. simply add this to the end of /etc/gdm/Init/Default before exit 0 so that the three last lines look like this:<br />
<br />
fi<br />
sleep 20 && /usr/bin/xvkbd -xdm -compact -geometry 480x210+0+0 &<br />
exit 0<br />
<br />
Simply click on the focus button of xvkbd and then on the input box of GDM to input your user name and password there. On each boot gdm should start automatically now.<br />
<br />
If you like you can also download a correctly sized Debian wallpaper I generated from the SVG source for 480x640:<br />
<br />
wget <nowiki>http://rabenfrost.net/debian/debian-blueish-wallpaper-480x640.png</nowiki> -O /usr/share/images/desktop-base/desktop-background<br />
<br />
== Clean Up ==<br />
aptitude clean<br />
<br />
== Load Additional Kernel Modules ==<br />
<br />
These are for sound, bluetooth and USB. Use the modules archive that fits to your kernel.<br />
<br />
wget http://rabenfrost.net/celtune/modules-2.6.24+svnr4194-r4165-r3-neo1973.tgz<br />
tar -xf modules-2.6.24+svnr4194-r4165-r3-neo1973.tgz -C /<br />
depmod -a<br />
echo -e "hci_usb\n\<br />
hidp\n\<br />
ohci-hcd\n\<br />
rfcomm\n\<br />
snd-mixer-oss\n\<br />
snd-pcm-oss\n\<br />
snd-soc-neo1973-wm8753" > /etc/modules<br />
<br />
[[Image:Sonata.png|480px|''Sonata on neo1973'']]<br />
== Enable Sound ==<br />
<br />
Now we turn our Debian into a jukebox!<br />
<br />
aptitude install alsa-base<br />
wget http://rabenfrost.net/celtune/alsa_state_files-working.tar.gz<br />
tar -xf alsa_state_files-working.tar.gz -C /etc<br />
alsactl -f /etc/alsa_state_files-working/stereoout.state restore<br />
addgroup openmoko audio<br />
<br />
I currently use mpd+sonata - let me know if you know another nice lightweight gtk player. Unfortunately RhythmBox is way too much for the Neo to handle - the MP3 playing stops after 20secs.<br />
<br />
= Using a keyboard =<br />
[[Image:Debian+frogpad.jpg|480px|''Using irssi on [[Debian]] together with the frogpad to IRC on #neo1973-germany'']]<br />
nezza prepared a nice guide for this here: [[Frogpad]]<br />
<br />
= Chroot installation =<br />
<br />
If you just want to run random debian programs without completely booting to debian you can use the following minimal steps:<br />
<br />
on desktop:<br />
<br />
sudo debootstrap --arch armel --foreign sid sid<br />
sudo tar cjf sid.tar.bz2 sid<br />
nc -w3 -lp1234 < sid-arm.tar.bz2<br />
<br />
on neo:<br />
<br />
cd /media/card<br />
nc 192.168.0.200 1234 | tar -x -j -f -<br />
mount -t none -o bind /dev /media/card/sid/dev<br />
mount -t none -o bind /proc /media/card/sid/proc<br />
mount -t none -o bind /sys /media/card/sid/sys<br />
mount -t none -o bind /tmp /media/card/sid/tmp<br />
chroot /media/card/sid /deboostrap/deboostrap --second-stage<br />
cp /etc/resolv.conf /media/card/sid<br />
chroot /media/card/sid apt-get update<br />
chroot /media/card/sid apt-get install mplayer<br />
chroot /media/card/sid mplayer http://relay.slayradio.org:8000/<br />
<br />
<br />
=For X applications / xserver.=<br />
<br />
Just copy /usr/bin/Xglamo (./Xfbdev) to /usr/bin in debian.<br />
Then. add this to your .bashrc export TSLIB_TSDEVICE=/dev/input/event1<br />
<br />
Then as root go ln -s /usr/lib/libts-0.0.so.0 /usr/lib/libts-1.0.so.0<br />
Also, do the following: cd /usr/bin && mv X X.orig && ln -s Xfbdev X<br />
This should make X a symlink to Xfbdev.<br />
<br />
=Official Debian Port=<br />
<br />
An official Debian port based on the FSO image is being created. First information can be found at http://wiki.debian.org/pkg-fso. Early adaptors are welcome.<br />
<br />
[[Category:Distributions]]<br />
[[Category:Software (non openmoko)]]<br />
[[category:Technical]]</div>Youshehttp://openmoko.org/wiki/Distributions/frDistributions/fr2008-08-10T14:12:54Z<p>Youshe: Quelques corrections</p>
<hr />
<div>{{Languages|Distributions}}<br />
<br />
{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"<br />
|<font color=white>Distributions</font><br />
|-<br />
! style='background-color:#333333;color:#FFFFFF'|<br />
<div align=left><br />
* <font color='#BBBBBB'>Openmoko (officiel)</font><br />
** [[Om 2008.8]]<br />
** [[Om 2007.2]]<br />
** [[OpenmokoFramework|FSO]]<br />
* <font color='#BBBBBB'>Communauté</font><br />
** [[SHR]]<br />
* <font color='#BBBBBB'>Autres</font><br />
** [[Qtopia]]<br />
** [[Debian]]<br />
</div><br />
|-<br />
|}<noinclude>[[Category:Templates]]</noinclude><br />
<br />
Les différentes distributions d'Openmoko sont construites afin de tourner sur différents périphériques mobiles, avec comme priorité les téléphones d'Openmoko Inc, à savoir le [[Neo 1973]] et le [[Neo FreeRunner]].<br />
Ces distributions sont similaires à des distributions linux : des systèmes d'exploitation complets avec leurs applications utilisateurs.<br />
Vous pouvez installer n'importe laquelle de celles ci sur votre téléphone ou avoir un système de multiboot avec plusieurs distributions d'installées.<br />
<br />
Alors que les distributions d'Openmoko peuvent aussi tourner sur [[Supported devices|d'autres appareils mobiles]], d'autres distributions logicielles peuvent s'exécuter sur les téléphones d'Openmoko Inc. (voir plus loin).<br />
<br />
Pour les téléchargements, voir [[Latest Images|Dernières images]], pour les instructions d'installations voir [[Flashing the Neo FreeRunner]]<br />
<br />
== A propos des distributions ==<br />
<br />
Pour être précis techniquement, les distributions 2007.2, 2008.8, FSO et SHR ne sont pas réellement des distributions indépendantes, mais des distributions visant des objectifs différents. Chaqu'une d'elle a été construite à partir de différentes branches de la méta-distribution [[OpenEmbedded]].<br />
<br />
Par exemple, 2007.2 et 2008.8 sont ce qu'Ubuntu Gutsy est à Kubuntu Hardy. L'une devrait seulement utiliser des packages de la branche correspondante, sinon, des choses risquent de ne pas bien se passer, c'est comme l'utilisation des .deb de Hardy sur un système Gutsy.<br />
<br />
Par ailleurs, il est à noter qu'il n'existe à l'heure actuelle, pas de mise à jour supportée entre ces deux distributions. Ainsi, mettre à jour l'une d'elle en changeant la provenance des paquets résultera dans un système cassé et probablement impossible à démarrer. <br />
<br />
Enfin, utilisez toujours le [[dfu-util]] pour changer de distribution ou installez les en dual boot (via une carte SD ou NFS par exemple)<br />
<br />
== Révisions cibles dirigées par Openmoko Inc. ==<br />
<br />
=== Om 2007.2 (GTK) ===<br />
<br />
[[Om 2007.2]] a pour objectif les personnes voulant se familiariser avec l'initiative [http://www.gnome.org/mobile/ GNOME Mobile] et qui veulent écrire des applications qui peuvent s'exécuter sur une multitude de systèmes utilisant (au moins des parties) du GNOME Mobile. Cette distribution introduit Maemo, qui tourne sur les Tablettes Internet Nokia. La force de la couche GTK+ est une interface utilisateur et un environnement de programmation similaire à ce que l'on peut trouver sur un système linux de bureau tournant sous GNOME.<br />
Le framework GTK+ dispose des applications PIM basées sur le serveur d'évolution des données (Evolution Data Server) et utilise le serveur téléphonique gsmd. Bien que l'on puisse les utiliser, ces application sont encore bugguées et non finies.<br />
De plus, certaines personnes ont des problèmes avec la stabilité du serveur téléphonique.<br />
<br />
* [[Om 2007.2]]<br />
* Disponibilité: [http://buildhost.openmoko.org/daily/ hotes officiels] et [[MokoMakefile]] pour la compilation<br />
* Téléchargement: [http://buildhost.openmoko.org/daily/freerunner/ Les révisions sont nommées "openmoko-devel-image" ]<br />
* Diverses vidéos sur cette couche sont disponibles sur Youtube : [http://uk.youtube.com/user/freeyourphone user freeyourphone] et le [http://uk.youtube.com/watch?v=U05kZfURPig&NR=1 video review par BVB Tech]<br />
<br />
Il s'agit du système de base installé sur le Neo Freerunner lorsqu'il quitte l'usine de fabrication.<br />
Le développement conduit par Openmoko inc. sur la version 2007.2 a été stoppé et les ressources sont allouées maintenant en faveur de la version 2008.8 alors que la communauté est en train de fournir un effort pour sauver les applications téléphoniques de 2007.2 dans le but de les placer dans le futur intergiciel du FSO (cf. SHR).<br />
<br />
De tels patchs sont toujours les bienvenus, surtout s'ils aident le développement de SHR.<br />
<br />
=== Om 2008.8 (ASU, Mises à jour logicielles Avril/aout) ===<br />
<br />
Om 2008.8 a débuté afin d'intégrer la pile [http://trolltech.com/products/qtopia Qtopia] - au dessus de X11 - avec un nouvel ensemble d'applications graphiques basées sur les librairies fondatrices de Enlightenment. ASU est le nom interne et est connu comme Om 2008.8 depuis sa sortie le 8 aout 2008. Qtopia est un projet plus mature que la pile mobile GNOME et vous pouvez en attendre toutes les fonctionnalités standard de téléphonie, le tout dans un environnement stable. Cette couche utilise le serveur téléphonique de Qtopia.<br />
Cependant - contrairement au standard Qtopia - elle n'utilise pas directement le framebuffer, ce qui permet un partage fiable de l'écran entre les applications Qt et non Qt.<br />
<br />
* [[Om2008.8|Om 2008.8]]<br />
* Téléchargement : [http://downloads.openmoko.org/releases/Om2008.8/ Les images sont nommées "Om2008.8" ]<br />
<br />
=== FSO - freesmartphone.org ===<br />
<br />
FSO a vu le jour afin de palier aux manques des couches 2007.2 et 2008.8, à savoir pour créer un framework extensible qui fournit aux développeurs une infrastructure permettant de créer de solides applications basées sur la plateforme Openmoko.<br />
Le framework supporte plusieurs interfaces utilisateur concurrentes qui peuvent alors collaborer pour développer des services, fournissant ainsi un solide framework.<br />
<br />
Ici, l'objectif est basé sur des services de haut niveau qui peuvent être accédés par l'intermédiaire de n'importe quel langage ou interface qui supporte [http://dbus.freesmartphone.org/ dbus]. On rapporte que malgré sa simplicité, le serveur téléphonique de FSO est déjà plus fiable que tout le reste.<br />
<br />
Il ne s'agit en fait pas vraiment d'une future révision/cible, mais plus un contenant pour le développement de nouveau et futur intergiciels.<br />
<br />
Les applications installées de base sont dédiées à des outils de test pour le futur intergiciel et ne sont pas tout à fait terminées et non orientées vers l'utilisateur final (Même si elles en ont l'air de temps en temps).<br />
<br />
* [[FSO]]<br />
* [http://trac.freesmartphone.org:8000/trac-example Development tracker]<br />
* [http://downloads.openmoko.org/framework/milestone2/ Téléchargement de milestone 2]<br />
* [http://freesmartphone.org freesmartphone.org]<br />
<br />
<br />
== Révisions cibles pilotées par la communauté openmoko ==<br />
<br />
=== SHR - Stable Hybrid Release (Révision hybride stable) ===<br />
<br />
La révision hybride stable est une combinaison du middleware provenant de FSO, de certaines parties du logiciel GTK de 2007.1 (telephony-ui, pim) et de 2008.8 qui fournit toutes les fonctionnalités du logiciel 2007.2, mais avec la stabilité de FSO.<br />
<br />
* [[Stable Hybrid Release]]<br />
<br />
== Distributions Non-Openmoko ==<br />
<br />
Ces distributions ne sont pas basées sur des distributions Openmoko (et OE). Il s'agit d'alternatives que vous pouvez utiliser sur vos téléphones Openmoko.<br />
<br />
=== Qtopia ===<br />
<br />
La distribution Qtopia de [http://www.trolltech.com Trolltech] vise à fournir une image prête à l'utilisation pour les matériels Openmoko.<br />
<br />
* [[Qtopia]]<br />
* Téléchargement: [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Qtopia.net]<br />
<br />
=== Debian ===<br />
<br />
L'entière distribution Debian Linux sur un téléphone portable.<br />
<br />
* [[Debian]]<br />
<br />
== Fonctionnalités par distribution/révision cible ==<br />
<br />
=== Connectivité ===<br />
<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| Téléphonie || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || N/A || style="background:lightgreen;" | Oui || ??<br />
|-<br />
| SMS || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || N/A || style="background:lightgreen;" | Oui || ??<br />
|-<br />
| GPRS || Pas via l'UI || Pas via l'UI || Pas via l'UI || N/A || Non (3) || ??<br />
|-<br />
| WiFi || style="background:lightgreen;" | Oui || Pas via l'UI || style="background:lightgreen;" | Oui (*) || N/A || style="background:lightgreen;" | Oui ||style="background:lightgreen;" | Oui<br />
|-<br />
| VoIP || ?? || ?? || ?? || ?? || ?? || ??<br />
|-<br />
| Bluetooth || style="background:lightgreen;" | Oui || Non || style="background:lightgreen;" | Oui || N/A || style="background:lightgreen;" | Oui || ??<br />
|-<br />
| GPS || style="background:lightgreen;" | Oui (1) || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui (1) || N/A || Non || ??<br />
|-<br />
|}<br />
<br />
=== Interaction Homme Machine ===<br />
<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| Stylet || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || N/A || style="background:lightgreen;" | Oui || ??<br />
|-<br />
| Doigts || Partiellement || Partiellement || Partiellement || N/A || style="background:lightgreen;" | Oui || ??<br />
|-<br />
| Accéléromètres || Non || Non || Non || N/A || Non || ??<br />
|-<br />
|}<br />
<br />
=== Applications ===<br />
<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| Terminal || Basic (2) || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui (1) || N/A || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui<br />
|-<br />
| PIM || style="background:lightgreen;" | Oui || Non || style="background:lightgreen;" | Oui || N/A || style="background:lightgreen;" | Oui || ??<br />
|-<br />
| Répertoire téléphonique || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || N/A || style="background:lightgreen;" | Oui || ??<br />
|-<br />
| Dialer || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || N/A || style="background:lightgreen;" | Oui || ??<br />
|-<br />
| Navigateur Web || style="background:lightgreen;" | Oui (1) || ? || style="background:lightgreen;" | Oui (1) || ? || Non || ?<br />
|-<br />
| Client Mail || ? || ? || ? || ? || style="background:lightgreen;" | Oui || ?<br />
|-<br />
| Client XMPP || style="background:lightgreen;" | Oui (1) || ? || ? || ? || Non || ?<br />
|-<br />
|}<br />
<br />
=== Suite d'outils / Runtimes ===<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| GTK+ || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui || Non || ??<br />
|-<br />
| QT/Qtopia || Non || style="background:lightgreen;" | Oui? || style="background:lightgreen;" | Oui || style="background:lightgreen;" | Oui? || style="background:lightgreen;" | Oui || ??<br />
|-<br />
| Intergiciel || gsmd/neod || freesmartphone.org || qtopia-x11 || freesmartphone.org || qtopia || ??<br />
|-<br />
| [[Java]] || Jalimo || ? || ? || ? || ? || ??<br />
|-<br />
| [[Python]] || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || ??<br />
|-<br />
|}<br />
<br />
<br />
Notes annexes:<br />
<br />
(1) Fonctionne mais nécessite l'installation de programmes supplémentaires.<br />
<br />
(2) Inutilisable en raison du manque de certains caractères sur le clavier (sauf en changeant la [[Switching_Keyboards#Matchbox_keyboard|install table de correspondance du clavier]])<br />
<br />
(3) Il existe une interface utilisateur mais elle plante le téléphone lorsqu'elle est utilisée.<br />
<br />
(*) Instable<br />
<br />
== Liens externes ==<br />
<br />
Les descriptions originelles des distributions proviennent du Mickey Layer's [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!].<br />
<br />
[[Category:Distributions|Distributions]]<br />
[[Category:Documentation]]</div>Youshehttp://openmoko.org/wiki/Distributions/frDistributions/fr2008-08-10T10:59:31Z<p>Youshe: Traduction partielle en français</p>
<hr />
<div>{{Languages|Distributions}}<br />
<br />
{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"<br />
|<font color=white>Distributions</font><br />
|-<br />
! style='background-color:#333333;color:#FFFFFF'|<br />
<div align=left><br />
* <font color='#BBBBBB'>Openmoko (officiel)</font><br />
** [[Om 2008.8]]<br />
** [[Om 2007.2]]<br />
** [[OpenmokoFramework|FSO]]<br />
* <font color='#BBBBBB'>Communauté</font><br />
** [[SHR]]<br />
* <font color='#BBBBBB'>Autres</font><br />
** [[Qtopia]]<br />
** [[Debian]]<br />
</div><br />
|-<br />
|}<noinclude>[[Category:Templates]]</noinclude><br />
<br />
Les différentes distributions d'Openmoko sont produites afin de tourner sur différents périphériques mobiles, avec comme première cible d'Openmoko Inc les téléphones [[Neo 1973]] et le [[Neo FreeRunner]].<br />
Ces distributions sont similaires à des distributions linux : des systèmes d'exploitation complets avec leurs applications utilisateurs.<br />
Vous pouvez installer n'importe laquelle de celles ci sur votre téléphone ou avoir un système de multiboot avec plusieurs distributions d'installées.<br />
<br />
Alors que les distributions d'Openmoko peuvent aussi tourner sur [[Supported devices|d'autres appareils mobiles]], d'autres distributions logicielles peuvent aussi s'exécuter sur les téléphones d'Openmoko Inc (voir plus loin).<br />
<br />
Pour les téléchargements, voir [[Lastest Images|Dernières images]], pour les instructions d'installations voir [[Flashing the Neo FreeRunner]]<br />
<br />
== A propos des distributions ==<br />
<br />
Pour ^etre précis techniquement, les distributions 2007.2, 2008.8, FSO et SHR ne sont pas réellement des distributions indépendantes, mais des distributions visant des cibles matérielles différentes. Elles ont été construites à partir de différentes branches de la métadistribution [[OpenEmbedded]]. Par exemple, 2007.2 et 2008.8 sont ce qu'Ubuntu Gutsy est à Kubuntu Hardy.<br />
L'une devrait seulement utiliser des packages de la branche correspondante, sinon, des choses risquent de ne pas bien se passer, comme l'utilisation des .deb de Hardy sur un système Gutsy.<br />
Par ailleurs, il est à noter qu'il n'existe, à l'heure actuelle, pas de mise à jour supportée entre ces deux distributions. Ainsi, mettre à jour l'une d'elle en changeant la provenance des paquets résultera dans un système cassé et probablement impossible à booter. Pour conclure, utilisez toujours le [[dfu-util]] pour changer de distribution ou installez les en dual boot (ex, via une carte SD ou NFD)<br />
<br />
== Révisions cibles dirigées par Openmoko Inc. ==<br />
<br />
=== Om 2007.2 (GTK) ===<br />
<br />
[[Om 2007.2]] est pour les personnes voulant se familiariser avec l'initiative [http://www.gnome.org/mobile/ GNOME Mobile] et qui veulent écrire des applications qui peuvent s'exécuter sur une multitude de systèmes utilisant (des parties) du GNOME Mobile. Cette distribution introduit Maemo, qui tourne sur les Tablettes Internet Nokia. La force de la couche GTK+ est une interface utilisateur et un environnement de programmation similaire à ce que l'on peut trouver sur un système linux de bureau, si vous ^etes sous GNOME. GTK+ a "PIM applications" basées sur le "Evolution Data Server" et utilise le serveur téléphonique gsmd. Bien que l'on puisse les utiliser, ces application sont encore bugguées et non finies.<br />
Certaines personnes ont des problèmes avec la stabilité du serveur téléphonique.<br />
<br />
* [[Om 2007.2]]<br />
* Disponibilité: [http://buildhost.openmoko.org/daily/ hotes officiels] et [[MokoMakefile]] pour la compilation<br />
* Téléchargement: [http://buildhost.openmoko.org/daily/freerunner/ Les révisions sont nommées "openmoko-devel-image" ]<br />
* Diverses vidéos sur cette couche sont disponibles sur Youtube : [http://uk.youtube.com/user/freeyourphone user freeyourphone] et le [http://uk.youtube.com/watch?v=U05kZfURPig&NR=1 video review par BVB Tech]<br />
<br />
Il s'agit du système de base installé sur le Neo Freerunner lorsqu'il quitte l'usine de fabrication.<br />
Le développement conduit par Openmoko inc. sur la version 2007.2 a stoppé et les ressources sont allouées en faveur de la version 2008.8, alors que la communauté est en train de faire un effort pour sauver les applications téléphoniques de la v2007.2 dans le but de les placer dans le futur intergiciel du FSO (cf. SHR).<br />
De tels patchs sont toujours les bienvenus, surtout s'ils aident le développement de SHR.<br />
<br />
=== Om 2008.8 (ASU, Mises à jour logicielles Avril/aout) ===<br />
<br />
Om 2008.8 a débuté afin d'intégrer la pile [http://trolltech.com/products/qtopia Qtopia] - sur X11 - avec un nouvel ensemble d'applications graphiques basées sur les librairies fondatrices de Enlightenment. ASU est le nom interne et est connu comme Om 2008.8 depuis sa sortie le 8 aout 2008. Qtopia est un projet plus mature que la pile mobile GNOME et vous pouvez en attendre toutes les fonctionnalités standard téléphonie, le tout dans un environnement stable. Cette couche utilise le serveur téléphonique Qtopia. Cependant - contrairement au standard Qtopia - elle n'utilise pas directement le framebuffer, ce qui permet un partage fiable de l'écran entre les applications Qt et non Qt.<br />
<br />
* [[Om2008.8|Om 2008.8]]<br />
* Téléchargement : [http://downloads.openmoko.org/releases/Om2008.8/ Les images sont nommées "Om2008.8" ]<br />
<br />
=== FSO - freesmartphone.org ===<br />
<br />
FSO a vu le jour afin de palier aux manques des couches 2007.2 et 2008.8, à savoir pour créer un framework extensible qui fournit aux développeurs une infrastructure permettant de créer de solides applications basées sur la plateforme Openmoko.<br />
Le framework supporte plusieurs interfaces utilisateur concurrentes qui peuvent alors collaborer pour développer des services, fournissant ainsi un solide framework.<br />
<br />
Ici, l'objectif est basé sur des services de haut niveau qui peuvent ^etre accédés par l'intermédiaire de n'importe quel langage ou interface qui supportent [http://dbus.freesmartphone.org/ dbus]. On rapporte que malgré sa simplicité, le serveur téléphonique de FSO est déjà plus fiable que tout le reste.<br />
<br />
Il ne s'agit en fait pas vraiment d'une future révision/cible, mais plus un contenant pour le développement de nouveau et futur intergiciel.<br />
<br />
Les applications installées de base sont dédiées à des outils de test pour le futur intergiciel et ne sont pas tout à fait terminées et non orientées vers l'utilisateur final (M^eme si elles en ont l'air de temps en temps).<br />
<br />
* [[FSO]]<br />
* [http://trac.freesmartphone.org:8000/trac-example Development tracker]<br />
* [http://downloads.openmoko.org/framework/milestone2/ Téléchargement de milestone 2]<br />
* [http://freesmartphone.org freesmartphone.org]<br />
<br />
<br />
== Révisions cibles pilotées par la communauté openmoko ==<br />
<br />
=== SHR - Stable Hybrid Release (Révision stable hybride) ===<br />
<br />
La révision hybride stable est une combinaison du middleware provenant de FSO, de certaines parties du logiciel GTK de 2007.1 (telephony-ui, pim) et de 2008.8 qui fournit toutes les fonctionnalités du logiciel 2007.2, mais avec la stabilité de FSO.<br />
<br />
* [[Stable Hybrid Release]]<br />
<br />
== Distributions Non-Openmoko ==<br />
<br />
Ces distributions ne sont pas basées sur des distributions Openmoko (et OE). Il s'agit d'alternatives que vous pouvez utiliser sur vos téléphones Openmoko.<br />
<br />
=== Qtopia ===<br />
<br />
La distribution Qtopia de [http://www.trolltech.com Trolltech] vise à fournir une image pr^ete à l'utilisation pour les matériels Openmoko.<br />
<br />
* [[Qtopia]]<br />
* Téléchargement: [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Qtopia.net]<br />
<br />
=== Debian ===<br />
<br />
L'entière distribution Debian Linux sur un téléphone portable.<br />
<br />
* [[Debian]]<br />
<br />
== Fonctionnalités par distribution/révision cible ==<br />
<br />
=== Connectivité ===<br />
<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| Téléphonie || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| SMS || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| GPRS || Not through UI || Not through UI || Not through UI || N/A || No (3) || ??<br />
|-<br />
| WiFi || style="background:lightgreen;" | Yes || Not through UI || style="background:lightgreen;" | Yes (*) || N/A || style="background:lightgreen;" | Yes ||style="background:lightgreen;" | Yes<br />
|-<br />
| VoIP || ?? || ?? || ?? || ?? || ?? || ??<br />
|-<br />
| Bluetooth || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| GPS || style="background:lightgreen;" | Yes (1) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || No || ??<br />
|-<br />
|}<br />
<br />
=== Interaction utilisateur ===<br />
<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| "Stylet friendly" || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| "Doigts friendly" || Partiellement || Partiellement || Partiellement || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| Accéléromètres || No || No || No || N/A || No || ??<br />
|-<br />
|}<br />
<br />
=== Applications ===<br />
<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| Terminal || Basic (2) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes<br />
|-<br />
| PIM || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| Carnet téléphonique || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| Dialer || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| Navigateur Web || style="background:lightgreen;" | Yes (1) || ? || style="background:lightgreen;" | Yes (1) || ? || No || ?<br />
|-<br />
| Client Mail || ? || ? || ? || ? || style="background:lightgreen;" | Yes || ?<br />
|-<br />
| Client XMPP || style="background:lightgreen;" | Yes (1) || ? || ? || ? || No || ?<br />
|-<br />
|}<br />
<br />
=== Suite d'outils / Runtimes ===<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| GTK+ || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || No || ??<br />
|-<br />
| QT/Qtopia || No || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| Intergiciel || gsmd/neod || freesmartphone.org || qtopia-x11 || freesmartphone.org || qtopia || ??<br />
|-<br />
| [[Java]] || Jalimo || ? || ? || ? || ? || ??<br />
|-<br />
| [[Python]] || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || ??<br />
|-<br />
|}<br />
<br />
<br />
Notes annexes:<br />
<br />
(1) Fonctionne mais nécessite l'installation de programmes supplémentaires.<br />
<br />
(2) Inutilisable en raison du manque de certains caractères sur le clavier (sauf en changeant la [[Switching_Keyboards#Matchbox_keyboard|install table de correspondance du clavier]])<br />
<br />
(3) Il existe une interface utilisateur mais elle plante le téléphone lorsqu'elle est utilisée.<br />
<br />
(*) Instable<br />
<br />
== Liens externes ==<br />
<br />
Les descriptions originelles des distributions proviennent du Mickey Layer's [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!].<br />
<br />
[[Category:Distributions|Distributions]]<br />
[[Category:Documentation]]</div>Youshehttp://openmoko.org/wiki/Main_Page/frMain Page/fr2008-08-09T17:57:44Z<p>Youshe: </p>
<hr />
<div>{{Languages|Main Page}}<br />
__NOTOC__<br />
__NOEDITSECTION__ [[Image:Freerunner02.gif|thumb|150px|right|Neo Freerunners]]<br />
<br />
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div><br />
<br />
Openmoko™ est un projet destiné à fournir un téléphone portable doté d'une couche logicielle opensource. <br />
A l'heure actuelle, Openmoko propose à la vente le téléphone [[Neo FreeRunner]] dédié pour l'instant à des utilisateurs avancés.<br />
Une fois que la coucle logicielle sera plus élaborée, le grand public pourra être visé.<br />
<br />
La couche logicielle Openmoko -qui inclue un serveur X complet- permet aux utilisateurs et développeurs de transformer la plateforme matérielle en un produit unique.<br />
Notre licence donne en effet la liberté la liberté d'adapter l'interface graphique, voir de la modifier totalement, de changer le fond d'écran, ou encore de modifier totalement l'aspect logiciel !<br />
La licence donne ainsi par exemple la liberté à l'utilisateur de transformer son téléphone en un appareil médical, en un espace de vente portatif ou encore de simplement installer ses applications favorites.<br />
En plus de proposer un logiciel libre sur nos machines, nous fournissons aussi l'intégralité du design sous licence Creative Commons.<br />
Par ailleurs, nous avons annoncé la diffusion des spécifications de nos produits aux Linux World 2008<br />
<br />
<div style="clear:both">&nbsp;</div><br />
<br />
<table class="wikitable" cellspacing="4" cellpadding="6" width="100%" style="color:white"><br />
<tr style="background:#ff6600; text-align:center; font-weight:bold"><br />
<td width="50%">Nouveautés et évènements</td><br />
<td width="50%">Nouveau sur Openmoko ?</td><br />
</tr><br />
<tr valign="top" style="background:#333333"><br />
<td><br />
* 8/8: Première sortie officielle de [[Om 2008.8]] (cf. [http://lists.openmoko.org/pipermail/community/2008-August/025619.html])<br />
* 4-5/8: Openmoko à Linuxworld, San Francisco<br />
* 30/7: La distribution FSO sort [http://downloads.openmoko.org/framework/milestone2/ milestone 2]<br />
* 25/7: Aide communautaire, [[GPS Problems|Problèmes de GPS]] corrigés<br />
* 20/7: Ajout de [[Debian]] à la page des [[Distributions]]<br />
* 27/6: Vente du GTA 02 sur [http://lists.openmoko.org/pipermail/community/2008-June/019943.html material world]<br />
</td><br />
<td><br />
===<font color=white>A propos d'Openmoko</font>===<br />
<br />
* [[Introduction/fr|Introduction]]<br />
* [[Why Openmoko|Pourquoi Openmoko ?]]<br />
* [[Neo FreeRunner/fr|Le Neo FreeRunner]]<br />
* [[Supported Hardware|Matériel supporté]]<br />
* [[FAQ/fr|FAQ]]<br />
<br />
===<font color=white>Se procurer Openmoko</font>===<br />
* [[Getting Openmoko|Obtenir Openmoko]]<br />
* [http://www.openmoko.com Openmoko Inc.]<br />
* [http://bearstech.com/shop bearstech : le revendeur Français]<br />
<br />
</td><br />
</tr><br />
<tr style="background:#ff6600; text-align:center; font-weight:bold"><br />
<td width="50%">Pour les utilisateurs</td><br />
<td width="50%">Pour les développeurs</td><br />
</tr><br />
<tr valign="top" style="background:#333333"><br />
<td><br />
===<font color=white>Où commencer ?</font>===<br />
* [[Getting Started with your Neo FreeRunner/fr|Guide de démarrage du Neo FreeRunner]]<br />
* [[Getting Started FAQ|FAQ sur le guide de démarrage]]<br />
<br />
<br />
===<font color=white>Logiciel</font>===<br />
* [[Distributions|Distributions logicielles Openmoko]]<br />
* [[Om 2007.2|Openmoko 2007.2]]<br />
* [[Om 2008.8|Openmoko 2008.8]]<br />
* [[OpenmokoFramework|distribution FSO]]<br />
* [[Qtopia_on_FreeRunner|distribution Qtopia]]<br />
<br />
===<font color=white>Communauté Openmoko</font>===<br />
* [[Discussion_Forums| Forums de discussion]]<br />
* [[CommunityRepository|Repository Commonautaire]]<br />
* [[Development resources | Ressources concernant le développement]]<br />
* [http://openmoko-fr.org Communauté Française]<br />
</td><br />
<td><br />
===<font color=white>Développement applicatif</font>===<br />
* [[Openmoko developer guide|Guide du développeur Openmoko]]<br />
* [[Toolchain|Suite d'outils]]<br />
<!-- * <font color=white>VMware</font> --><br />
* [[Python|Introduction à Python]]<br />
* [http://projects.openmoko.org/ Projects hosted in our GForge]<br />
<br />
===<font color=white>Intégration et distributions</font>===<br />
* [[OpenEmbedded|Librairie de développement OpenEmbedded]]<br />
* [[MokoMakefile|Compiler Openmoko à l'aide du MokoMakefile ]]<br />
* [[Opkg|Opkg, le gestionnaire de packages]]<br />
<br />
===<font color=white>Emulation</font>===<br />
* [[Openmoko under QEMU|Openmoko sous QEMU]]<br />
</td><br />
</tr><br />
</table><br />
<br />
[[Category:Information| ]]</div>Youshehttp://openmoko.org/wiki/Qtopia_/_Qt_Extended_on_FreeRunnerQtopia / Qt Extended on FreeRunner2008-08-09T17:48:27Z<p>Youshe: Languages</p>
<hr />
<div>{{Languages|Qtopia_on_FreeRunner}}<br />
<br />
This page provides instructions on how to install Qtopia (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (Freerunner) phone. It is similar to the [[Qtopia on Neo1973]] page.<br />
<br />
{|align=right<br />
|__TOC__<br />
|}<br />
<br />
== Current status ==<br />
On 08 August 2008, Qtopia released the [http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=77 latest flash image for the FIC Neo Freerunner (gta02)] containing the Qtopia 4.3.2 snapshot (Version: 4.3.2-080808) of 08 August 2008 (GPL version). <br />
<br />
This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does not, however, have a web browser or a GPS application.<br />
<br />
You can find all the Qtopia images [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 here]<br />
<br />
== Option 1: Flashing Qtopia to FreeRunner ==<br />
<br />
Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]<br />
<br />
== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==<br />
<br />
Installation Requirements: <br />
<br />
# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.<br />
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)<br />
<br />
<br />
=== Preparing the SD card ===<br />
<br />
See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions.<br />
<br />
<br />
=== Installing Qtopia ===<br />
<br />
==== Unpacking the Qtopia Root Filesystem Image ====<br />
<br />
Download the Qtopia FLASH image from [[Latest Images#Qtopia image from qtopia.net]] to your Linux box and extract its contents:<br />
<br />
tar xzf qtopia-4.3.2-gta02-flash-*.tgz<br />
<br />
You should now have two files: <br />
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin<br />
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2 <br />
Now extract the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]].<br />
<br />
<br />
Now, tar up the root filesystem:<br />
<br />
tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .<br />
<br />
Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted.<br />
<br />
==== Installing Root Filesystem ====<br />
<br />
Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:<br />
<br />
scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/<br />
<br />
Log in to your FreeRunner and unpack the root filesystem:<br />
<br />
cd /media/mmcblk0p2<br />
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br />
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br />
rm -f /media/mmcblk0p2/boot/*<br />
<br />
'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.<br />
<br />
==== Installing Kernel ====<br />
<br />
From your Linux box, rename uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin to uImage.bin and copy it to the boot/ on the first partition of the MicroSD card.<br />
<br />
{{note|There are reports that the kernel image sometimes does not work from the /boot directory. If this is the case for you, try moving the kernel image into the root of the microSD card, ie: /media/card instead of /media/card/boot. This is probably dependent on the version of U-Boot installed. It also doesn't hurt, seeing as there is room on the first partition, to simply have uImage.bin in both locations.}}<br />
<br />
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin<br />
scp uImage.bin root@192.168.0.202:/media/card/boot/<br />
scp uImage.bin root@192.168.0.202:/media/card/<br />
<br />
=== Option 3: updating from source ===<br />
<br />
{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}<br />
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:<br />
<br />
* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 <br />
* unzip it on your PC in / (as root)<br />
* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/<br />
* once dowloaded untar it<br />
tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz<br />
* make a "build" dir <br />
mkdir build<br />
cd build<br />
* configure and make:<br />
../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01<br />
make <br />
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:<br />
<br />
make install<br />
<br />
will make a root directory into build directory. That directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.<br />
<br />
=== Booting into Qtopia ===<br />
<br />
Now shutdown the FreeRunner<br />
<br />
shutdown -h now<br />
<br />
Log into U-Boot in the NOR Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])<br />
<br />
* Press and hold Power button<br />
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds. <br />
* A boot menu will appear. <br />
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.<br />
<br />
Qtopia should now boot.<br />
<br />
'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run<br />
<br />
umount /dev/mmcblk0p2<br />
fsck.ext3.e2fsprogs /dev/mmcblk0p2<br />
<br />
This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.<br />
<br />
[[Category:Distributions]]<br />
[[Category:Qtopia]]</div>Youshehttp://openmoko.org/wiki/Manuals/Neo_FreeRunner/frManuals/Neo FreeRunner/fr2008-08-09T17:38:33Z<p>Youshe: </p>
<hr />
<div>{{Languages|Getting_Started_with_your_Neo_FreeRunner}}<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #cccccc; background:#eeeeee; width:100%;floating="center"; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:75% " | <br />
<div align="left"><br />
Merci d'avoir acheté cette version du Neo FreeRunner pour les développeurs. Le téléphone [[Neo FreeRunner]] est la deuxième plate-forme matérielle à utiliser OpenMoko. Ce guide vous aidera à mieux connaître votre Neo FreeRunner et commencer à utiliser votre Neo FreeRunner.<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Freerunner box.png|200px|thumb|La Boîte Neo FreeRunner]]<br />
|}<br />
<br />
== Ce que contient la boîte==<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #ffffff; background:#ffffff; width:80%; floating="center"; "<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid ffffff; border:1px solid #ffffff; " | <br />
<div align="left"><br />
[[Image:GTA02ALL.png|400px|thumb|Contenu de la boîte]]<br />
|<br />
<br />
: [[Image:Circle2.gif|10px]] Neo FreeRunner<br />
: [[Image:Circle2.gif|10px]] Stylet<br />
: [[Image:Circle2.gif|10px]] Batterie<br />
: [[Image:Circle2.gif|10px]] Chargeur<br />
: [[Image:Circle2.gif|10px]] Cable USB <br />
: [[Image:Circle2.gif|10px]] Carte microSD 512MB<br />
|}<br />
</div><br />
<br />
== Aperçu du Neo FreeRunner==<br />
<br />
<div align-center><br />
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;"><br />
<tr valign="top" style="background: #ffffff"><br />
<td style="width: 25px; padding-left: 0.5em;"><br />
</td><br />
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu8.jpg|370px|thumb|Bouton AUX et jack du casque-micro (De gauche à droite)|center]]</td><br />
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu9.jpg|365px|thumb|Bouton d'Alimentation, USB et Antenne GPS externe (De gauche à droite)|center]]</td><br />
</tr></table><br />
</div><br />
<br />
<div align-center><br />
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;"><br />
<tr valign="top" style="background: #ffffff"><br />
<td style="width: 50%; padding-left: 0.5em;"><br />
</td><br />
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu12.jpg|233px|thumb|Dos de l'AUX avec sa batterie|center]]</td><td style="padding: 1px 1em 0; background: #ffffff;"><br />
[[Image:menu11.jpg|260px|thumb|Mettez la carte SIM et la carte SD ici|center]]</td></tr></table><br />
</div><br />
<br />
<div align-center><br />
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;"><br />
<tr valign="top" style="background: #ffffff"><br />
<td style="width: 50%; padding-left: 0.5em;"><br />
</td><br />
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|ouvrir le boîtier de ce côté |center]]</td><td style="padding: 1px 1em 0; background: #ffffff;"><br />
[[Image:menu14.jpg|250px|thumb|Ouvert|center]]</td></tr></table><br />
</div><br />
<br />
===Installation de la carte Micro SD, de la carte SIM, et de la batterie ===<br />
<br />
# Retirez le capot arrière du Néo Freerunner en maintenant le Neo Freerunner par le côté, et utiliser votre ongle pour détacher le capot arrière au niveau de la fente en haut<br />
# Identifier l'emplacement combiné de la carte SIM et de la carte SD au fond du compartiment à piles<br />
# Déverrouiller la carte SIM en faisant glisser la languette de métal vers le bas (vers la prise USB) avec votre ongle. Soyez prudent car ces languettes sont délicates et pourraient être endommagées en forçant dans la mauvaise direction. Les propriétaires du Neo 1973 devraient accorder une attention particulière, puisque la direction pour l'ouverture est opposé à celle du Neo 1973.<br />
# Soulevez la carte SIM<br />
# Le compartiment Micro-SD de la carte est maintenue en place par un verrouillage par languette de chaque côté. Il est plus facile d'ouvrir le compartitement Micro-SD de la carte par la libération de ces languettes une par une plutôt que par la levée par le milieu, comme la levée par le milieu tend à augmenter la pression de fermeture. Un petit tournevis ou un couteau peut être utilisé pour:<br />
# Insérez la carte Micro SD dans le compartiment Micro SD de la carte. Notez que les contacts doivent être dirigés vers le bas, et sont sur le front du Néo Freerunner:<br />
# Fermer le compartiment Micro SD de la carte, en vous assurant que les deux doigts sont bien fermé:<br />
# Insérez la carte SIM dans le compartiment de la carte SIM, en prenant soin de glisser les deux languettes de métal dans la couverture. Note que les languettes doivent être dirigés vers le bas, et que le chanfrein (le coin coupé) sera plus proche de l'emplacement de l'antenne GPS externe:<br />
# Fermer le compartiment de la carte SIM et verrouillez-le en glissant la languette vers l'emplacement de l' antenne GPS externe:<br />
# Insérez la batterie dans son compartiment, en alignant les contacts de la batterie avec ceux de son compartiment. Insérez en premier le côté possédant les contacts.<br />
# Remettez le couvercle<br />
<br />
===Allumer le Neo Freerunner===<br />
<br />
====Charger the Neo Freerunner====<br />
<br />
Lors de la première utilisation du Neo Freerunner, vous devez charger complétement la batterie. La batterie peut être chargé avec le chargeur fourni, ou part un port USB capable de fournir 500mA d'un ordinateur.<br />
La charge à 100mA prend de 6 à 12 heures et celle à 500mA prend de 1 à 2 heures. (from [http://openmoko.togaware.com/survivor/Charging.html openmoko.togaware.com])<br />
<br />
Vous pouvez démarrer votre Neo FreeRunner des façons suivantes:<br />
<br />
: [[Image:Circle2.gif|10px]] Vous pouvez démarrer directement sur une image Openmoko. <br />
<br />
: [[Image:Circle2.gif|10px]] Démarrer par [[Bootloader|U-Boot]] par l'intermédiaire de la [[NAND Flash]].<br />
<br />
: [[Image:Circle2.gif|10px]] Démarrer par U-Boot par l'intermédiaire de la Flash NOR.<br />
<br />
Ces manières vous permettent de mettre à jour le noyau et le système de fichiers racine.<br />
<br />
====Démarrer sur l'Image Openmoko====<br />
<br />
<div align-center><br />
<table width="100%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;"><br />
<tr valign="top" style="background: #ffffff"><br />
<td style="width: 25px; padding-left: 0.5em;"><br />
<br />
</td><br />
<td style="width: 10px; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:Menu2.jpg|200px|right|thumb]]</td><td style="padding: 1px 1em 0; background: #eeeeee;"><br />
Maintenez enfoncée la touche bouton d'alimentation (environ 8 secondes) jusqu'à ce que l'écran d'accueil OpenMoko se présente. Vous pouvez lachez le bouton d'alimentation, ainsi Le Neo FreeRunner s'amorera avec l'Image OpenMoko.<br />
<br />
</td></tr></table><br />
</div><br />
<br />
====Démarrer par U-Boot par l'intermédiaire de la Flash NAND====<br />
<br />
<div align-center><br />
<table width="100%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;"><br />
<tr valign="top" style="background: #ffffff"><br />
<td style="width: 25px; padding-left: 0.5em;"><br />
<br />
</td><br />
<td style="width: 10px; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:Menu7.jpg|200px|right|thumb]]</td><td style="padding: 1px 1em 0; background: #eeeeee;"><br />
Maintenez le bouton d'alimentation enfoncé, puis appuyez sur le bouton AUX (environ 5 ~ 8 secondes). Vous pouvez voir le menu de démarrage de la Flash NAND. Appuyez sur le bouton AUX pour sélectionner les options, et sur celui de l'alimentation pour les exécuter.<br />
</td></tr></table><br />
</div><br />
<br />
====Démarrer par U-Boot par l'intermédiaire de la Flash NOR====<br />
<br />
<div align-center><br />
<table width="100%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;"><br />
<tr valign="top" style="background: #ffffff"><br />
<td style="width: 25px; padding-left: 0.5em;"><br />
<br />
</td><br />
<td style="width: 10px; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:Menu6.jpg|200px|right|thumb]]</td><td style="padding: 1px 1em 0; background: #eeeeee;"><br />
<br />
Maintenez le bouton AUX enfoncé, puis appuyez sur le bouton d'alimentation et maintenez enfoncé. Relachez le bouton AUX. Vous pouvez voir le menu de démarrage de la Flash NOR. (Cette option est généralement utilisée par les développeurs ou lorsque vous flashezle FreeRunner. Aussi, si vous ne pouvez pas vous connecter par U-Boot dans la flash NAND, alors vous pouvez vous connecter par U-Boot dans la Flash NOR.)<br />
</td></tr></table><br />
</div><br />
<br />
{{note| Il ya six options que vous pouvez choisir lorsque vous vous connectez par la Flash NOR.<br />
1. Démarrer<br />
<br />
2. [[Boot from sd card|Démarrer à partir de la MicroSD]]<br />
<br />
3. Lier la console à l'USB<br />
<br />
4. Lier la console au port série<br />
<br />
5. Réinitialiser<br />
<br />
6. Eteindre<br />
<br />
}}<br />
<br />
===Déverouiller l'écran===<br />
<br />
Lorsque l'écran est verrouillé, vous voyez un graphique vert du style Matrix avec le symbole OpenMoko au centre du bas de l'écran, un symbole verrouiller et déverrouiller. Si vous faites glisser le symbole OpenMoko sur le symbole déverrouiller en haut, alors l'écran sera déverrouillée.<br />
<br />
==Flasher le Neo FreeRunner==<br />
Comme le développement d'Openmoko continu, Openmoko publie réguliérement des versions mises à jour du système de fichier racine Openoko, du noyau, et de[[Bootloader|U-Boot]]. Ils peuvent être programmé dans la mémoire Flash du Neo FreeRunner. Vous pouvez utiliser le cable USB et l'outil fourni par Openmoko pour flasher le Neo FreeRunner.<br />
<br />
{{note|L'équipe du département logiciel d'Openmoko construit des images chaque jour. Si vous souhaitez utiliser les dernières images, vous pouvez les téléchargé à partir de la construction journalière, mais nous vous recommandons de télécharger des images plus stable à partir de http://downloads.openmoko.org/releases/Freerunner/. Ces Images ont été vérifié par l'équipe de test.}}<br />
<br />
===Etape 1. Télécharger DFU-util===<br />
<br />
Vous pouvez télécharger l'outil qui permet de flasher le Neo Freerunner à partir de: <br />
http://downloads.openmoko.org/releases/Freerunner/dfu-util<br />
<br />
Sur l'hôte GNU/Linux, vous pouvez utiliser la ligne de commande suivante pour télécharger dfu-util:<br />
wget http://downloads.openmoko.org/releases/Freerunner/dfu-util<br />
<br />
Ensuite vous devez changer les droits:<br />
chmod a+x dfu-util<br />
<br />
===Etape 2. Flasher le noyau===<br />
<br />
Vous pouvez télécharger le noyau à partir de <br />
http://downloads.openmoko.org/releases/Freerunner/<br />
<br />
Taper la ligne de commande suivante dans le terminal d'un hôte GNU/Linux. Sur certains systèmes vous aurez besoins d'être root.<br />
./dfu-util -a (partion name) -R -D (download image file name)<br />
<br />
<br />
ex:<br />
<br />
./dfu-util -a kernel -R -D uImage-2.6.24+svnr4082-r4055-r3-neo1973.bin<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:0px solid #ffffff; background:#ffffff; width:100%;floating="center"; "<br />
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid ffffff; border:1px solid #ffffff; width:75% " | <br />
<div align="left"><br />
[[Image:menu15.jpg|thumb|Connectez-vous par U-Boot dans la Flash NOR, connectez votre Neo avec l'hôte Linux par un câble USB]]<br />
Avant d'exécuter la commande, s’il vous plaît connectez-vous par U-Boot dans la Flash NOR. Neo FreeRunner doit démarrer en U-boot pour être flasher.<br />
<br />
Ensuite, connectez votre Neo avec Linux hôte par un câble USB. Appuyez sur Entrée pour exécuter la commande. Lorsque le flash a réussi vous verrez:<br />
<br />
status(0) = No error condition is present<br><br />
Done!<br />
</div><br />
|}<br />
<br />
{{note| La signification des paramètres que vous avez entré:<br />
-a --alt alt Specifie le parametrage alt de l'interface DFU par un nom ou par un nombre<br><br />
-R --reset Effectue une Réinitialisation USB une fois que c'est fini<br><br />
-D --download file Ecrit le micrologiciel à partir de<file> dans l'appareil <br><br />
}}<br />
<br />
===Step 3. Flasher le système de fichier Racine ===<br />
Vous pouvez télécharger le système de fichier racine à partir de :<br />
http://downloads.openmoko.org/releases/Freerunner/<br />
<br />
<br />
Taper la ligne de commande suivante dans le terminal d'un hôte GNU/Linux. Sur certains systèmes vous aurez besoins d'être root.<br />
<br />
./dfu-util -a rootfs -R -D openmoko-devel-image-fic-gta02.jffs2<br />
<br />
Lorsque le flash a réussi vous verrez:<br />
<br />
status(0) = No error condition is present<br><br />
Done!<br />
<br />
==Connectez-vous à Neo FreeRunner par la mise en réseau USB==<br />
<br />
Connecter le Neo FreeRunner à l'hôte Linux avec le cable USB. Pour OS X veuillez suivre le lien suivant [[MacOS_X]]. Après le démarrage sur l'image Openmoko, il y aura une nouvelle interface, usb0, dans votre hôte Linux.<br />
<br />
=====Méthode Manuelle=====<br />
Taper les lignes suivantes dans un terminal de l'hôte GNU/Linux.<br />
<br />
ifconfig usb0 192.168.0.200 netmask 255.255.255.0<br />
ssh root@192.168.0.202<br />
<br />
Appuyer sur la touche Entrée pour donner le mot de passe.<br />
<br />
=====Methode Automatique=====<br />
*Debian et derivées (Ubuntu, Sidux etc.)<br />
Editer /etc/network/interfaces<br />
<br />
auto usb0<br />
iface usb0 inet static<br />
address 192.168.0.200<br />
netmask 255.255.255.0<br />
<br />
*Gentoo <br />
Editer /etc/conf.d/net<br />
<br />
config_usb0="192.168.0.200/24"<br />
<br />
Redémarrer le service de mise en réseau (/etc/init.d/networking restart pour les distributions basées sur Debian) et taper la commande suivante dans un terminal d'un hôte GNU/Linux.<br />
<br />
ssh root@192.168.0.202<br />
<br />
Appuyer sur la touche Entrée pour donner le mot de passe.<br />
<br />
=====Rendre les choses encore plus automatique=====<br />
Si vous ne voulez pas vous souvenir de l'addresse IP de votre téléphone, vous pouvez créer un alias en ajoutant la ligne suivante dans votre fichier /etc/hosts:<br />
<br />
192.168.0.202 openmoko<br />
<br />
Maintenant, il devrait être immédiatement possible de vous connecter à votre téléphone en utilisant la ligne de commande suivante:<br />
<br />
ssh root@openmoko<br />
<br />
La ligne ajoutée ci-dessus vous permet d'ouvrir une connection ssh sur OpenMoko, elle ne permet pas OpenMoko de se connecter à l'Internet. Pour faire cela, suivre les instructions dans la section [[USB_Networking]].<br />
<br />
==Annexe==<br />
Si vous souhaitez en savoir plus sur le FreeRunner, vous pouvez obtenir davantage d'information sur les sujets qui suivent:<br />
* [[GTA02 Openness]]<br />
* [[Neo FreeRunner]]<br />
* [[Neo FreeRunner GTA02 Hardware]]<br />
* [[FreeRunner/Buttons and LEDs]]<br />
<br />
[[Category:GTA02 Hardware]]</div>Youshehttp://openmoko.org/wiki/FAQ/frFAQ/fr2008-08-09T17:33:55Z<p>Youshe: Le changement de langue est mieux en haut !</p>
<hr />
<div>{{Languages|FAQ}}<br />
<br />
Questions and Answers that don't seem to fit elsewhere<br />
<br />
==Introduction== <br />
<br />
=== Q: Qu'est-ce que Openmoko et Neo1973 ? ===<br />
R: [[Openmoko/fr|Openmoko]] est une plateforme logicielle, une tentative de créer la première solution logicielle totalement ouverte au monde pour téléphone portable. Le [[Neo1973]] de [[FIC]] est le premier téléphone completement compatible avec [[Openmoko/fr|Openmoko]].<br />
<br />
=== Q: Je suis un ____ expert, est-ce que je peut rejoindre/aider Openmoko ? ===<br />
<br />
Nous aimerions avoir de vos nouvelles. <br />
<br />
Si vous êtes interéssé pour rejoindre Openmoko, visitez http://www.openmoko.com/contact-index.html et envoyez nous un mail. Ou vous pouvez aussi poster un message sur notre liste de participants si vous vooulez juste nous aider.<br />
<br />
=== Q: Quand pourrais-je acheter le [[neo1973]] ? ===<br />
<br />
R: Maintenant -sur from https://direct.openmoko.com/. Mais lisez d'abord "What will it do?".<br />
<br />
=== Q: À quel prix ? === <br />
<br />
R: Neo1973 GTA01B_v04: $300 pour le Neo Base, $450 pour le Neo Advanced. Disponible maintenant. Voir [[Neo1973]] pour ce qu'il fait.<br />
<br />
R: Neo1973 GTA02: $450 pour le Neo Base, $600 pour le Neo Advanced. Prévu pour être disponible en 2007. Voir [[Neo1973]] pour la liste du matériel.<br />
<br />
=== Q: Qu'est-ce qu'il fera? ===<br />
<br />
R: Pour une réponse longue voir [[Developer preview]]<br />
<br />
R: Le téléphone Phase 1 est conçu pour les développeurs. Il n'est pas utilisable par des utilisateurs normaux, il n'a que des fonction basiques comme celles d'un téléphone à écran tactile. Deux trois trucs marchent, mais le développement d'applications continuera jusqu'à la production de masse.<br />
<br />
Les personnes intéréssées doivent:<br />
<br />
* savoir qu'un nouveau modèle va sortir avec un processeur plus puissant, un système GSM … Dans quelques mois (GTA02 )<br />
* aimer hacker des appareils.<br />
* être capable de se débrouiller seules sans plus de documentation que ça…<br />
* partager le rêve d'un appareil utilisant des logiciels libres.<br />
* ne pas attendre un appareil du niveau d'un utilisateur.<br />
* proposer des idées pour explorer au maximum les possibilités ofertes par le téléphone.<br />
* avoir $300.<br />
<br />
Elles peuvent aussi:<br />
<br />
* chercher et rapporter les bugs.<br />
* publier des patches.<br />
* aimer coopérer avec une communauté pour améliorer les logiciels.<br />
<br />
=== Q: Ai-je besoin du Neo Advanced? === <br />
<br />
Avec le Neo de base vous pouvez faire:<br />
* du developpement de noyau.<br />
* du developpement d'applications.<br />
* mettre à jour le u-boot ( équivalent au BIOS d'un PC )en utilisant une image pré-testée.<br />
* remplacer un noyau defectueux et/ou rootfs utilisant [[Dfu-util]].<br />
<br />
Avec le Neo Advanced vous pouvez en plus faire:<br />
* du developpement de u-boot.<br />
* utiliser la console du noyau.<br />
* démonter votre téléphone si vous flashez une mauvaise image de u-boot.<br />
<br />
=== Q: J'ai une question relative à l'envoi du téléphone === <br />
<br />
Voir [[SH1_FAQ|Shipment 1 FAQ]].<br />
<br />
==Logiciel==<br />
<br />
<br />
=== Q: Le logiciel peut-il faire/se connecter à ... ===<br />
R: Pour le momoent, la réponse est non dans tout les cas. Le téléphone n'est pour le moment qu'une petite boite Linux avec un écran tactile, un système qui fonctionne pour les appels et pas mal de prototypes d'applications dont la plupart ne fonctionneront pas de manière correcte pour les utilisateurs.<br />
Si vous voulez ajouter des fonctionnalités ou demander des applications, jetez un coup d'oeil dans la liste des applications existantes et ajoutez celle que vous souhaitez, ou alors faites une demande d'ajout de fonctionnalités dans la page des applications.<br />
<br />
===Quels logiciels seront dans le téléphone?===<br />
Pour le moment, presque aucune application destinée aux utilisateurs n'est présente et utilisable de façon stable.<br />
Il est possible de téléphoner et de recevoir des appels.<br />
====Quels logiciels peuvent être installés sur le téléphone?====<br />
<br />
=== Q: Est-ce qu'une liste et une description des logiciels Openmoko est disponible? ===<br />
<br />
R: Voir [[Openmoko]] et [[OpenmokoFramework]]<br />
<br />
=== Q: Est-ce que c'est totalement opensource/composé de logiciels libres? ===<br />
<br />
R: L'espace utilisateur [[Gpsd]] utilisera un plugin binaire pour [[:Category:Neo1973 Hardware#AGPS|Hammerhead AGPS]] et [[:Category:Neo1973 Hardware#GSM.2FGPRS|le modem GSM]] est un sous-système séparé connecté au S3C2410 UART1. Le reste n'est que logiciel libre. Voir [[MokoMakefile]] et [[Development resources]].<br />
<br />
=== Q: Comment puis-je installer et gérer des logiciels sur Openmoko? ===<br />
<br />
R: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg<br />
<br />
=== Q: Comment puis-je compiler des programmes pour le Neo1973? ===<br />
<br />
R: Voir [[Toolchain]].<br />
<br />
=== Q: Un émulateur est-il disponible pour Openmoko? ===<br />
<br />
Pour le travail de developpement et le test, vous n'avez pas besoin d'émulateur car vous pouvez faire tourner Openmoko sur votre PC. Les émulateurs ne sont pas parfaits à 100%. Ceci étant dis, il y a plusieurs émulateurs qui sont décrits ci-après.<br />
<br />
====QEMU====<br />
QEMU peut maintenant émuler le Neo1973. Le [[MokoMakefile]] est supporté pour la compilation automatique et le fonctionnement de [[Openmoko under QEMU|l'émulateur Openmoko]].<br />
<br />
“make qemu” construira qemu-neo1973, téléchargera la dernière version officielle openmoko, chargera l'image dans la mémoire NAND virtuelle, et lancera l'émulateur.<br />
<br />
====Xoo====<br />
Un autre émulateur est [http://projects.o-hand.com/xoo Xoo]. Koen a dit: "Xoo doit être efficace pour le plus grand nombre d'applications que les gens développeront, celles qui n'ont pas besoin d'acceder au module GSM directement. Si vous êtes un peu fou ( hardcore )vous pouvez utiliser qemu + Xoo, mais ça n'émulera pas toute l'architecture matérielle (e.g. unaligned access ??)".<br />
<br />
Mise à jour: Stefan Schmidt a modifié le Mock-up du [[Neo1973]] et a écrit une petite description pour Xoo. Ses propos:<br />
<br />
Ce n'est pas réellement utilisable, comme une image en grande résolution pour trouver une image sur votre écran. Evidemment le dpi est mauvais. Il n'y a pas de boutons car je ne sais plus ou ils se trouvent sur le boitier.<br />
<br />
http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2<br />
<br />
Commencez avec 'xoo --device /path/to/neo1973.xml'<br />
<br />
Plus de détails ici [[Getting_Openmoko_working_on_host_with_Xoo|here]].<br />
<br />
====Xephyr====<br />
Ou utilisez Xephyr directement avec des programmes compilés (par exemple matchbox svn + openmoko):<br />
Xephyr -screen 480x640 -nolisten tcp -ac :1 &<br />
export DISPLAY=:1<br />
export LD_LIBRARY_PATH=/usr/local/lib<br />
matchbox-window-manager -display $DISPLAY -use_titlebar no \<br />
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \<br />
-use_cursor yes &<br />
matchbox-panel --geometry=480x44 --end-applets=clock &<br />
openmoko-footer &<br />
openmoko-taskmanager &<br />
<br />
=== Q: Ou puis-je trouver des tutoriaux pour un petit 'Hello World' sur Openmoko? ===<br />
<br />
R: Vous pouvez commencer avec ça http://www.gtk.org/tutorial/<br />
<br />
=== Q: Can PalmOS apps applications be ported to run on Openmoko? ===<br />
<br />
A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux<br />
is decidedly non-trivial.<br />
<br />
PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.<br />
<br />
The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M6800 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.<br />
<br />
It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on Openmoko, but this has to be considered a short-term bandaid rather than a long-term solution.<br />
<br />
The soon-to-be-released [http://www.palm.com/foleo/ Palm Foleo], which runs a Linux port developed by Palm Inc. independently of ALP, contains a PalmOS compatibility environment that runs PalmOS apps, supposedly all of them and supposedly seamlessly. Little is known about how it works but if it's not too kludgy it should run unmodified on any ARM linux. It is not known what license it will be distributed under.<br />
<br />
Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.<br />
<br />
=== Q: A-t-il Java? ===<br />
R: Il l'aura peut-être, si vous nous aidez à le faire marcher. Les bons endroits pour se tenir informé :[http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] et [https://phoneme.dev.java.net/ PhoneME].<br />
<br />
=== Q: What are the relevant X11 details? ===<br />
<br />
A: See [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].<br />
<br />
=== Q: Openmoko marche-t-il sur d'autres matériels? ===<br />
<br />
Vous pouvez le faire marcher sur votre [[How_to_run_Openmoko_Apps_on_PC|PC]]. Ca devrait marcher sur [http://www.datenfreihafen.org/~stefan/weblog//archives/2007/02/#e2007-02-18T15_27_07.txt OpenEZX and HTC]. Ca marche sur [http://dominion.kabel.utwente.nl/koen/cms/openmoko-running-on-an-ipaq iPaq hx4700], sur un [http://hackndev.com/node/701 Palm TX] et sur [http://blog.mikeasoft.com/2007/07/01/openmoko-on-a-treo-650/ PalmOne's Treo 650].<br />
<br />
=== Q: What are the requirements to the hardware to run Openmoko? (Would it run on the IXI ogo?) ===<br />
<br />
=== Q: Why do you not build on top of the Maemo platform instead? ===<br />
<br />
While I can't speak for the Openmoko team, it's worth noting that maemo is fixed resolution only. That will, I've heard, change in the future, but it hasn't yet. Maemo's current layout is also optimized for wide screens, not tall narrow ones. Most third party maemo applications that are out there will need to be modified to work at different sizes. Finally, a number of the software components of the Nokia 770 and N800 are not open source. --gopi<br />
<br />
To add up on that, according to Nokia, Maemo is designed to bring the "Desktop" experience to an Internet Tablet. A lot of Desktop paradigms just won't work on a phone. However, we really share a lot of the base-technology (gtk, dbus, eds, gconf, to name a few) with Maemo, so we are definitely not a reinvent-the-wheel team.<br />
<br />
=== Q: Will it be possible to use popular VoIP applications such as Skype on the Openmoko platform? ===<br />
<br />
A: Perhaps. Hardware issues mean that it won't work well on the Neo1973. (the typical latency of GPRS is far too high). Also, Skype is a closed source application, which does not provide binaries that would be suitable to run on Openmoko. Skype's vendor could of course choose to provide binaries for Openmoko phones. However, many telephone providers' terms of service agreements preclude running VoIP over their baseline GSM service.<br />
<br />
=== Q: Same question for Instant Messaging applications such as MSN Messenger? ===<br />
<br />
A: Very probably. MSN is closed source and will only run where Microsoft wants you to run it. But there are many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [http://www.pidgin.im Pidgin, formerly called GAIM]. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.<br />
<br />
==Neo1973 niveau matériel== <br />
<br />
=== Q: Y a-t-il une description du [[:Category:Neo1973 Hardware | matériel du neo1973]] ? ===<br />
<br />
R: Voir [[:Category:Neo1973 Hardware | Neo1973 Hardware]] et [[Disassembling Neo1973]]<br />
<br />
=== Q: Quelles sont les dimensions? ===<br />
<br />
R: 120.7 x 62 x 18.5 mm, il tiendra dans une boite de conserve. (4.75 * 2.4 * 0.72 ")<br />
<br />
=== Q: Quel poid fera-t-il? ===<br />
<br />
R: 185g, (6.5 ounces).<br />
<br />
=== Q: A-t-il un appareil photo? ===<br />
<br />
R: Non, voir [[:Category:Neo1973 Hardware | Neo1973]] pour les détails de ce qu'il incluera (et la [[Wish List - Hardware|liste de souhait matériel]] pour ce que les gens veulent dans les versions futures.) Voir aussi [[FAQ#USB]].<br />
<br />
=== Q: What is the rationale behind the exclusion of WiFi? ===<br />
<br />
A: No suitable low power open source WiFi device was available when the [[Neo1973]] was designed. A closed source WiFi device would have been restrictive for developers and users alike. See also [[FAQ#USB]].<br />
<br />
See also:<br />
[[Sean Moss-Pultz]]'s [http://lists.openmoko.org/pipermail/community/2006-November/000050.html comment on this]<br />
<br />
[[Neo1973|Neo1973 GTA02]] will include WiFi.<br />
<br />
=== Q: A-t-il le Bluetooth? ===<br />
<br />
R: Oui!<br />
<br />
=== Q: Le recevra-t-on avec un stylet? ===<br />
<br />
R: Oui, mais il n'y aucun implacement pour le ranger dans le téléphone.<br />
<br />
=== Q: Où se trouvent les boutons ? ===<br />
<br />
Le bouton d'allumage et d'exctinction est un petit bouton circulaire, juste à coté du connecteur USB. [[Neo1973 Power Button|Bouton d'allumage du Neo1973]]<br />
Le bouton auxiliaire est un bouton rectangulaire dans le coin gauche en haut du téléphone. (sur les téléphones noirs il ressemble à un port InfrRouge). [[Neo1973 AUX Button|Bouton auxiliaire du Neo1973]]<br />
<br />
=== Q: Comment taper du texte? ===<br />
<br />
R: Utilisez le clavier visuel sur l'écran.<br />
<br />
R: Utilisez un clavier Bluetooth.<br />
<br />
R: Pour plus de méthodes et d'idées voir [[Wishlist:Text_Input|Attentes: claviers]].<br />
<br />
=== Q: Can I record calls and/or play audio files in calls? ===<br />
<br />
A: Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.<br />
<br />
=== Q: Quel est la durée de vie de la batterie? ===<br />
<br />
R: On ne sait pas pour l'instant, mais vous pouvez regarder [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|ces approximations]] pour une petite idée. Plus d'informations [[Neo1973 Battery|ici]].<br />
<br />
=== USB ===<br />
<br />
==== Q: What can I do with the USB port on the Neo1973? ====<br />
A: Charge the phone, communicate with it over USB-serial, or USB-networking.<br />
<br />
A: Plug external devices, such as wifi, cameras, or mass-storage devices in.<br />
<br />
==== Q: What can't I do with the USB? ====<br />
<br />
The USB on the neo has no power output. This means that you cannot use USB bus powered devices without some sort of powered hub or cable.<br />
This is due to the fact that adding a 5V power supply into the device would have added complexity, volume and cost.<br />
<br />
Many powered USB devices don't work without at least a nominal amount of 5v power from the USB bus. A few powered USB hubs will work without 5v power from the host, but most powered ones need to have simple electrical modifications done to work.<br />
<br />
==== Q: Why is only USB 1.1 provided? ====<br />
<br />
A: The processor has USB 1.1 built in. One with USB2 built in would have been more expensive.<br />
<br />
==== Q: Can the Neo charge and use devices on a USB hub at the same time? ====<br />
<br />
A: <br />
*When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.<br />
<br />
*If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)<br />
*This is because the host socket on USB hubs is not powered.<br />
<br />
FIC product development is looking into providing something that<br />
conveniently solves this problem.<br />
<br />
The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)<br />
<br />
One solution is a three headed cable.<br />
<br />
One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.<br />
<br />
The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.<br />
<br />
For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.<br />
<br />
==== Q: What are the details of the USB port on the [[Neo1973]]? How does it compare to USB On-The-Go? ====<br />
<br />
A: The [[Neo1973]] will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just<br />
a AB socket, but also electrical and software components which cannot be provide by the S3C2410.<br />
<br />
You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).<br />
<br />
=== Q: Are there any LEDs on the Neo 1973? ===<br />
<br />
A: The [[Neo1973]] v1 will have no LEDs besides the screen backlight.<br />
<br />
=== Q: Will a JTAG port be made available? ===<br />
<br />
A: The "Hacker's Lunchbox" in Advanced version will make this kind of stuff easy. <br />
<br />
There are [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connectors]] inside case in all versions and [[Debug Board|Debug Board v2]] (JTAG and serial console) in Advanced version. [[Connecting Neo1973 with Debug Board v2]] explains how to connect it to the phone.<br />
<br />
=== Q: What can we expect in future versions? ===<br />
<br />
A: A faster CPU, faster GSM (EDGE?) perhaps even powered USB port, USB2, wifi, and camera. No details have been released yet. More details of hardware upgrades should be available sometime in May. There will also be 5 more Openmoko devices - some not phones in the traditional sense - announced by FIC in September.<br />
<br />
==Networking/Connectivity==<br />
<br />
=== Q: What kind of connectivity? ===<br />
<br />
A: Tri-band GSM, GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR, USB in all versions. WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)<br />
<br />
=== Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ===<br />
<br />
A: Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].<br />
<br />
=== Q: What providers provide the GSM required for Neo1973? ===<br />
<br />
A: See [[Neo1973 compatible cellphone providers]]<br />
<br />
=== Q: Will Openmoko "Just Work" with Mac OS X? ===<br />
<br />
A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers. <br />
Not being a Mac OS X user, I don't know enough<br />
to summarize the discussion to answer this question. Can someone please fill in?<br />
<br />
A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the Openmoko.<br />
<br />
A: It is expected that (Bluetooth/UB) SyncML based interoperation for<br />
contacts and events can easily be achieved by a patch<br />
to the Apple iSync configuration tables.<br />
<br />
A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of<br />
PPC/x86/ARM universal binaries) on Openmoko devices: mySTEP.<br />
<br />
==Divers==<br />
<br />
=== Q: On the lists on lists.openmoko.org, should replies be added above or below the original text? ===<br />
<br />
A: Please reply UNDER post.<br />
<br />
=== Q: How can I find out if a question or topic has already been discussed on the mailing lists? ===<br />
<br />
A: By searching the mailing list archives. For example, using Google searches:<br />
<br />
site:openmoko.org text<br />
<br />
For example, to search for accelerometer:<br />
<br />
site:openmoko.org accelerometer<br />
<br />
If you only want to read the "official" mails from FIC people or from Openmoko people:<br />
<br />
site:openmoko.org text "at fic.com.tw"<br />
site:openmoko.org text "at openmoko.org"<br />
<br />
For example to search for "release date" from FIC people:<br />
<br />
site:openmoko.org "release date" "at fic.com.tw"<br />
<br />
Alternatively you can use the [http://www.google.com/coop/cse?cx=017507431580478583395%3Astsl7lhxzbc custom Openmoko search engine] which has been created using [http://www.google.com/coop/ Google Co-op].<br />
<br />
<br />
=== Q:Can I has some money for a Neo1973 ===<br />
<br />
A:No.<br />
<br />
[[Category:Information]]</div>Youshehttp://openmoko.org/wiki/FAQFAQ2008-08-09T17:32:51Z<p>Youshe: Languages better on top of page</p>
<hr />
<div>{{Languages|FAQ}}<br />
Frequently Asked Questions... with answers included!<br />
<br />
==Introduction== <br />
<br />
=== Q: What is Openmoko? What is the Neo 1973? What is the Neo Freerunner? ===<br />
A: Openmoko is a software platform and the world's first completely open mobile phone software stack. It is based on Linux and allows users and enthusiasts great freedom to customise their phone.<br />
* The [[Neo 1973]] is the first fully supported Openmoko phone. <br />
* The FIC [[Neo FreeRunner]] is the second Openmoko phone and is now available for sale!<br />
<br />
=== Q: I'm a ____ expert, can I join/help Openmoko? ===<br />
<br />
We would love to hear from you.<br />
<br />
* If you are interested in joining Openmoko as a software developer, please visit http://www.openmoko.com/contact-index.html and send us an e-mail. <br />
* Or register some your project at http://projects.openmoko.org/<br />
<br />
=== Q: When and where can I buy a [[Neo 1973]]? ===<br />
<br />
A: The OpenMoko Neo 1973 is now sold out (11 Feb 2008). You should get the better [[Neo FreeRunner]] instead!<br />
<br />
=== Q: Where can I buy a [[Neo FreeRunner]]? ===<br />
<br />
A: You can buy a Neo FreeRunner at [http://www.openmoko.com/ openmoko.com]. See [[Getting Openmoko]] for more information on buying the Neo FreeRunner.<br />
<br />
=== Q: What are the new features that the Neo FreeRunner has? ===<br />
<br />
It retains many good features from the Neo 1973 such as the very high resolution touch screen and integrated GPS unit.<br />
<br />
It adds the following features<br />
* WiFi - 802.11 b/g - for high speed internet<br />
* Faster processor operating at 400Mhz (up from 266Mhz) - for faster operation<br />
* * SMedia Glamo3362 Graphics Accelerator - for improved graphical performance<br />
* 2 3D Accelerometers - the phone applications will know which way the phone is oriented<br />
* 256MB Flash - larger memory to run bigger applications<br />
* LED's illuminating the 2 external buttons on the phone<br />
<br />
=== Q: How much? === <br />
<br />
A: If you buy directly from the Openmoko webshop you will pay $399 for the Neo FreeRunner, $99 for the debug board on [http://www.openmoko.com/ www.openmoko.com].<br />
<br />
=== Q: What can I do with the Neo1973? ===<br />
<br />
A: For long answer see [[Developer preview]]<br />
<br />
A: The Neo1973 is a Phase 1 phone and aimed at software developers only. It is not suitable for end users, it will have basic functionality as a touchscreen phone. Little else will work, software development will continue till mass market release. Here are one developer's thoughts about the possibilities [http://blog.syntaxpolice.org/isaac/technology/linuxPhones.html]<br />
<br />
Those interested should:<br />
<br />
* Know that there will be a device with faster cpu, gsm system etc in the spring of 2008.<br />
* Have fun hacking devices.<br />
* Be able to find their way through prototype software and hardware without much documentation.<br />
* Share the dream of a device powered by free software.<br />
* Not expect a consumer-level device.<br />
* Come up with new ideas for exploring the age of mobile computing.<br />
* Have $300.<br />
<br />
Ideally they also:<br />
<br />
* Can spot bugs and submit patches.<br />
* Love to cooperate with a community improving the software.<br />
<br />
=== Q: What can I do with the Neo Freerunner? ===<br />
<br />
A: The Neo Freerunner is the first phase 2 (mass release) phone from the Openmoko project and is designed for everyday use by end users and continued software development and improvements by the Openmoko team and the Openmoko community.<br />
<br />
A: The question is almost what can you NOT do with this phone - eventually there will be a huge range of free software applications allowing both end users and developers to get much more out of this phone than a standard "locked" mobile phone using features like the integrated GPS, bluetooth, wifi and accelerometers.<br />
<br />
=== Q: Do I need the Neo 1973 Advanced (or in due course the Neo Freerunner Advanced)? === <br />
<br />
End users or power users should buy the "base" unit.<br />
<br />
Software developers may wish to buy the "advanced" model.<br />
<br />
With Neo 1973 Base or Neo Freerunner Base you can do:<br />
* Kernel development.<br />
* Application development.<br />
* Updating u-boot (equivalent to PC BIOS) using a tested image.<br />
* Replace a non-booting kernel and/or rootfs using [[Dfu-util]].<br />
<br />
With Neo 1973 Advanced or Neo Freerunner Advanced you can additionally do:<br />
* U-boot development.<br />
* Use the kernel console.<br />
* Unbrick your device if you flash a wrong or non-working u-boot image.<br />
<br />
=== Q: I have a shipping related question === <br />
<br />
For Neo1973<br />
* See [[SH1_FAQ|Shipment 1 FAQ]].<br />
<br />
For FreeRunner<br />
* See [http://www.openmoko.com/ openmoko.com]<br />
<br />
=== Q: What does the [[Neo 1973]] look like? ===<br />
<br />
* See the original launch [[Artwork|artwork]]<br />
* Collected images from google [[http://images.google.co.uk/images?q=neo+1973&ie=UTF-8&oe=utf-8&rls=com.ubuntu:en-GB:official&client=firefox-a&um=1&sa=N&tab=wi]]<br />
<br />
=== Q: What does the [[Neo FreeRunner]] look like? ===<br />
<br />
* It uses the same case and dimensions as the Neo1973 (as announced at CES Jan08)<br />
<br />
=== Q: What else do I need to know? ===<br />
<br />
* Both Neo 1973 and Neo Freerunner are tri-band GSM phones. <br />
* The Neo Freerunner is expected to be offered in an 850/1800/1900MHz version for North America and an 900/1800/1900MHz version for the rest of the world. <br />
* The Neo1973 is an 900/1800/1900Mhz version only and may not work well in some rural parts of North America.<br />
<br />
=== Q: What are the benefits of an "open" phone over a "closed" phone ===<br />
<br />
A: In a conventional closed phone, the handset maker and the mobile network operator work together to provide a service to you that best suits their business model. The capabilities of a modern smartphone equipped with GPS, Wifi and bluetooth are amazing and the result is that many features are "locked down" because they do not suit the network operator. Up until now it has been difficult to buy a phone on which you have freedom to install sofware which is not controlled by the network operators - [[Openmoko]] changes that!<br />
<br />
A: A list of examples of "closed" behaviour has been started here - [[Problems of typical "closed" phones]]<br />
<br />
==Software==<br />
<br />
<br />
=== Q: Can the software do/connect to/... ===<br />
A: Reviews of the latest "bleeding edge" daily builds of the OpenMoko software stack can be seen [[Snapshot_review|here]]<br />
<br />
A: At the moment, the answer to many other questions is "no". The phone is at the moment a small linux box with a touchscreen, a working dialer and some prototype apps. Most do not function in any way that would be suitable for end-users. If you want to add a feature or application request, then look over the existing [[Applications]] and either add one, or add a feature request to the applications page.<br />
<br />
===What software is on the phone?===<br />
At the moment, almost no 'end-user' applications are present and working in a usable state.<br />
It is possible to make and receive calls in some software revisions, this frequently breaks though.<br />
<br />
====What software can be installed on the phone?====<br />
<br />
=== Q: Is there description and list of OpenMoko software? ===<br />
<br />
A: See [[OpenMoko]] and [[OpenmokoFramework]]<br />
<br />
=== Q: Is it completely free software/open source? ===<br />
<br />
A: User space GPS/[[Gpsd]] will use a binary plugin for [[:Category:Neo1973 Hardware#AGPS|Hammerhead AGPS]] and [[:Category:Neo1973 Hardware#GSM.2FGPRS|GSM modem]] is separate subsystem connected to S3C2410 UART1. <br />
<br />
There are legal reasons why it is not possible to provide Open Source software for GPS and GSM modules.<br />
<br />
Otherwise it is completely free software. See [[MokoMakefile]] and [[Development resources]].<br />
<br />
=== Q: How do I install and manage software on OpenMoko? ===<br />
<br />
A: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg<br />
<br />
=== Q: How can I compile programs for the Neo1973? ===<br />
<br />
A: See [[Toolchain]].<br />
<br />
=== Q: Is there an emulator available for OpenMoko? ===<br />
<br />
For a lot of testing and development work, you don't actually need emulation as you can run OpenMoko on a normal PC too. The emulators also aren't 100% accurate. That being said, there are several emulation options as described in the following.<br />
<br />
====QEMU====<br />
QEMU can now emulate the Neo1973 device. The [[MokoMakefile]] has support for automatically building, flashing, and running [[OpenMoko under QEMU|the Neo1973 emulator]].<br />
<br />
*Ubuntu users can follow the instructions in [[Automatic_emulation_in_Ubuntu]]<br />
<br />
*Users of other Linux distributions can try the following:<br />
:"make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.<br />
<br />
See [[Qemu]] for more advanced information on running OpenMoko in Qemu.<br />
<br />
====Xoo====<br />
Another is [http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most apps people will develop, since most don't need access to the gsm uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".<br />
<br />
Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:<br />
<br />
It's not really useable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.<br />
<br />
http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2<br />
<br />
Start with 'xoo --device /path/to/neo1973.xml'<br />
<br />
Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].<br />
<br />
====Xephyr====<br />
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):<br />
Xephyr -screen 480x640 -nolisten tcp -ac :1 &<br />
export DISPLAY=:1<br />
export LD_LIBRARY_PATH=/usr/local/lib<br />
matchbox-window-manager -display $DISPLAY -use_titlebar no \<br />
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \<br />
-use_cursor yes &<br />
matchbox-panel --geometry=480x44 --end-applets=clock &<br />
openmoko-footer &<br />
openmoko-taskmanager &<br />
<br />
=== Q: Where can I find some type of tutorial for a 'Hello, world' on OpenMoko? ===<br />
<br />
A: This should get you started:<br />
* [[Building_a_hello_world_application]]<br />
* http://www.gtk.org/documentation.html#Tutorials<br />
<br />
=== Q: Can PalmOS apps applications be ported to run on OpenMoko? ===<br />
<br />
A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux<br />
is decidedly non-trivial.<br />
<br />
PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.<br />
<br />
The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M6800 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.<br />
<br />
It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on OpenMoko, but this has to be considered a short-term bandaid rather than a long-term solution.<br />
<br />
The soon-to-be-released [http://www.palm.com/foleo/ Palm Foleo], which runs a Linux port developed by Palm Inc. independently of ALP, contains a PalmOS compatibility environment that runs PalmOS apps, supposedly all of them and supposedly seamlessly. Little is known about how it works but if it's not too kludgy it should run unmodified on any ARM linux. It is not known what license it will be distributed under.<br />
<br />
Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.<br />
<br />
=== Q: Does it have Java? ===<br />
A: It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].<br />
<br />
Project [[https://wiki.evolvis.org/jalimo/index.php/Jalimo Jalimo]] is a project aiming to provide a Java stack on mobile devices. This project supports OpenMoko.<br />
<br />
=== Q: What are the relevant X11 details? ===<br />
<br />
A: See [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].<br />
<br />
=== Q: Does OpenMoko run on any other hardware? ===<br />
<br />
You can run it on your [[How_to_run_OpenMoko_Apps_on_PC|PC]]. You may be able to run it on other [[OpenMoko-supported_hardware | mobile platforms]]<br />
<br />
<br />
<br />
=== Q: Why do you not build on top of the Maemo platform instead? ===<br />
<br />
While I can't speak for the OpenMoko team, it's worth noting that maemo is fixed resolution only. That will, I've heard, change in the future, but it hasn't yet. Maemo's current layout is also optimized for wide screens, not tall narrow ones. Most third party maemo applications that are out there will need to be modified to work at different sizes. Finally, a number of the software components of the Nokia 770 and N800 are not open source. --gopi<br />
<br />
To add up on that, according to Nokia, Maemo is designed to bring the "Desktop" experience to an Internet Tablet. A lot of Desktop paradigms just won't work on a phone. However, we really share a lot of the base-technology (gtk, dbus, eds, gconf, to name a few) with Maemo, so we are definitely not a reinvent-the-wheel team.<br />
<br />
=== Q: Will it be possible to use popular VoIP applications such as Skype on the Openmoko platform? ===<br />
<br />
A: Answer for the [[Neo1973]] - Perhaps. Hardware issues mean that it won't work well on the Neo1973. (the typical latency of GPRS is far too high). Also, Skype is a non-free software and binaries are not provided that would be suitable to run on a Neo. Skype's vendor could of course choose to provide binaries for Openmoko phones. However, this would not be desirable by Openmoko since it removes freedoms from the end-user. <br />
<br />
A: Answer for the [[Neo FreeRunner]]. Since it has WiFi the FreeRunner should be a good platform for VOIP use. <br />
<br />
In either case please check for softphone apps ported to the Openmoko distribution at the [http://projects.openmoko.org/ projects] page. We need to focus efforts on free software. Not convincing non-free software companies to release binaries for our Neos.<br />
<br />
=== Q: Same question for Instant Messaging applications such as MSN Messenger? ===<br />
<br />
A: Very probably. MSN is closed source and will only run where Microsoft wants you to run it. But there are many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [http://www.pidgin.im Pidgin, formerly called GAIM]. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.<br />
<br />
==Neo1973 Hardware== <br />
<br />
=== Q: Is there description of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] ? ===<br />
<br />
A: See page [[Neo1973_Hardware]] and category [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]<br />
<br />
=== Q: Does it have a camera? ===<br />
<br />
A: No, see [[:Category:Neo1973 Hardware | Neo1973]] for details on what it does include (and [[Wish List - Hardware]] for what some want in the future.) See also [[FAQ#USB]].<br />
<br />
=== Q: Does it have Wifi? ===<br />
<br />
A: The currently available [[Neo1973]] does not have WiFi. There was no suitable Wifi device available when it was designed. The next version will have WiFi. See also [[FAQ#USB]].<br />
<br />
=== Q: Does it have bluetooth? ===<br />
<br />
A: Yes! Bluetooth 2.0.<br />
<br />
=== Q: Does it come with a stylus? ===<br />
<br />
A: Yes, but there's no holder for it on the phone.<br />
<br />
=== Q: Where are the buttons? ===<br />
<br />
[[Neo1973 Power Button|The power button]] is a small circular button, just next to the USB connector. <br />
[[Neo1973 AUX Button|The Auxiliary button]] is a rectangular button on the top left of the edge of the phone. (on black phones it looks just like an IRDA port).<br />
<br />
=== Q: How do I input text? ===<br />
<br />
A: Use provided keyboard app.<br />
<br />
A: Use Bluetooth keyboard.<br />
<br />
A: For more methods and ideas see [[Wishlist:Text_Input]].<br />
<br />
=== Q: Can I record calls and/or play audio files in calls? ===<br />
<br />
A: Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.<br />
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. [[Neo1973_Audio_Subsystem|Neo1973 Audio Subsystem]]<br />
<br />
=== Q: What is the battery life? ===<br />
<br />
A: There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].<br />
<br />
=== USB ===<br />
<br />
==== Q: What can I do with the USB port on the Neo1973? ====<br />
A: Charge the phone, communicate with it over USB-serial, or USB-networking.<br />
<br />
A: Plug external devices, such as wifi, cameras, or mass-storage devices in. The "Mass Market" version of the phone will have wifi integrated.<br />
<br />
==== Q: What can't I do with the USB? ====<br />
<br />
The only limitation on current hardware seems to be no usb 2.0 support, which means slower communication with 2.0 devices.<br />
<br />
==== Q: Why is only USB 1.1 provided? ====<br />
<br />
A: The processor has USB 1.1 built in. One with USB2 built in would have been more expensive.<br />
<br />
==== Q: Can the Neo charge and use devices on a USB hub at the same time? ====<br />
<br />
A: <br />
*When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.<br />
<br />
*If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)<br />
*This is because the host socket on USB hubs is not powered.<br />
<br />
FIC product development is looking into providing something that<br />
conveniently solves this problem.<br />
<br />
The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)<br />
<br />
One solution is a three headed cable.<br />
<br />
One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.<br />
<br />
The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.<br />
<br />
For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.<br />
<br />
==== Q: What are the details of the USB port on the [[Neo1973]]? How does it compare to USB On-The-Go? ====<br />
<br />
A: The [[Neo1973]] will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just<br />
an AB socket, but also electrical and software components which cannot be provide by the S3C2410.<br />
<br />
You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).<br />
<br />
=== Q: Are there any LEDs on the Neo 1973? ===<br />
<br />
A: The [[Neo1973]] P1/P2 will have no LEDs besides the screen backlight.<br />
<br />
=== Q: Will a JTAG port be made available? ===<br />
<br />
A: Included with purchase of The "Hacker's Lunchbox" (Advanced version).<br />
<br />
There are [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connectors]] inside case in all versions and [[Debug Board|Debug Board v2]] (JTAG and serial console) in Advanced version. [[Connecting Neo1973 with Debug Board v2]] explains how to connect it to the phone.<br />
<br />
=== Q: Will the JTAG interface that comes with GTA01 be compatible with GTA02? ===<br />
<br />
A: Yes<br />
<br />
=== Q: What can we expect in future versions? ===<br />
<br />
A: A faster CPU, faster GSM (EDGE?) perhaps even powered USB port, USB2, wifi, and camera. No details have been released yet. More details of hardware upgrades should be available sometime in May. There will also be 5 more OpenMoko devices - some not phones in the traditional sense - announced by FIC in September.<br />
<br />
=== Q: Are microSDHC-cards like this[1] supported? ===<br />
<br />
[1] http://www.amazon.de/Secure-Digital-Card-microSDHC-8192MB/dp/B0019XICD4/ref=pd_sbs_pc_15<br />
<br />
==Networking/Connectivity==<br />
<br />
=== Q: What kind of connectivity? ===<br />
<br />
A: Tri-band GSM (commonly known as "European tri-band", 900/1800/1900 MHz), GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR, USB in all versions. WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)<br />
<br />
=== Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ===<br />
<br />
A: Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].<br />
<br />
=== Q: What providers provide the GSM required for Neo1973? ===<br />
<br />
A: See [[Neo1973 compatible cellphone providers]]<br />
<br />
=== Q: Will OpenMoko "Just Work" with Mac OS X? ===<br />
<br />
A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers. <br />
Not being a Mac OS X user, I don't know enough<br />
to summarize the discussion to answer this question. Can someone please fill in?<br />
<br />
A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the OpenMoko.<br />
<br />
A: It is expected that (Bluetooth/UB) SyncML based interoperation for<br />
contacts and events can easily be achieved by a patch<br />
to the Apple iSync configuration tables.<br />
<br />
A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of<br />
PPC/x86/ARM universal binaries) on OpenMoko devices: mySTEP.<br />
<br />
==Misc==<br />
<br />
=== Q: On the lists on lists.openmoko.org, should replies be added above or below the original text? ===<br />
<br />
A: Please reply UNDER post.<br />
<br />
=== Q: How can I find out if a question or topic has already been discussed on the mailing lists? ===<br />
<br />
A: By searching the mailing list archives. For example, using Google searches:<br />
<br />
site:openmoko.org text<br />
<br />
For example, to search for accelerometer:<br />
<br />
site:openmoko.org accelerometer<br />
<br />
If you only want to read the "official" mails from FIC people or from OpenMoko people:<br />
<br />
site:openmoko.org text "at fic.com.tw"<br />
site:openmoko.org text "at openmoko.org"<br />
<br />
For example to search for "release date" from FIC people:<br />
<br />
site:openmoko.org "release date" "at fic.com.tw"<br />
<br />
Alternatively you can use the [http://www.google.com/coop/cse?cx=018430699993342716089%3Aszsaurhronw custom OpenMoko search engine] that is using [http://www.google.com/coop/ Google Co-op].<br />
<br />
=== Q: how many dead pixels may the LCM have before calling it defect? ===<br />
<br />
A: the answer for the display used in GTA01 and GTA02 is '2'<br />
<br />
=Historical=<br />
The Neo1973 was last available in Febuary 2008. See [Ne<br />
<br />
[[Category:Information]]<br />
[[Category:FAQ]]</div>Youshehttp://openmoko.org/wiki/Why_OpenmokoWhy Openmoko2008-08-09T17:25:58Z<p>Youshe: </p>
<hr />
<div>{{Languages|Why_Openmoko}}<br />
<br />
This article discusses the pros and cons of various operating systems for the mobile platform, and tells us why Openmoko is the true ‘open’ platform. There are many mobile platforms that exist on this planet today. The situation is very similar to the desktop segment, where we have operating systems like Linux, Windows and a few others. To me, the fact that Linux is an open source model makes it a much better OS. We also have great mobile operating systems like Symbian, Windows Mobile Platform and Linux. But none of these are really ‘open’. Surprised to see Linux in this list? Linux as a mobile OS comes in different shapes and sizes that are not very compatible with each other, as there are many different implementations of the platform. There are no common APIs available for developers to build on top of. Examples include implementations from Motorola and MontaVista. At least, this is not the case with proprietary OSs such as Symbian and Windows Mobile. They provide abundant अपिस to aid third-party programmers to build on their platform. Let us now set aside all this for a while and concentrate on a Linux-based mobile platform project called Openmoko—a project that combines the true essence of open source with a rich application-programming interface. Openmoko is a true conversion of the desktop Linux into mobile Linux, which doesn’t bring in any non-standard or hidden aspects. It was built using standard X-server, GTK, ALSA, Dbus and so on. The beauty is that even the hardware platform is as open as the software platform. Openmoko makes use of a standard platform to make the mobile environment complete. Even the circuit-board hackers will find Openmoko a dream come true!<br />
<br />
==What is wrong with the others? ==<br />
<br />
Let’s now take a look at what is seriously wrong.<br />
<br />
===Symbian OS===<br />
<br />
First up is the Symbian OS, considered the Windows of the mobile world. More than 75 percent of the smart phones sold today, run Symbian, and it’s perhaps the most developed mobile operating system, backed by such industry leaders as Nokia, Motorola, Sony and Lenovo. But there are a few things I don’t like about Symbian, which I’m listing below.<br />
<br />
*'''A proprietary OS:''' Symbian is a closed source OS developed by Symbian Ltd, and perhaps the worst thing about it is that it uses open programs like GCC, Java, Perl and many others in its SDK, but doesn’t share its code base or support any open source OS for its application development.<br />
<br />
*'''A restricted development environment:''' Symbian only supports Windows for application development. There is no official SDK that can be used with Linux or Mac OSX. What is ironic is that most of Symbian’s SDK components will fail without the supporting open source programs.<br />
<br />
*'''Poor backward compatibility:''' Every new version of the OS breaks the code. You can’t just recompile the code and run the application on a new platform. You need to re-write the whole application to support the code.<br />
<br />
*'''High-end systems requirements:''' Symbian phones require a pretty decent hardware configuration to run properly. Even if you do have that, you may come across messages like “Out of Memory”. I am sure that many of our readers using Nokia smart phones are already aware of this.<br />
<br />
*'''Difficult to program:''' Even though it offers a rich set of APIs, these are difficult to program. You may say that Symbian supports many programming languages, but remember — if you really want to program, you must know that Symbian C++ is very different from the standard C++, and hence has a very steep learning curve.<br />
<br />
*'''Confused UI platforms:''' Symbian uses two confusing and mutually incompatible UI platforms— namely, S60 (formerly Series 60) and User Interface Quartz (UIQ). For developers, this means that even though you are developing for Symbian, you need to learn UI specific details in order to be up and running.<br />
<br />
*'''Poor developer support:''' Starting with Symbian 9, the company has started punishing third-party developers. Most of the phone features are open only to subscribers of Symbian Signed. If you are not a member of the Symbian Signed programme, then you won’t be able to make use of many core features of the OS.<br />
<br />
*'''Version lock:''' The OS doesn’t support OS upgradation—if your machine has got Symbian 9.1, it will remain as it is as long as you use it. You won’t be able to upgrade it to a later version of the same OS. So you are bound to live in the Stone Age unless you spend a fortune on getting a new device with a newer OS.<br />
<br />
*'''Symbian is a mobile-only OS:''' You can’t use your existing skills to build on it. Or, in other words, you can’t use your Symbian skills anywhere else.<br />
<br />
===Windows Mobile===<br />
<br />
Considering Symbian drawbacks, Symbian is not exactly like Windows on the desktop, even though it is doing quite well. Windows is better than Symbian in some ways. It has got better developer support and has a plethora of developer documentation available. Visual Studio is an excellent IDE for it. But there are a few things I don’t like about Windows Mobile too.<br />
<br />
*'''Microsoft vendor lock:''' Nothing is worse than a vendor lock-in, where the keys of the locks are with Microsoft.<br />
*'''Closed source:''' I don’t need to stress on this, do I?<br />
*'''Microsoft’s partiality:''' When it comes to a Microsoft product, there is always a reasonable amount of partiality. One example is in Windows Mobile 6, where some of the improvements to email and the calendar application require that you have Exchange Server 2007. The situation is exactly like that on the desktop, where you can’t have DX 10 if you don’t have Vista. Remember all those anti-trust cases that Microsoft is facing?<br />
*'''Poor API support:''' Not all the Windows APIs are available for third party use. You may need to sign an NDA with Microsoft before you want to fully unleash the OS’s potential.<br />
<br />
===iPhone===<br />
Apple's iPhone is very popular, we must take that into consideration as well. iPhone is not exactly a mobile application platform – rather, it is a product name. And, unfortunately, as of today, there is nothing much in store for the developers and end users. Let’s list the disadvantages here as well:<br />
<br />
* '''Apple’s insane vendor lock:''' This phone is locked in to Apple and the cellular company, and you as the user, end up paying both.<br />
* '''No third-party application development support:''' I end my argument with that!<br />
<br />
==Why Openmoko is the best==<br />
Linux is the best way to program. All that still stands true, as Openmoko is all about programming on Linux itself. And here’s why I think so:<br />
<br />
* '''Open source:''' It is truly open source—not only in terms of software, but also in terms of hardware. You get to see all the nuts and bolts behind your excellent phone.<br />
* '''Built from open source:''' Openmoko is an amazing collection of already popular open source programs to build a mobile development platform.<br />
* '''Cross-platform development:''' Moving forward, Openmoko SDK will support Windows and Mac too, thus giving you the option to develop on your choice of platform.<br />
* '''Easy application development:''' Since it makes use of popular technologies, it’s pretty easy to get up and running with Openmoko in a very short period of time. All Linux programmers will feel at home, as Openmoko makes use of popular open source components like GTK, X server, ALSA and so on.<br />
* '''Low on hardware requirements:''' It doesn’t require a very high-end configuration to run on.<br />
* '''Great developer support:''' Even though the project is in its infancy, it already has got great community support. Apart from this, all the components used in building Openmoko have their own communities. So, there may already be someone to help you out.<br />
* '''A very rich API:''' OpenMoko has got a very rich set of APIs. A few have been developed exclusively for OpenMoko, while the others are simply derived from other projects. OpenMoko enables you to use your existing skill set to create the phone applications that you want to.<br />
<br />
==The Openmoko Architecture==<br />
The Openmoko architecture is simple, yet very powerful. Most of it is based on already-available open source technologies. However, new technologies have also been developed exclusively for the platform. Openmoko consists of the following major components:<br />
[[Image:Software1.jpg]]<br />
<br />
* '''Linux kernel 2.6 and associated device drivers:''' The project makes use of the vanilla kernel 2.6 series, patched against OpenMoko-specific patches. The patch set includes additional support for various embedded devices like USB, SD, touch screen, and communication drivers. All these drivers reside in the kernel space, and are loaded at boot time.<br />
* '''Linux Core (or system) services:'''<br />
<br />
** '''udev:''' It acts as the device manger and maintains all the device nodes in a pseudo /dev filesystem. udev provides a standard way for device components to interact.<br />
** '''blueZ:''' It is the official LinuxBluetooth stack that is responsible for all Bluetooth related activities in Openmoko.<br />
** '''Dbus:''' This provides an IPC (inter-process communication) framework. In other words, Dbus allows applications to talk to each other.<br />
** '''GSM:''' It consists of GSM (the core GSM module), GSMd (a daemon to manage the GSM backend) and libgsm (an API to communicate with the GSM subsystem).<br />
** '''GPS:''' It consists of GPS (a core GPS module) and GPSd (a daemon to manage the GPS backend).<br />
<br />
* '''The user interface (UI)'''<br />
**'''kdrive:''' It is the thin X server for embedded platforms, which runs directly on a frame-buffer device and supports OpenGL.<br />
**'''matchbox:''' It is a window manager for embedded platforms. Matchbox has been very popular with its recent adoption in Nokia’s Linux tablet and the One Laptop Per Child project.<br />
**'''GTK:''' This cross-platform widget toolkit is popular due to its truly open source nature and wide cross-platform support. GTK sits behind the popular desktop environment GNOME. UPDATE: Qt is now supported widget.<br />
**'''ALSA:''' The Advanced Linux Sound Architecture (ALSA) provides the audio functionality. ALSA is already very popular in Linux systems and is now part of the standard kernel.<br />
**'''Qtopia:''' It is the robust and commercial-grade mobile phone and PDA platform from Trolltech, and arguably much more than just a GUI toolkit.<br />
* '''The application framework:'''<br />
**'''Core (libmokocore):''' This provides the core functionality to the framework, such as the switching device, reading/ writing data, application-toapplication signalling, etc. It makes use of the Dbus and Gconf packages.<br />
**'''.Net (libmokonet):''' It provides the core networking functionality to the framework. It makes use of libgsm, bluez-lib and libgps.<br />
**'''UI (libmokoui):''' It provides the UI programming capabilities to the platform and makes use of GTK and ALSA (for applications interacting with audio devices). The standard GTK has been customised to provide a rich mobile application-development experience.<br />
**'''PIM (libmokopim):''' Provides the core PIM (personal information management) capabilities. It makes use of the embedded Evolution data server.<br />
* '''Applications:'''<br />
**'''X11 applications:''' Standard X11 applications linked to libX11.<br />
**'''Finger applications:''' Includes the dialler, menu, media player, etc.<br />
**'''Stylus applications:''' Includes contacts, messages, search applications, etc.<br />
**'''Third-party applications:''' Various heavy-duty applications like Web browsers, instant messaging applications, etc.<br />
<br />
Subsequent to this quick introduction to the upcoming Openmoko platform, in forthcoming articles I’ll show you how to build and run OpenMoko applications. The experience is like hacking the world’s best phone environment at your workbench—and yes, nobody is going to sue you! Dont forget to post in your comments at kunaldeo at gmail.com<br />
<br />
--[[User:Kunaldeo|Kunaldeo]] 10:54, 30 June 2008 (UTC)<br />
<br />
[[category:Distributions]]</div>Youshehttp://openmoko.org/wiki/Why_OpenmokoWhy Openmoko2008-08-09T17:25:06Z<p>Youshe: Language</p>
<hr />
<div>{{Languages|Main Page}}<br />
<br />
This article discusses the pros and cons of various operating systems for the mobile platform, and tells us why Openmoko is the true ‘open’ platform. There are many mobile platforms that exist on this planet today. The situation is very similar to the desktop segment, where we have operating systems like Linux, Windows and a few others. To me, the fact that Linux is an open source model makes it a much better OS. We also have great mobile operating systems like Symbian, Windows Mobile Platform and Linux. But none of these are really ‘open’. Surprised to see Linux in this list? Linux as a mobile OS comes in different shapes and sizes that are not very compatible with each other, as there are many different implementations of the platform. There are no common APIs available for developers to build on top of. Examples include implementations from Motorola and MontaVista. At least, this is not the case with proprietary OSs such as Symbian and Windows Mobile. They provide abundant अपिस to aid third-party programmers to build on their platform. Let us now set aside all this for a while and concentrate on a Linux-based mobile platform project called Openmoko—a project that combines the true essence of open source with a rich application-programming interface. Openmoko is a true conversion of the desktop Linux into mobile Linux, which doesn’t bring in any non-standard or hidden aspects. It was built using standard X-server, GTK, ALSA, Dbus and so on. The beauty is that even the hardware platform is as open as the software platform. Openmoko makes use of a standard platform to make the mobile environment complete. Even the circuit-board hackers will find Openmoko a dream come true!<br />
<br />
==What is wrong with the others? ==<br />
<br />
Let’s now take a look at what is seriously wrong.<br />
<br />
===Symbian OS===<br />
<br />
First up is the Symbian OS, considered the Windows of the mobile world. More than 75 percent of the smart phones sold today, run Symbian, and it’s perhaps the most developed mobile operating system, backed by such industry leaders as Nokia, Motorola, Sony and Lenovo. But there are a few things I don’t like about Symbian, which I’m listing below.<br />
<br />
*'''A proprietary OS:''' Symbian is a closed source OS developed by Symbian Ltd, and perhaps the worst thing about it is that it uses open programs like GCC, Java, Perl and many others in its SDK, but doesn’t share its code base or support any open source OS for its application development.<br />
<br />
*'''A restricted development environment:''' Symbian only supports Windows for application development. There is no official SDK that can be used with Linux or Mac OSX. What is ironic is that most of Symbian’s SDK components will fail without the supporting open source programs.<br />
<br />
*'''Poor backward compatibility:''' Every new version of the OS breaks the code. You can’t just recompile the code and run the application on a new platform. You need to re-write the whole application to support the code.<br />
<br />
*'''High-end systems requirements:''' Symbian phones require a pretty decent hardware configuration to run properly. Even if you do have that, you may come across messages like “Out of Memory”. I am sure that many of our readers using Nokia smart phones are already aware of this.<br />
<br />
*'''Difficult to program:''' Even though it offers a rich set of APIs, these are difficult to program. You may say that Symbian supports many programming languages, but remember — if you really want to program, you must know that Symbian C++ is very different from the standard C++, and hence has a very steep learning curve.<br />
<br />
*'''Confused UI platforms:''' Symbian uses two confusing and mutually incompatible UI platforms— namely, S60 (formerly Series 60) and User Interface Quartz (UIQ). For developers, this means that even though you are developing for Symbian, you need to learn UI specific details in order to be up and running.<br />
<br />
*'''Poor developer support:''' Starting with Symbian 9, the company has started punishing third-party developers. Most of the phone features are open only to subscribers of Symbian Signed. If you are not a member of the Symbian Signed programme, then you won’t be able to make use of many core features of the OS.<br />
<br />
*'''Version lock:''' The OS doesn’t support OS upgradation—if your machine has got Symbian 9.1, it will remain as it is as long as you use it. You won’t be able to upgrade it to a later version of the same OS. So you are bound to live in the Stone Age unless you spend a fortune on getting a new device with a newer OS.<br />
<br />
*'''Symbian is a mobile-only OS:''' You can’t use your existing skills to build on it. Or, in other words, you can’t use your Symbian skills anywhere else.<br />
<br />
===Windows Mobile===<br />
<br />
Considering Symbian drawbacks, Symbian is not exactly like Windows on the desktop, even though it is doing quite well. Windows is better than Symbian in some ways. It has got better developer support and has a plethora of developer documentation available. Visual Studio is an excellent IDE for it. But there are a few things I don’t like about Windows Mobile too.<br />
<br />
*'''Microsoft vendor lock:''' Nothing is worse than a vendor lock-in, where the keys of the locks are with Microsoft.<br />
*'''Closed source:''' I don’t need to stress on this, do I?<br />
*'''Microsoft’s partiality:''' When it comes to a Microsoft product, there is always a reasonable amount of partiality. One example is in Windows Mobile 6, where some of the improvements to email and the calendar application require that you have Exchange Server 2007. The situation is exactly like that on the desktop, where you can’t have DX 10 if you don’t have Vista. Remember all those anti-trust cases that Microsoft is facing?<br />
*'''Poor API support:''' Not all the Windows APIs are available for third party use. You may need to sign an NDA with Microsoft before you want to fully unleash the OS’s potential.<br />
<br />
===iPhone===<br />
Apple's iPhone is very popular, we must take that into consideration as well. iPhone is not exactly a mobile application platform – rather, it is a product name. And, unfortunately, as of today, there is nothing much in store for the developers and end users. Let’s list the disadvantages here as well:<br />
<br />
* '''Apple’s insane vendor lock:''' This phone is locked in to Apple and the cellular company, and you as the user, end up paying both.<br />
* '''No third-party application development support:''' I end my argument with that!<br />
<br />
==Why Openmoko is the best==<br />
Linux is the best way to program. All that still stands true, as Openmoko is all about programming on Linux itself. And here’s why I think so:<br />
<br />
* '''Open source:''' It is truly open source—not only in terms of software, but also in terms of hardware. You get to see all the nuts and bolts behind your excellent phone.<br />
* '''Built from open source:''' Openmoko is an amazing collection of already popular open source programs to build a mobile development platform.<br />
* '''Cross-platform development:''' Moving forward, Openmoko SDK will support Windows and Mac too, thus giving you the option to develop on your choice of platform.<br />
* '''Easy application development:''' Since it makes use of popular technologies, it’s pretty easy to get up and running with Openmoko in a very short period of time. All Linux programmers will feel at home, as Openmoko makes use of popular open source components like GTK, X server, ALSA and so on.<br />
* '''Low on hardware requirements:''' It doesn’t require a very high-end configuration to run on.<br />
* '''Great developer support:''' Even though the project is in its infancy, it already has got great community support. Apart from this, all the components used in building Openmoko have their own communities. So, there may already be someone to help you out.<br />
* '''A very rich API:''' OpenMoko has got a very rich set of APIs. A few have been developed exclusively for OpenMoko, while the others are simply derived from other projects. OpenMoko enables you to use your existing skill set to create the phone applications that you want to.<br />
<br />
==The Openmoko Architecture==<br />
The Openmoko architecture is simple, yet very powerful. Most of it is based on already-available open source technologies. However, new technologies have also been developed exclusively for the platform. Openmoko consists of the following major components:<br />
[[Image:Software1.jpg]]<br />
<br />
* '''Linux kernel 2.6 and associated device drivers:''' The project makes use of the vanilla kernel 2.6 series, patched against OpenMoko-specific patches. The patch set includes additional support for various embedded devices like USB, SD, touch screen, and communication drivers. All these drivers reside in the kernel space, and are loaded at boot time.<br />
* '''Linux Core (or system) services:'''<br />
<br />
** '''udev:''' It acts as the device manger and maintains all the device nodes in a pseudo /dev filesystem. udev provides a standard way for device components to interact.<br />
** '''blueZ:''' It is the official LinuxBluetooth stack that is responsible for all Bluetooth related activities in Openmoko.<br />
** '''Dbus:''' This provides an IPC (inter-process communication) framework. In other words, Dbus allows applications to talk to each other.<br />
** '''GSM:''' It consists of GSM (the core GSM module), GSMd (a daemon to manage the GSM backend) and libgsm (an API to communicate with the GSM subsystem).<br />
** '''GPS:''' It consists of GPS (a core GPS module) and GPSd (a daemon to manage the GPS backend).<br />
<br />
* '''The user interface (UI)'''<br />
**'''kdrive:''' It is the thin X server for embedded platforms, which runs directly on a frame-buffer device and supports OpenGL.<br />
**'''matchbox:''' It is a window manager for embedded platforms. Matchbox has been very popular with its recent adoption in Nokia’s Linux tablet and the One Laptop Per Child project.<br />
**'''GTK:''' This cross-platform widget toolkit is popular due to its truly open source nature and wide cross-platform support. GTK sits behind the popular desktop environment GNOME. UPDATE: Qt is now supported widget.<br />
**'''ALSA:''' The Advanced Linux Sound Architecture (ALSA) provides the audio functionality. ALSA is already very popular in Linux systems and is now part of the standard kernel.<br />
**'''Qtopia:''' It is the robust and commercial-grade mobile phone and PDA platform from Trolltech, and arguably much more than just a GUI toolkit.<br />
* '''The application framework:'''<br />
**'''Core (libmokocore):''' This provides the core functionality to the framework, such as the switching device, reading/ writing data, application-toapplication signalling, etc. It makes use of the Dbus and Gconf packages.<br />
**'''.Net (libmokonet):''' It provides the core networking functionality to the framework. It makes use of libgsm, bluez-lib and libgps.<br />
**'''UI (libmokoui):''' It provides the UI programming capabilities to the platform and makes use of GTK and ALSA (for applications interacting with audio devices). The standard GTK has been customised to provide a rich mobile application-development experience.<br />
**'''PIM (libmokopim):''' Provides the core PIM (personal information management) capabilities. It makes use of the embedded Evolution data server.<br />
* '''Applications:'''<br />
**'''X11 applications:''' Standard X11 applications linked to libX11.<br />
**'''Finger applications:''' Includes the dialler, menu, media player, etc.<br />
**'''Stylus applications:''' Includes contacts, messages, search applications, etc.<br />
**'''Third-party applications:''' Various heavy-duty applications like Web browsers, instant messaging applications, etc.<br />
<br />
Subsequent to this quick introduction to the upcoming Openmoko platform, in forthcoming articles I’ll show you how to build and run OpenMoko applications. The experience is like hacking the world’s best phone environment at your workbench—and yes, nobody is going to sue you! Dont forget to post in your comments at kunaldeo at gmail.com<br />
<br />
--[[User:Kunaldeo|Kunaldeo]] 10:54, 30 June 2008 (UTC)<br />
<br />
[[category:Distributions]]</div>Youshehttp://openmoko.org/wiki/DistributionsDistributions2008-08-09T17:19:33Z<p>Youshe: Languages</p>
<hr />
<div>{{Languages|Distributions}}<br />
<br />
{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold" <br />
|<font color=white>Distributions</font><br />
|-<br />
! style='background-color:#333333;color:#FFFFFF'|<br />
<div align=left><br />
* <font color='#BBBBBB'>Openmoko (official)</font><br />
** [[Om 2008.8]]<br />
** [[Om 2007.2]]<br />
** [[OpenmokoFramework|FSO]]<br />
* <font color='#BBBBBB'>Community</font><br />
** [[SHR]]<br />
* <font color='#BBBBBB'>Other</font><br />
** [[Qtopia]]<br />
** [[Debian]]<br />
</div><br />
|-<br />
|}<noinclude>[[Category:Templates]]</noinclude><br />
<br />
Openmoko distributions are designed to run on various mobile devices, with the primary aim of Openmoko Inc.'s [[Neo 1973]] and [[Neo FreeRunner]] phones. They are similar to Linux distributions; complete operating systems with user applications. You can install any of them on your phone or even have a multiboot system with two distributions installed. <br />
<br />
While the Openmoko distributions will run on [[Supported devices|other mobile devices]] too, some other software distributions will also run on the Openmoko Inc. phones (see below). <br />
<br />
For downloads see [[Latest Images]], for installation instructions see [[Flashing the Neo FreeRunner]].<br />
<br />
== About distributions ==<br />
<br />
To be technically precise, 2007.2, 2008.8, FSO and SHR of these are not directly independent distributions, but different 'release targets'. They are built out of different branches of the [[OpenEmbedded]] metadistribution source tree, e.g. 2007.2 and 2008.8 are to each other like Ubuntu Gutsy is to Kubuntu Hardy. <br />
<br />
One should only use feeds from packages of the same source-branch, else 'stuff will break', similar to like using .debs from Hardy on a Gutsy base system. Also note that there is NO supported upgrade path between these at the moment, thus updating by changing the feeds will most likely end in broken packages or even a unbootable system. Thus please always use [[dfu-util]] to switch between the different 'distributions' for now or install them in a dual-boot setup (e.g. via sdcard or NFS).<br />
<br />
== Openmoko Inc. driven release targets ==<br />
<br />
=== Om 2007.2 (GTK) ===<br />
<br />
[[Om 2007.2]] is for people who are familiar with the [http://www.gnome.org/mobile/ GNOME Mobile] initiative and who want to write applications that run on multiple devices running (parts of) GNOME Mobile. This includes Maemo, which runs on the Nokia Internet Tablets. The strength of the GTK+ stack is a UI and programming environment similar to what you run on your Linux desktop, if you’re into GNOME. The GTK+ has PIM applications based on the Evolution Data Server and runs the gsmd phone server. Although you can use them, the applications are still pretty rough und unfinished. Some people have problems with the stability of the phone server.<br />
<br />
* [[Om 2007.2]]<br />
* Availabilty: [http://buildhost.openmoko.org/daily/ Official Buildhost] and [[MokoMakefile]] support for development builds<br />
* Download: [http://buildhost.openmoko.org/daily/freerunner/ Releases are labeled "openmoko-devel-image" ]<br />
* Several videos of this stack by [http://uk.youtube.com/user/freeyourphone Youtube user freeyourphone] and [http://uk.youtube.com/watch?v=U05kZfURPig&NR=1 video review by BVB Tech]<br />
<br />
This is the base-system which is installed on Freerunner when it leaves the factory.<br />
<br />
2007.2 development driven by openmoko inc. has basically stopped and resources are allocated in favor of 2008.8, while the community currently does the effort to 'rescue' the 2007.2 telephony apps and pull them to the future middleware from FSO (see SHR).<br />
thus patches are still welcome, especially if they help development of SHR.<br />
<br />
=== Om 2008.8 (ASU, April/August Software Update) ===<br />
<br />
Om 2008.8 has been started to integrate the [http://trolltech.com/products/qtopia Qtopia] stack - on X11 - with a new set of graphically pleasing applications based on the Enlightenment Foundation Libraries. ASU is the internal name and is known as Om 2008.8 upon its release on August 8, 2008. Qtopia is a more mature product than the GNOME Mobile stack and you can expect all the standard feature phone applications to work in a solid way. It uses the Qtopia phone server. Since - contrary to standard Qtopia - it does not directly use the framebuffer, non-Qt applications can safely share the screen with Qt applications.<br />
<br />
* [[Om2008.8|Om 2008.8]]<br />
* Download: [http://downloads.openmoko.org/releases/Om2008.8/ Releases are labeled "Om2008.8" ]<br />
<br />
=== FSO - freesmartphone.org ===<br />
<br />
FSO has been started to overcome the deficiencies both of the 2007.2 and the 2008.8 stack, namely to come up with an extensible framework that gives developers the infrastructure they need to create solid and exciting software products based on the Openmoko platform. An infrastructure that supports competing UIs while we can collaborate on developing services, making the framework strong . Here, the focus is on stable highlevel services that you can access from whatever language or UI that supports [http://dbus.freesmartphone.org/ dbus]. People report that despite its infancy, e.g. the phone server part in FSO is already more solid than anywhere else.<br />
<br />
It is not really intended as future release-target, but used as a 'vessel' or 'container' for the development and testing of the new, future middleware.<br><br />
The applications installed are intended as test-tools for the new middleware and not as fully featured, end user oriented applications. (even if it looks that way sometimes)<br />
<br />
* [[FSO]]<br />
* [http://trac.freesmartphone.org:8000/trac-example Development tracker]<br />
* [http://downloads.openmoko.org/framework/milestone2/ Download milestone 2]<br />
* [http://freesmartphone.org freesmartphone.org]<br />
<br />
== Openmoko Community driven release targets ==<br />
<br />
=== SHR - Stable Hybrid Release ===<br />
<br />
Stable Hybrid Release is a combination of the middleware from FSO, some of the 2007.2 GTK software (telephony-ui, pim), and Om2008.8 that provides all of the functionality of the 2007.2 software, but with the stability of the FSO.<br />
<br />
* [[Stable Hybrid Release]]<br />
<br />
== Non-Openmoko distributions ==<br />
<br />
These are not Openmoko (and OE) based distributions. These are an alternatives you can run on your Openmoko phones.<br />
<br />
=== Qtopia ===<br />
<br />
The Qtopia distribution from [http://www.trolltech.com Trolltech], it aims to provide a ready-to use image for Openmoko devices. <br />
<br />
* [[Qtopia]]<br />
* Download: [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Qtopia.net]<br />
<br />
=== Debian ===<br />
<br />
Debian Linux, the whole distribution, on a mobile phone.<br />
<br />
* [[Debian]]<br />
<br />
== Features by distribution/release target ==<br />
<br />
=== Connectivity ===<br />
<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| Telephony || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| SMS || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| GPRS || Not through UI || Not through UI || Not through UI || N/A || No (3) || ??<br />
|-<br />
| WiFi || style="background:lightgreen;" | Yes || Not through UI || style="background:lightgreen;" | Yes (*) || N/A || style="background:lightgreen;" | Yes ||style="background:lightgreen;" | Yes<br />
|-<br />
| VoIP || ?? || ?? || ?? || ?? || ?? || ??<br />
|-<br />
| Bluetooth || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| GPS || style="background:lightgreen;" | Yes (1) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || No || ??<br />
|-<br />
|}<br />
<br />
=== User Interaction ===<br />
<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| Stylus friendly || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| Finger friendly || Partially || Partially || Partially || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| Accelerometer || No || No || No || N/A || No || ??<br />
|-<br />
|}<br />
<br />
=== Applications ===<br />
<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| Terminal || Basic (2) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes<br />
|-<br />
| PIM || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| Phonebook || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| Dialer || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| Web Browser || style="background:lightgreen;" | Yes (1) || ? || style="background:lightgreen;" | Yes (1) || ? || No || ?<br />
|-<br />
| Mail Client || ? || ? || ? || ? || style="background:lightgreen;" | Yes || ?<br />
|-<br />
| XMPP Client || style="background:lightgreen;" | Yes (1) || ? || ? || ? || No || ?<br />
|-<br />
|}<br />
<br />
=== Toolkits / Runtimes ===<br />
{| border=1 width=100% |<br />
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian<br />
|-<br />
| GTK+ || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || No || ??<br />
|-<br />
| QT/Qtopia || No || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || ??<br />
|-<br />
| Middleware || gsmd/neod || freesmartphone.org || qtopia-x11 || freesmartphone.org || qtopia || ??<br />
|-<br />
| [[Java]] || Jalimo || ? || ? || ? || ? || ??<br />
|-<br />
| [[Python]] || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || ??<br />
|-<br />
|}<br />
<br />
<br />
Footnotes:<br />
<br />
(1) works, but need additional software to be installed<br />
<br />
(2) unusable due to lack of certain keyboard characters (unless you [[Switching_Keyboards#Matchbox_keyboard|install matchbox-keyboard]])<br />
<br />
(3) there is a UI but it crashes the device when used.<br />
<br />
(*) unstable<br />
== External links ==<br />
<br />
Original distribution descriptions are from Mickey Lauer's [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!].<br />
<br />
[[Category:Distributions| ]]<br />
[[Category:Documentation]]</div>Youshehttp://openmoko.org/wiki/Main_Page/frMain Page/fr2008-08-09T17:13:45Z<p>Youshe: Mise à jour de la page, conformément à la page principale en anglais.</p>
<hr />
<div>{{Languages|Main Page}}<br />
__NOTOC__<br />
__NOEDITSECTION__ [[Image:Freerunner02.gif|thumb|150px|right|Neo Freerunners]]<br />
<br />
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div><br />
<br />
Openmoko™ est un projet destiné à fournir un téléphone portable doté d'une couche logicielle opensource. <br />
A l'heure actuelle, Openmoko propose à la vente le téléphone [[Neo FreeRunner]] dédié pour l'instant à des utilisateurs avancés.<br />
Une fois que la coucle logicielle sera plus élaborée, le grand public pourra être visé.<br />
<br />
La couche logicielle Openmoko -qui inclue un serveur X complet- permet aux utilisateurs et développeurs de transformer la plateforme matérielle en un produit unique.<br />
Notre licence donne en effet la liberté la liberté d'adapter l'interface graphique, voir de la modifier totalement, de changer le fond d'écran, ou encore de modifier totalement l'aspect logiciel !<br />
La licence donne ainsi par exemple la liberté à l'utilisateur de transformer son téléphone en un appareil médical, en un espace de vente portatif ou encore de simplement installer ses applications favorites.<br />
En plus de proposer un logiciel libre sur nos machines, nous fournissons aussi l'intégralité du design sous licence Creative Commons.<br />
Par ailleurs, nous avons annoncé la diffusion des spécifications de nos produits aux Linux World 2008<br />
<br />
<div style="clear:both">&nbsp;</div><br />
<br />
<table class="wikitable" cellspacing="4" cellpadding="6" width="100%" style="color:white"><br />
<tr style="background:#ff6600; text-align:center; font-weight:bold"><br />
<td width="50%">Nouveautés et évènements</td><br />
<td width="50%">Nouveau sur Openmoko ?</td><br />
</tr><br />
<tr valign="top" style="background:#333333"><br />
<td><br />
* 8/8: Première sortie officielle de [[Om 2008.8]] (cf. [http://lists.openmoko.org/pipermail/community/2008-August/025619.html])<br />
* 4-5/8: Openmoko à Linuxworld, San Francisco<br />
* 30/7: La distribution FSO sort [http://downloads.openmoko.org/framework/milestone2/ milestone 2]<br />
* 25/7: Aide communautaire, [[GPS Problems|Problèmes de GPS]] corrigés<br />
* 20/7: Ajout de [[Debian]] à la page des [[Distributions]]<br />
* 27/6: Vente du GTA 02 sur [http://lists.openmoko.org/pipermail/community/2008-June/019943.html material world]<br />
</td><br />
<td><br />
===<font color=white>A propos d'Openmoko</font>===<br />
<br />
* [[Introduction]]<br />
* [[Why Openmoko|Pourquoi Openmoko ?]]<br />
* [[Neo FreeRunner|Le Neo FreeRunner]]<br />
* [[Supported Hardware|Matériel supporté]]<br />
* [[FAQ]]<br />
<br />
===<font color=white>Se procurer Openmoko</font>===<br />
* [[Getting Openmoko|Obtenir Openmoko]]<br />
* [http://www.openmoko.com Openmoko Inc.]<br />
<br />
</td><br />
</tr><br />
<tr style="background:#ff6600; text-align:center; font-weight:bold"><br />
<td width="50%">Pour les utilisateurs</td><br />
<td width="50%">Pour les développeurs</td><br />
</tr><br />
<tr valign="top" style="background:#333333"><br />
<td><br />
===<font color=white>Où commencer ?</font>===<br />
* [[Getting Started with your Neo FreeRunner | Guide de démarrage du Neo FreeRunner]]<br />
* [[Getting Started FAQ| FAQ sur le guide de démarrage]]<br />
<br />
<br />
===<font color=white>Logiciel</font>===<br />
* [[Distributions|Distributions logicielles Openmoko]]<br />
* [[Om 2007.2|distribution 2007.2]]<br />
* [[Om 2008.8|distribution 2008.8]]<br />
* [[OpenmokoFramework|distribution FSO]]<br />
* [[Qtopia_on_FreeRunner|distribution Qtopia]]<br />
<br />
===<font color=white>Communauté Openmoko</font>===<br />
* [[Discussion_Forums| Forums de discussion]]<br />
* [[CommunityRepository|Repository Commonautaire]]<br />
* [[Development resources | Ressources concernant le développement]]<br />
* [http://openmoko-fr.org Communauté Française]<br />
</td><br />
<td><br />
===<font color=white>Développement applicatif</font>===<br />
* [[Openmoko developer guide|Guide du développeur Openmoko]]<br />
* [[Toolchain|Suite d'outils]]<br />
<!-- * <font color=white>VMware</font> --><br />
* [[Python|Introduction à Python]]<br />
* [http://projects.openmoko.org/ Projects hosted in our GForge]<br />
<br />
===<font color=white>Intégration et distributions</font>===<br />
* [[OpenEmbedded|Librairie de développement OpenEmbedded]]<br />
* [[MokoMakefile|Compiler Openmoko à l'aide du MokoMakefile ]]<br />
* [[Opkg|Opkg, le gestionnaire de packages]]<br />
<br />
===<font color=white>Emulation</font>===<br />
* [[Openmoko under QEMU|Openmoko sous QEMU]]<br />
</td><br />
</tr><br />
</table><br />
<br />
[[Category:Information| ]]</div>Youshe