View source for User:Panta/translate
From Openmoko
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Template used on this page:
Return to User:Panta/translate.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Template used on this page:
Return to User:Panta/translate.
Languages: |
English • العربية • Български • Česky • Dansk • Deutsch • Esperanto • Eesti • Español • فارسی • Suomi • Français • עברית • Magyar • Italiano • 한국어 • Nederlands • Norsk (bokmål) • Polski • Português • Română • Русский • Svenska • Slovenčina • Українська • 中文(中国大陆) • 中文(台灣) • Euskara • Català |
Note: Questa è la (attuale) descrizione della nuova architettura framework in sviluppo. Si veda OpenmokoOldFramework per informazioni sull'architettura framework 2007.1 e 2007.2, nonché NeoSoftwareStack per lo stato attuale (che non ha ancora niente da fare con questo framework)
Questa iniziativa non copre servizi di basso livello come
Questa iniziativa non copre servizi di alto livello come
Noi facciamo differenza tra servizi di alto e basso livello -- per comunicare orizzontalmente e verticalmente verrà utilizzato dbus.
Il servizio di controllo del dispositivo di basso livello gestisce il controllo delle periferiche, il che consiste nel verificare l'accensione di sottosistemi singoli come
Inoltre, ha a che fare con
Per finire, invia notifiche sulle attività dell'utente in modo che i servizi in ascolto possano
Per far ciò, abbiamo implementato il software seguente:
The low level audio service relies on a working alsa device driver. On top of that, there are two components:
Gstreamer is to be used for all kinds of event sounds where a) multiple audio formats need to be supported and b) a latency of about one second is acceptable. This goes for e.g. ring tones, welcome tones, plug indication.
Pulseaudio is to be used for event sounds, where low-latency is necessary, e.g. touch click sounds and UI event acknowledge sounds. Pulseaudio is our general all-purpose mixer. Gstreamer will use the pulseaudio sink to feed audio through.
The low level GSM services expect a modem complying to GSM 07.07, GSM 07.05, and assorted GSM specifications, talking an AT-protocol over a serial line. If GSM 07.10 is supported, we use the multiplexing daemon
to export virtual serial lines over -- again -- AT-protocol can be spoken.
The low level Bluetooth services rely on the official Linux Bluetooth subsystem:
The low level GPS services assume a GPS device that talks NMEA over a device node. We rely on the following software:
The low level networking service assumes network interfaces, such as USB, Ethernet, Wifi, etc. We rely on the following software here:
The Usage subsystem is coordinating application I/O requirements preventing. Applications are not supposed to turn on or off devices, since they do not have any knowledge about concurrent applications that may be also using the device -- think reference counting for I/O requirements.
With this added layer, we could later think about monitoring subsystems, subsystem usage statistics, or accounting.
See discussion page about PolicyKit.
An intelligent storage database server. This is being carried out as a Google Summer of Code project. See complete description at [1]
TBD Reference Geoclue
Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the Dbus APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.
Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, if necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.
Milestone 1:
Milestone 2:
Milestone 3: