User:Panta/translate

From Openmoko

< User:Panta(Difference between revisions)
Jump to: navigation, search
m (OpenMoko to translate)
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Openmoko is the distribution that we're creating for phones and eventually other mobile devices.  
+
{{Languages|Main Page}}
 +
__NOTOC__
 +
__NOEDITSECTION__ [[Image:Freerunner02.gif|thumb|150px|right|Neo Freerunners]]
  
See [[Trademark Policy]] for information on the Openmoko trademark policy.
+
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div>
  
It has the following software stack:
+
Openmoko™ è un progetto il cui scopo è distribuire telefoni cellulari con uno stack software open source. Al momento Openmoko sta vendendo il telefono [[Neo FreeRunner]] ad utenti tecnologicamente più preparati, ma inizierà a venderlo al pubblico generico nel momento in cui il software sarà sviluppato maggiormente.
  
{{ui_img_path}}/software_stack2007.png
+
Lo stack Openmoko, che include un server X completo, permette ad utenti e sviluppatori di trasformare piattaforme hardware mobile in prodotti unici. La nostra licenza lascia a sviluppatori ed utenti la libertà di personalizzare i propri dispositivi a livello estetico o di modificarli radicalmente; sostituire la carta da parati o ricostruire la casa per intero! Gli  garantisce la liberta, per esempio, di trasformare il telefono in un dispositivo medico, in un registratore di cassa o di installare semplicemente il proprio software preferito. Oltre a rendere libero il software presente nei nostri apparati, ne abbiamo rilasciato i relativi file CAD sotto licenza Creative Commons. In occasione del Linux world 2008, abbiamo annunciato il rilascio degli schemi interni dei nostri prodotti.  
  
A printer-friendly version can be found [http://people.openmoko.org/sean/files/openmokostack2007.pdf here].
+
<div style="clear:both">&nbsp;</div>
  
 +
<table class="wikitable" cellspacing="4" cellpadding="6" width="100%" style="color:white">
 +
<tr style="background:#ff6600; text-align:center; font-weight:bold">
 +
<td width="50%">Notizie ed eventi (en)</td>
 +
<td width="50%">Sei nuovo ad Openmoko?</td>
 +
</tr>
 +
<tr valign="top" style="background:#333333">
 +
<td>
 +
* 2/9: Trolltech [http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=83 released] Qtopia 4.3.3-snapshot.
 +
* 28/8: Trolltech [http://n2.nabble.com/qtopia-4.3.2-release-tp789148p789148.html released] Qtopia 4.3.2.
 +
* 26/8: Openmoko [http://lists.openmoko.org/pipermail/community/2008-August/027997.html updates] [[Om 2008.8]] distribution.
 +
* 15/8: [[Debian]] on the FreeRunner [http://n2.nabble.com/Debian-on-the-FreeRunner----now-official-td726410.html announced] (instructions for [http://wiki.debian.org/DebianOnFreeRunner FreeRunner] and [http://wiki.debian.org/DebianOnNeo1973 Neo1973]).
 +
<br />
 +
* [[Weekly Engineering News|Openmoko Weekly Engineering News]]
 +
* [[News Archive|(news archive)]]<!--Editors: copy removed news to News Archive! -->
 +
</td>
 +
<td>
 +
===<font color=white>About Openmoko</font>===
 +
* [[Introduction/it | Introduzione]]
 +
* [[Why Openmoko | Why Openmoko (en)]]
 +
* [[Neo FreeRunner/it|Il telefono Neo FreeRunner]]
 +
* [[Supported Hardware | Supported Hardware (en)]]
 +
* [[FAQ/it | FAQ]]
  
{{note|This article needs to be updated to reflect our current architecture.}}
+
===<font color=white>Ottenere Openmoko</font>===
 +
* [[Getting Openmoko | Getting Openmoko (en)]]
 +
* [http://www.openmoko.com Openmoko Inc.]
  
== Kernel Space ==
+
</td>
The Kernel Space consists of the Bootloader, the Kernel, and Power Management.
+
</tr>
 +
<tr style="background:#ff6600; text-align:center; font-weight:bold">
 +
<td width="50%">Area Utenti</td>
 +
<td width="50%">Area Sviluppatori</td>
 +
</tr>
 +
<tr valign="top" style="background:#333333">
 +
<td>
 +
===<font color=white>Getting started</font>===
 +
* [[Getting Started with your Neo FreeRunner | Neo FreeRunner getting started guide]]
 +
* [[Applications]]
  
=== Bootloader ===
+
===<font color=white>Distributions</font>===
The Bootloader is [[u-boot]]. We will have the following requirements:
+
* [[Distributions|Features comparison table]]
* '''Firmware Update''' – Need a way to download executible code using [[USB DFU]]
+
* [[Om 2008.8|Om 2008.8 (ASU)]] - [[Om 2007.2|Om 2007.2 (old stable)]]
* '''RAM Loader''' – Provide a method to run code directly from the device’s RAM
+
* [[OpenmokoFramework|FSO]] - [[Qtopia_on_FreeRunner|Qtopia]] - [[Debian|Debian]] - [[Gentoo|Gentoo]]
* '''Secure Memory Interface''' – Provide a method to secure the interface to write into both RAM and FLASH. This is for the end user to prevent other users from modifying their own handsets. It’s not for vendor lock-in.
+
* '''[[Backup]]''' – Provide a method to backup the data from flash. This could possibly allow for the sharing of images between users.
+
  
=== Kernel ===
+
===<font color=white>Openmoko community</font>===
The Kernel is based on the 2.6.x mainline using the moko patch set. It was planned to use TomTom's patches as they did extensive work with the Samsung 2410 application processor and added great support for SD cards. Currently their patches will allow support for almost all vendors’ SD cards. Kernel work is divided into the following components:
+
* [[Mailing List Duplicates| Mailing List Duplicates]]
 +
* [[Discussion_Forums| Discussion Forums]]
 +
* [[CommunityRepository|Community repository]]
 +
* [[Development resources | Development resources]]
 +
</td>
 +
<td>
 +
===<font color=white>Applications development</font>===
 +
* [[Openmoko developer guide]]
 +
* [[Toolchain|The toolchain]]
 +
<!-- * <font color=white>VMware</font> -->
 +
* [[Python|Introduction to Python]]
 +
* [http://projects.openmoko.org/ Projects hosted in our GForge]
  
==== Flash ====
+
===<font color=white>Integration and distributions</font>===
The flash functions as a MTD using the standard Linux access. It will run the JFFS2 filesystem over the entire flash.
+
* [[OpenEmbedded|The OpenEmbedded distribution building framework]]
We would like to have some type of encryption on the user’s data. This will be configured in the User Interface at a later time. But for now, we should build the supporting framework.
+
* [[MokoMakefile|Building Openmoko using the MokoMakefile ]]
 +
* [[Opkg|The Opkg package manager]]
  
==== Sound ====
+
===<font color=white>Emulation</font>===
The sound driver for the codec uses Advanced Linux Sound Architecture (ALSA) with the ASoC glue code. This is the standard for Linux sound cards.
+
* [[Openmoko under QEMU]]
 +
</td>
 +
</tr>
 +
</table>
  
==== Backlight ====
+
Browse articles by [[:Category:Categories|Categories]].
This is an LCD backlight class driver.
+
 
+
==== Keypad / Buttons ====
+
The keypad driver will use the standard Input device /dev/input.
+
 
+
==== Touch Screen ====
+
The touch screen driver uses the standard Input device /dev/input/touchscreen0.
+
 
+
==== Accellerometer (GTA02 only) ====
+
{{stub}}
+
 
+
==== USB ====
+
We will need USB host / client support for Linux, OS X, and Windows. It should support the following features:
+
* '''Mass Storage''' – To be mountable from another device
+
* '''Host Network''' – To provide networking support over USB
+
* '''Linux USB Gadget''' – The standard method for having the device act as a slave
+
 
+
==== NFS Root Support ====
+
This will serve as one of our methods to develop code for the device. It will allow us to have a filesystem larger than the actual flash size. See [[Booting_from_NFS]] for setup details.
+
 
+
==== Bluetooth ====
+
Bluetooth support will be based on the Linux standard called BlueZ. We will support the following profiles:
+
* '''Headset''' – For wireless headsets
+
* '''OBEX''' – For file transfer
+
* '''HID''' – For both Bluetooth keyboards and keypad emulation (such as for remote control devices)
+
* '''Network Emulation''' – For Bluetooth-based network support
+
 
+
==== WiFi (GTA02 only) ====
+
{{stub}}
+
 
+
==== TS07.10 ====
+
This is the [[GSM]] interface part. It is based on the idea of creating multiple serial devices out of one physical serial device. This code will be based work from the openEZX project and the original Motorola architecture. It will also provide ipsec for secure [[VPN]] connections.
+
 
+
The following diagram depicts the general architecture:
+
 
+
{{ui_img_path}}/gsm_interface.png
+
 
+
A printer-friendly version can be found [http://people.openmoko.org/sean/files/openmokogsm.pdf here].
+
 
+
===== GPRS modem=====
+
2.5G (no EDGE) access to the Internet.
+
 
+
==== Vibration ====
+
This is using the LED class interface. This may be troublesome for mainline merging, but it makes no sense to invent a new subsystem which would be 100% identical to the LED class interface.
+
 
+
=== Power Management ===
+
The Power Management Unit will interface with the standard kernel I2C interface. The actual power states transitions are TBD.
+
 
+
== User Space ==
+
 
+
{{note|We will use glibc (not uClibC) and libX11 (full, not diet) for the first incarnation of this product. The alternatives may save more space and be more optimized, but are more likely to give us integration headaches. We will have to reconsider this decision for later releases.}}
+
 
+
=== Linux Core Services ===
+
 
+
Most of these core services include a daemon and a library.
+
 
+
==== sshd ====
+
sshd enables a remote shell login via network.
+
 
+
==== udev ====
+
udev is responsible for managing the device nodes in the /dev pseudo file system.
+
 
+
==== bluez ====
+
bluez is the Linux Bluetooth subsystem.
+
 
+
==== dbus ====
+
dbus is an interprocess communication subsystem.
+
 
+
==== GSM ====
+
* '''GSM''' - handles the communication with the GSM module.
+
* '''gsmd''' - is responsible for the management of GSM backend.
+
* '''libgsmd''' - will communicate with the gsmd and export an API for applications.
+
 
+
==== GPS ====
+
* '''GPS''' - handles the communication with the GPS module.
+
* '''[http://gpsd.berlios.de/ gpsd]''' - is the daemon for management of GPS backend. It will export the standard [[Gpsd|gpsd]] interface.
+
 
+
=== Linux User Interface ===
+
==== Matchbox ====
+
A lightweight window manager from the [http://projects.o-hand.com/matchbox O-Hand]
+
 
+
==== KDrive ====
+
KDrive-fbdev is a lightweight X11 server that runs directly on a Linux FrameBuffer.
+
 
+
==== libX11 ====
+
The X11 library.
+
 
+
==== GTK+ ====
+
GTK+ is a rich GUI-Toolkit. It's the foundation for the [http://gtk.org Gnome project]
+
 
+
=== Openmoko Application Framework ===
+
{{Main|OpenMokoFramework}}
+
 
+
==== Native Applications ====
+
===== Currently Included Applications =====
+
Currently included applications that are accessible from the application menus are found [[Openmoko_Core_Applications | here]].
+
This consists of both Stylus-based and Finger-based applications.
+
 
+
===== Finger-Based Applications =====
+
Complete specifications for all the Finger-Based Applications are found [[Applications#Finger-Based_Applications | here]].
+
 
+
===== Stylus-Based Applications =====
+
Complete specifications for all the Stylus-Based Applications are found [[Applications#Stylus-Based_Applications | here]].
+
 
+
<span id="bottom"></span>
+
{{Languages|OpenMoko}}
+
 
+
[[Category:Openmoko| ]]
+
[[Category:Neo1973_Phase_0_related]]
+
[[Category:Neo1973_Phase_1_related]]
+

Latest revision as of 06:39, 18 November 2008


Neo Freerunners
Openmoko™ - Open. Mobile. Free.

Openmoko™ è un progetto il cui scopo è distribuire telefoni cellulari con uno stack software open source. Al momento Openmoko sta vendendo il telefono Neo FreeRunner ad utenti tecnologicamente più preparati, ma inizierà a venderlo al pubblico generico nel momento in cui il software sarà sviluppato maggiormente.

Lo stack Openmoko, che include un server X completo, permette ad utenti e sviluppatori di trasformare piattaforme hardware mobile in prodotti unici. La nostra licenza lascia a sviluppatori ed utenti la libertà di personalizzare i propri dispositivi a livello estetico o di modificarli radicalmente; sostituire la carta da parati o ricostruire la casa per intero! Gli garantisce la liberta, per esempio, di trasformare il telefono in un dispositivo medico, in un registratore di cassa o di installare semplicemente il proprio software preferito. Oltre a rendere libero il software presente nei nostri apparati, ne abbiamo rilasciato i relativi file CAD sotto licenza Creative Commons. In occasione del Linux world 2008, abbiamo annunciato il rilascio degli schemi interni dei nostri prodotti.

 
Notizie ed eventi (en) Sei nuovo ad Openmoko?


About Openmoko

Ottenere Openmoko

Area Utenti Area Sviluppatori

Getting started

Distributions

Openmoko community

Applications development

Integration and distributions

Emulation

Browse articles by Categories.

Personal tools

Openmoko is the distribution that we're creating for phones and eventually other mobile devices.

See Trademark Policy for information on the Openmoko trademark policy.

It has the following software stack:

Template:Ui img path/software_stack2007.png

A printer-friendly version can be found here.


NOTE: This article needs to be updated to reflect our current architecture.


Kernel Space

The Kernel Space consists of the Bootloader, the Kernel, and Power Management.

Bootloader

The Bootloader is u-boot. We will have the following requirements:

  • Firmware Update – Need a way to download executible code using USB DFU
  • RAM Loader – Provide a method to run code directly from the device’s RAM
  • Secure Memory Interface – Provide a method to secure the interface to write into both RAM and FLASH. This is for the end user to prevent other users from modifying their own handsets. It’s not for vendor lock-in.
  • Backup – Provide a method to backup the data from flash. This could possibly allow for the sharing of images between users.

Kernel

The Kernel is based on the 2.6.x mainline using the moko patch set. It was planned to use TomTom's patches as they did extensive work with the Samsung 2410 application processor and added great support for SD cards. Currently their patches will allow support for almost all vendors’ SD cards. Kernel work is divided into the following components:

Flash

The flash functions as a MTD using the standard Linux access. It will run the JFFS2 filesystem over the entire flash. We would like to have some type of encryption on the user’s data. This will be configured in the User Interface at a later time. But for now, we should build the supporting framework.

Sound

The sound driver for the codec uses Advanced Linux Sound Architecture (ALSA) with the ASoC glue code. This is the standard for Linux sound cards.

Backlight

This is an LCD backlight class driver.

Keypad / Buttons

The keypad driver will use the standard Input device /dev/input.

Touch Screen

The touch screen driver uses the standard Input device /dev/input/touchscreen0.

Accellerometer (GTA02 only)

Stub: This is a stub. You can help OpenMokoWiki by expanding it.


USB

We will need USB host / client support for Linux, OS X, and Windows. It should support the following features:

  • Mass Storage – To be mountable from another device
  • Host Network – To provide networking support over USB
  • Linux USB Gadget – The standard method for having the device act as a slave

NFS Root Support

This will serve as one of our methods to develop code for the device. It will allow us to have a filesystem larger than the actual flash size. See Booting_from_NFS for setup details.

Bluetooth

Bluetooth support will be based on the Linux standard called BlueZ. We will support the following profiles:

  • Headset – For wireless headsets
  • OBEX – For file transfer
  • HID – For both Bluetooth keyboards and keypad emulation (such as for remote control devices)
  • Network Emulation – For Bluetooth-based network support

WiFi (GTA02 only)

Stub: This is a stub. You can help OpenMokoWiki by expanding it.


TS07.10

This is the GSM interface part. It is based on the idea of creating multiple serial devices out of one physical serial device. This code will be based work from the openEZX project and the original Motorola architecture. It will also provide ipsec for secure VPN connections.

The following diagram depicts the general architecture:

Template:Ui img path/gsm_interface.png

A printer-friendly version can be found here.

GPRS modem

2.5G (no EDGE) access to the Internet.

Vibration

This is using the LED class interface. This may be troublesome for mainline merging, but it makes no sense to invent a new subsystem which would be 100% identical to the LED class interface.

Power Management

The Power Management Unit will interface with the standard kernel I2C interface. The actual power states transitions are TBD.

User Space

NOTE: We will use glibc (not uClibC) and libX11 (full, not diet) for the first incarnation of this product. The alternatives may save more space and be more optimized, but are more likely to give us integration headaches. We will have to reconsider this decision for later releases.


Linux Core Services

Most of these core services include a daemon and a library.

sshd

sshd enables a remote shell login via network.

udev

udev is responsible for managing the device nodes in the /dev pseudo file system.

bluez

bluez is the Linux Bluetooth subsystem.

dbus

dbus is an interprocess communication subsystem.

GSM

  • GSM - handles the communication with the GSM module.
  • gsmd - is responsible for the management of GSM backend.
  • libgsmd - will communicate with the gsmd and export an API for applications.

GPS

  • GPS - handles the communication with the GPS module.
  • gpsd - is the daemon for management of GPS backend. It will export the standard gpsd interface.

Linux User Interface

Matchbox

A lightweight window manager from the O-Hand

KDrive

KDrive-fbdev is a lightweight X11 server that runs directly on a Linux FrameBuffer.

libX11

The X11 library.

GTK+

GTK+ is a rich GUI-Toolkit. It's the foundation for the Gnome project

Openmoko Application Framework

Main article: OpenMokoFramework


Native Applications

Currently Included Applications

Currently included applications that are accessible from the application menus are found here. This consists of both Stylus-based and Finger-based applications.

Finger-Based Applications

Complete specifications for all the Finger-Based Applications are found here.

Stylus-Based Applications

Complete specifications for all the Stylus-Based Applications are found here.