View source for OpenmokoFramework/fr
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:
Templates used on this page:
Return to OpenmokoFramework/fr.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Templates used on this page:
Return to OpenmokoFramework/fr.
![]() |
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à |
Introduction |
---|
Note: This is the (ongoing) description of the new framework architecture that is in development. See OpenmokoOldFramework for the framework architecture of 2007.1 and 2007.2 and NeoSoftwareStack for the current status (which has nothing to do yet with this framework)
This initiative does not cover low level services such as
This initiative does not cover high level services such as
We differenciate between low-level and high-level services -- dbus will be used to communicate horizontally and vertically.
The low level device control service manages peripheral control, i.e. controlling power for individual subsystems such as
It also deals with
Last but not least, it sends notifications about the user's activity so that listeners have a chance to
We implement the following software for that:
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 here
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.
Subsystem Ownership
Phase 1 subsystems
Phase 2 subsystems
The milestone releases are combined Openmoko Framework and Zhone releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does not exist. Until Framework 1.0.0 (later this year), we will not use any versioning in components. Afterwards, individual components may see individual releases.
Note: If you have implemented a task, please edit this page and add a '[done]' behind. In the very unlikely event that you can't finish a task for a milestone, then add strike it through and add it to the next milestone. Don't leave it sitting untouched -- poor little feature does not deserve this!
P h a s e O n e
Features
Tasks
Features
Tasks
Features
Tasks
Integration Features
Tasks
Features
Tasks
Participants
Evaluation Criteria
Features
Tasks
P h a s e T w o