Comparison of seven Linux mobile phone platforms (1): Similarities and Differences between processes

At present, there are many Linux mobile phone platforms, no matter whether they are strong or weak at present, let's put them aside first;

Let's take a look at the similarities and differences between the technical points used in each platform, such as analyzing

The similarities and differences between processes and communication mechanisms on each platform will be analyzed one by one.

 

 

At present, there are several Linux mobile platforms:

1 maemo

2 android

3 limo

4 openmoko

5 GPE ^ 2

6.

7 qtopia phone edition.

 

 

First put their system architecture here, and then find out their similarities and differences from the architecture.

Today, we will analyze the inter-process communication mechanism (IPC) of each platform ).

 

 

Android architecture:

 

 

 Maemo Achitecture:

 

Limo architecture:

I have previously written several division of labor:

Http://blog.csdn.net/cuijpus/archive/2007/12/21/1956597.aspx

Some official documents have already been released. You can check them out:

Http://www.limofoundation.org/technical-documents.html

 

Openmoko architecture:

 

 

GPE phone edition architecture:

 

 

 

 

Http://gpephone.linuxtogo.org/

Http://gpephone.linuxtogo.org/doc/components/gpearch.php

 

Qtopia phone edition:

 

Http://dist.trolltech.com/pdf/Greensuite%231_FactSheet_cn.pdf

Http://dist.trolltech.com/pdf/Qtopia_Phone_Edition_4_ds_v7_A4_web_cn20080221.pdf

PLD architecture:

 

 

Http://alp.access-company.com/

 

 

 

From the above architectures, we can see that for inter-process communication,

1 maemo D-BUS used

2. openbinder for Android

3 limo with D-BUS

4 openmoko D-BUS

5 GPE phone edition D-BUS

6. Using openbinder

7 qtopia phone edition D-BUS (http://doc.trolltech.com/4.2/intro-to-dbus.html)

 

 

From the comparison, we can find that the main use of D-BUS and openbinder communication mechanism between processes, and the D-BUS is widely used.

 

D-BUS:

 

For the introduction of D-BUS, you can go to its official website to learn about the comprehensive information:

 

 

Http://www.freedesktop.org

Http://www.freedesktop.org/wiki/Software/dbus

Http://dbus.freedesktop.org/doc/dbus-specification.html

Http://blog.csdn.net/cuijpus/archive/2008/01/30/2073962.aspx

 

 

 

Openbinder:

Openbinder is described as "similar to DCOM and CORBA in general, but it is better suited to small-scale devices ".

 

Http://www.open-binder.org/

Http://www.open-binder.org/docs/html/BinderOverview.html

 

 

It is not surprising that openbinder is used as the IPC for access Linux platform, because

Access acquired palm, and palm started to use openbinder.

 

The Android platform also uses openbinder as the IPC. The Android platform has two differences: the Java language,

Instead of C as the language of most programs; the other is not using D-BUS, but using openbinder.

Http://www.android-internals.org/index.php? Title = openbinder

It is estimated that there are historical origins, just like access directly inherits openbinder, Google's Android

It was originally acquired.

 

 

Supplement: for inter-process communication, there are mainly five:

1 D-BUS

2 openbinder

3. CORBA/Corbit

4 Ivy

5 GNET

Http://www.gnetlibrary.org/

 

 

In addition, there is an open-source broncho platform in China, which is very good. You can check it out.

Http://www.broncho.cn/