Dbus device API

From Openmoko

Jump to: navigation, search
In progress: This article or section documents one or more features whose implementation are in progress.


Contents

A dbus API that allows setting/getting hardware specifics in a platform independent way.

  • May be written as devmand (see linuxtogo.org)
  • May be the successor to zaurusd
  • May be formalized using the FreeSmartPhone.org initiative

Could be based on [1] Or based on [2]

The existing Neo1973 DBus API

Here is the list of objects that advertise themselves on dbus on my Neo1973 right now. Each object links to a page with an overview of the API for the object (based on the results of calling Introspect), followed by the XML from an Introspect call.

The (arbitrary) way I constructed the overview of the API is as follows:

Bus name: <bus name within the given bus>
Object name: <object name within that bus name>
  interface: <some interface the object provides>
    (outval1:type, outval2:type) methodName(inval1:type,inval2:type)
    signal (arg1:type)

The types are just a direct transcription of the type in the Introspect XML.

The types:

  • s - string
  • b - boolean
  • ax - array of x (where x is another entry in this list)
  • <someone please add any new types for which you know the meaning>

TODO: finish filling out the list; double check for objects ending in a digit (since I filtered those out, some rightly and now I see some incorrectly).

Session Bus

Starter Bus

For some reason this appears to be identical to the Session Bus. There is a tree of GConf nodes returned in the Introspection, but they just refer to more nodes, the leaf nodes don't advertise any interfaces or functionality via Introspect.

System Bus

Personal tools