Hi Daniil,<br><br>So you mean the API references are object (component) dependent hence there is no unified reference to all the services of /com/nokia objects? I've got to say it is a little bit inconvenient. A unified reference document will be much helpful. So how about mce and icd? I found the <font size="2">dbus-names.h File Reference</font> but no luck with icd in the same page.<br>
<br>Thanks for the help!<br><br>Cheers,<br>Wei<br><br><br><div class="gmail_quote">On Mon, Jun 7, 2010 at 12:20 PM, Daniil Ivanov <span dir="ltr"><<a href="mailto:daniil.ivanov@gmail.com">daniil.ivanov@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Wei!<br>
<br>
CSD stands for cellular services daemon and name explains why API is closed.<br>
<br>
Thanks, Daniil.<br>
<div><div></div><div class="h5"><br>
On Mon, Jun 7, 2010 at 12:15 PM, Wei Li <<a href="mailto:ttlee1984@gmail.com">ttlee1984@gmail.com</a>> wrote:<br>
> Thanks for all your help! As I mentioned, I am doing a middleware (for<br>
> energy efficiency) project on N900, hence I need to get the device status<br>
> information such as battery, WLan card, mce. I need to use DBus to<br>
> communicate with other components in my work. So the refs on DBus methods<br>
> and signals will be helpful. Some of such information (for example, the<br>
> battery) can be queried from HAL which has a defined specification. But some<br>
> are not. For example, under /com/nokia path, there are many objects like<br>
> icd, wlancond and in Faheem's example, csd (don't even know what it is. I<br>
> assumed circuit switch data?), which I couldn't find the docs for them. If<br>
> anyone knows a general reference to all those objects, like what HAL<br>
> specification does, it would be great.<br>
><br>
> BTW, in dbus-send command, the --desti argument specifies the "service",<br>
> meaning the interface? I always get lost with bus name (connection name) and<br>
> interface.<br>
><br>
> Thanks for all the help!<br>
><br>
> Cheers,<br>
> Wei<br>
><br>
> On Mon, Jun 7, 2010 at 11:35 AM, Faheem Pervez <<a href="mailto:trippin1@gmail.com">trippin1@gmail.com</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> On Mon, Jun 7, 2010 at 12:15 AM, Wei Li <<a href="mailto:ttlee1984@gmail.com">ttlee1984@gmail.com</a>> wrote:<br>
>> > I am doing a project of middleware on Maemo/N900. I need to find the<br>
>> > methods<br>
>> > and signals related to the hardware, for example, HAL (especially the<br>
>> > objects under /com/nokia since it is somehow proprietary). However, I<br>
>> > couldn't find a detailed documentation on that. And I also used tools<br>
>> > such<br>
>> > as mdbus2, but since it lacks documentation and so does DBus itself, I<br>
>> > couldn't figure out how to do the introspection to find the information<br>
>> > I<br>
>> > want. Anyone knows how to find that? Thanks!<br>
>> ><br>
>><br>
>> You'll get more information if you specify *what* interface you're<br>
>> trying to figure out. The best way I found for me was looking, using<br>
>> strings, in a library that calls a D-Bus method, finding the name of<br>
>> that method call and working out its arguments by trial and error.<br>
>><br>
>> Graham Cobb's<br>
>> <a href="https://garage.maemo.org/plugins/wiki/index.php?Tools&id=1106&type=g" target="_blank">https://garage.maemo.org/plugins/wiki/index.php?Tools&id=1106&type=g</a><br>
>> may also be of help.<br>
>><br>
>> Best regards,<br>
>> Faheem<br>
><br>
><br>
</div></div><div><div></div><div class="h5">> _______________________________________________<br>
> maemo-developers mailing list<br>
> <a href="mailto:maemo-developers@maemo.org">maemo-developers@maemo.org</a><br>
> <a href="https://lists.maemo.org/mailman/listinfo/maemo-developers" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br>
><br>
><br>
</div></div></blockquote></div><br>