Editing Documentation/Maemo 5 Developer Guide/Architecture/Core Domain

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

[[Image:core_top_level_decomposition.png|500px|alt=Diagram|Core architecture]]

==Nolo bootloader==

;Name
: NoLo (Nokia Loader)
;Purpose
: The bootloader does basic configuration of the HW, loads the kernel into memory, and passes control to the kernel. In addition to this basic task the NoLo boot loader has many features to support R&D. (The capability to flash the device is currently implemented in NoLo but it will become an R&D feature once flashing is moved to user space.)
;Responsibilities
: <ul><li>Load kernel into memory</li><li>Initialize HW so that kernel is able to boot</li><li>Pass ATAGs to the kernel and transfer execution to the kernel </li><li>Production line flashing functionality</li><li>Creates partitions</li></ul>
;Package / License
: [http://maemo.org/packages/view/nolo/ nolo] / Nokia

==Linux Kernel==

;Purpose
: The function of the kernel code is to provide all the basic services and hardware interfaces of the Linux operating system for the underlying programs. The kernel also passes the control to the chosen user space program (usually <code>/sbin/init</code>) after initializing its own structures and drivers. When the kernel starts up, it checks a lot of the available subsystems and initializes everything according to the kernel configuration chosen at compile time. Some subsystems will be left uninitialized by the boot loader, for example, the display subsystem.
;Responsibilities
: The operating system kernel
;Notes
: Maemo specific functionality is in OMAP3 & Rover HW specific code. OMAP3 support is developed, generally speaking, in the linux-omap tree, from which code is pulled into Maemo kernel.
;Package / License
: [http://maemo.org/packages/view/kernel/ kernel] / GPL2
;Public interfaces provided
: Linux kernel API: Linux system calls accessed through the C library

===Kernel core services===

;Purpose
: The Linux core services comprise generic, hardware independent code.
;Responsibilities
: <ul><li>memory management</li><li>process management</li><li>device management</li><li>inter-process communication…</li></ul>
;Notes
: Used as is.
;Package / License
: [http://maemo.org/packages/view/kernel/ kernel] / GPL2

===ARM architecture support===

;Purpose
: The ARM architecture subsystem in the kernel provides mainly ARM specific implementations of necessary core mechanisms.
;Responsibilities
: ARM specific implementations of kernel mechanisms.
;Notes
: Used as is.
;Package / License
: [http://maemo.org/packages/view/kernel/ kernel] / GPL2

===Kernel framework===

;Purpose
: The low level HW drivers provide the concrete implementation that is bound to the virtual services in the Linux kernel to provide the complete functionality. 
;Responsibilities
: <ul><li>ALSA & Video for Linux 2 (V4L2) APIs,Networking stack, BlueZ (Bluetooth), mac80211 (WLAN), USB core</li><li>Virtual File System, file systems, block devices, MTD</li><li>Frame buffer, serial port, input layer (keyboard, touch screen)</li></ul>
;Package / License
: [http://maemo.org/packages/view/kernel/ kernel] / GPL2
;Public interfaces provided
: <ul><li>ALSA: Advanced Linux Sound Architecture, de facto Linux sound API.</li><li>V4L2: Video for Linux 2, de facto video capture API + Maemo specific ioctls</li><li>Camera ioctls: Extensions to V4L2 interface used by the camera daemon.</li><li>File systems: FAT16/32, EXT3 and UBIFS file systems are currently supported on the platform.</li><li>Frame buffer: The raw frame buffer interface is used in early stages of the boot.</li><li>Input layer: The input layer events are routed via X to applications.</li><li>Serial port: Available for R&D use.</li></ul>

===OMAP3 support===

;Purpose
: OMAP specific code implements the device drivers and bus support for the specific hardware included in the OMAP3430 chip. The supported OMAP3 subsystems are described in the following subsections.
;Responsibilities
: <ul><li>DMA: OMAP3 has a 32 channel general purpose DMA controller, display DMA, HS USB DMA, and IVA 2.2 DMA (not supported).</li><li>Interrupt handling:OMAP3 has an interrupt controller (MPU INTC) with 96 synchronous interrupt lines.</li><li>OMAP3 specific power management functionality: The power management functionality is built on top of idle, sleep, suspend, resume, and dynamic voltage & frequency scaling functionalities [SystemSW].</li><li>DSP Bridge, ioMMU, OMAP watchdog, GPIOs, timers, Muxing framework</li><li>Gpmc (OneNAND driver), hsmmc (MMC/SD)</li><li>Bus drivers: spi, i2c, McBSP, uart, SSI</li></ul>
;Package / License
: [http://maemo.org/packages/view/kernel/ kernel] / GPL2

===DSP Bridge===

;Purpose
: OMAP's integrated DSP allows offloading tasks to the DSP from the ARM processor.  This is exposed with the DSP bridge component.
;Responsibilities
: Interface to the OMAP3’s DSP which is used for codec acceleration.
;Package / License
: [http://maemo.org/packages/view/kernel/ kernel] / GPL2

===OMAP3 bus drivers===

;Responsibilities
: Drivers for the following buses: SPI, SSI, McBSP, GPIOs, HS MMC/SD, UART, I2C/I2S, RFBI, CBUS, Flash BUS, (STI/XTI debugging interfaces)
;Package / License
: [http://maemo.org/packages/view/kernel/ kernel] / GPL2

===OMAP3 specific HW drivers===

;Responsibilities
: Drivers for following HW components:SGX, OMAP framebuffer & LCD & TV-out, Camera & ISP, HS USB Host & HS USB OTG, SDRAM memory controller, GPMC NAND/NOR flash&SRAM controller, and PRCM
;Package / License
: [http://maemo.org/packages/view/kernel/ kernel] / GPL2

===Specific hardware drivers===

;Responsibilities
: The following components external to OMAP are supported: USB transceiver, USB charging, FM RX/TX, WLAN, OneNAND flash, touch screen, audio, stereo IHF, earphone, digital mics, LEDs, HW keys, ALS, Accelerometer, Vibrator, Proximity sensor, Miscellaneous Sensors, LCD backlight, Bluetooth, WLAN, CMT, Ethernet (R&D use).
;Package / License
: [http://maemo.org/packages/view/kernel/ kernel] / GPL2

==X Window System==

;Purpose
: Graphical User Interface framework
;Responsibilities
: <ul><li>XServer – GUI framework & resource management</li><li>Xv – Video playback interface</li><li>XRandR – Support for rotation & output configuration</li><li>XRender, XComposite – Support for composited UI</li><li>XInput – Routing of input events to applications</li></ul>
;Package/ License
: Several/ MIT
;Public interfaces provided
: <ul><li>X protocol: Interface to the X window system</li><li>DRI2: Direct Rendering Infrastructure 2, [[OpenGL-ES|OpenGL ES 2.0]]</li></ul>

=== OpenGL ES 2.0 ===

;Purpose
: Accelerated 3D rendering
;Responsibilities
: <ul><li>Accelerated 3D rendering</li><li>Acceleration of XRender</li></ul>
;Notes
: The user space GLES components are licensed from Imagination.
;Package/ License
: [http://maemo.org/packages/view/opengles-sgx-img-common/ opengles2-sgx-img-common], [http://maemo.org/packages/view/libgles2/ libgles2]([http://maemo.org/packages/view/libgles2 -sgx-img/-sgx-img]) / Nokia
;Public interfaces provided
: EGL: Khronos API for OpenGL ES application for interacting with the native graphics framework.

==C library==

;Purpose
: Posix C library functionality
;Responsibilities
: <ul><li>System call interfaces</li><li>Posix functionalities</li></ul>
;Package/ License
: [http://maemo.org/packages/view/libc6/ glibc] / LGPL2

==Essential tools==

;Purpose
: The essential tools provide tools needed in system scripts. The role is similar to the Debian essentials (tools that are always installed in a Debian system).
;Responsibilities
: system tools like: shell, grep, find, dpkg, …
;Notes
: Many tools have many limitations compared to the Debian versions. Not all Debian essentials are supported.
;Package/ License
: [http://maemo.org/packages/view/busybox/ busybox] / GPL2
;Public interfaces provided
: <ul><li>Posix shell</li><li>Subset of Debian essentials</li></ul>

==Sysinfod==

;Purpose
: Provide interface for accessing device information
;Responsibilities
: Provide a D-Bus interface to device specific information (HW id, WLAN MAC, …)
;Package / License
: [http://maemo.org/packages/view/sysinfod/ sysinfod] / Nokia
;Public interface provided
: Sysinfod D-Bus interface

==Softupd==

;Purpose
: Program for flashing the eMMC contents
;Responsibilities
: <ul><li>Unpacks a FIASCO image fed to it</li><li>Copies the unpacked contents to eMMC</li></ul>
;Package / License
: [http://maemo.org/packages/view/softupd/ softupd] / Nokia

==Fiasco-flasher==

;Purpose
: Tool for updating the kernel flashed to the device
;Responsibilities
: <ul><li>Flash kernel image into the kernel partition</li><li>Reboot the device</li></ul>
;Package / License
: [http://maemo.org/packages/view/fiasco-flasher/ fiasco-flasher] / Nokia
;Public interface provided
: Fiasco-flasher: The tool can be used to flash a new kernel image into the kernel partition.

[[Category:Development]]
[[Category:Documentation]]
[[Category:Fremantle]]

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Retrieved from "http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/Core_Domain"

Personal tools

Navigation

Views

Editing Documentation/Maemo 5 Developer Guide/Architecture/Core Domain

@@ Line 6: / Line 6: @@
 : NoLo (Nokia Loader)
 ;Purpose
-: The bootloader does basic configuration of the HW, loads the kernel into memory, and passes control to the kernel. In addition to this basic task the NoLo boot loader has many features to support R&D. (The capability to [[update the firmware|flash the device]] is currently implemented in NoLo but it will become an R&D feature once flashing is moved to user space.)
+: The bootloader does basic configuration of the HW, loads the kernel into memory, and passes control to the kernel. In addition to this basic task the NoLo boot loader has many features to support R&D. (The capability to flash the device is currently implemented in NoLo but it will become an R&D feature once flashing is moved to user space.)
 ;Responsibilities
 : <ul><li>Load kernel into memory</li><li>Initialize HW so that kernel is able to boot</li><li>Pass ATAGs to the kernel and transfer execution to the kernel </li><li>Production line flashing functionality</li><li>Creates partitions</li></ul>