.
Correct. Maybe I'm prematurely optimizing here. Just go ahead with your
original proposal and lets see how it works out.
If it will be slow over system bus, we can simply redesign it to
pear-to-pear communication which uses system sockets.
Agreed.
Regards,
:M:
--
Michael 'Mickey
* What is the recommended method of accessing the vibrator in user
space?
The dialer shouldn't do that. It rather should use the aforementioned
event API.
* How are network services such as call waiting going to be
implemented?
* How is gsmd going to deal with multiple
Thomas Seiler wrote:
[...]
Thanks Thomas [to both of you ;)], that's pretty close to my
vision of how the OpenMoko system services architecture should look
like (at least considering the phone services, I want to do similar
with Device I/O services and PIM services).
This is extensible (new
-driven.
Please use the list openmoko-devel instead.
Thanks!
Regards,
:M:
--
Dr. Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de
