Something else that came into my mind is the use of the init system and Android system properties.
We currently only support the Android init scripts. Bluetooth starts and stops its system service on demand. That code is currently being moved into the HAL module in bug 1232687. [1] If you want to do something similar, you should implement this HAL interface for your Linux init system, probably systemd. The Android system properties are read and written with |property_get| and |property_set|. [2] If you need such functionality, you could work around this for now by implementing them for plain Linux. A preferable solution would be another HAL interface around the functionality. I don't know the optimal solution for Linux, but calling dconf via D-Bus seems like a viable option. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1232687 [2] https://android.googlesource.com/platform/system/core/+/master/include/cutils/properties.h Am 17.12.2015 um 11:30 schrieb Pierre-Eric Pelloux: > Hi All, > > I'm starting an exploratory project: using b2g on a laptop machine > (think Chromebook). > > I plan to use bug 731498 as a starting point for basically > implementing Gonk for a non-Android Linux. > After updating/rebasing these patches I believe some of them could > even be merged. > > This work could also be used as a test bed for the ideas shown in > Orlando presentation "The Future of Gonk". > > Thoughts? > (feel free to ping me to discuss this, irc nick: pepp) > > Pierre-Eric > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
