A few days gone by, and endless wrestling with git wherein I was not able to push code. Turned out, I was using the wrong URL to push ..doh!
But anyway, the code is beginning to stabilise a bit (Read no unexpected segfaults, only expected ones..). The last few days were spent in changing the method names in accordance with OTAPI naming conventions after my mentor went through my code.
There is also another important change. The sysfs nodes for backlight and power plugins were hardcoded in their configuration files. So, I came up with some helpers that creates DBus paths automatically based on the device class which they belong to. Here’s a picture of today’s code in action,
Notice the d-feet DBus debugger towards the lower left? It shows all the automatically created DBus object paths based on the device class which the plugin stands for. And the terminal to the right shows some debug messages. Note how odeviced spits out the current battery status viz. “Charging, Discharging”. The corresponding “battery-status-changed” DBus signal is emitted as well (along with “low-battery-warning” signal which *ahem* is emitted when battery is low).
For more follow this thread..
Filed under: FOSS and Linux, Logs, embedded, freesmartphone.org, gsoc, linux, neo1973, odeviced, openmoko | Leave a Comment
Tags: openmoko, neo1973, gsoc, odeviced, freerunner, dbus, freesmartphone, fso, freesmartphone.org
No Responses Yet to “odeviced: More sysfs abuse (Screenshot attached! :P)”