> You should write an ofono plugin to properly initialize the 3rd party
> hardware instead. This way, you don't need to start up anything
> manually, get rid of the dependencies, and the ofono plugin can
> actually restart/monitor the service, making your part of the stack
> much more reliable.
We can't. There are other services that must access this hardware also,
and completely independently from ofono. The multiplexing daemon
handles all of that arbitration and startup synchronization.
> What if your hardware isn't available to the system before ofonod starts?
this piece of hardware is available before the CPU even comes out of
reset.. non-issue..
> With delayed device initialization, this may very well be the case.
> What if your daemon needs to be restarted?
"/etc/init.d/foo restart" would be handy. tho your now dealing with
broken sockets in a dozen places. What if ofono needs to be restarted?
-p.j.
>
> Auke
>
--
P.J. Bostley
[email protected]
Qualcomm Innovation Center Inc. is a member of the Code Aurora Forum
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
