Hi Kyle / Tony / Rohit. As per my understandings,
HAL Plugins: tel-plugin-vmodem tel-plugin-imcmodem Modem Plugin: tel-plugin-atmodem tel-plugin-imc Points to note: 1. HAL plugin has high priority as compared to Modem plugin. This means, HAL plugin will be loaded by telephony-daemon before Modem plugin. 2. Every HAL has a corresponding name associated with it. 3. When modem plugin loads, it scans all the available HAL's and tries to correlate to a particular HAL based upon it's name (refer on_init() in tel-plugin-imc) As far as to "start" development of Telephony on AP side, I don't think anything else other than reading libslp-tapi / tel-plugin-dbus_tapi / libtcore / telephony-daemon / tel-plugin-imc / tel-plugin-imcmodem is required. I am not aware about the CP code. Take any one of the following: If you are reading tel-plugin-atmodem, the correspoding HAL is tel-plugin-vmodem and If you are reading tel-plugin-imc, the correspoding HAL is tel-plugin-imcmodem Let me know if you find anomalies in my understanding. Regards -- Gaurav Kalra Mobile: +91-9916-18-99-66 Facebook: /gauravkalra Twitter: @gvkalra On Mon, Dec 10, 2012 at 8:52 AM, Tzeng, Tonny <[email protected]> wrote: > I think tel-plugin-atmodem is a modem plugin, which talks to > tel-plugin-vmodem (the HAL plugin), and exposes modem functions to the > tel-plugin-dbus_tapi (the dbus communicator) for Tizen emulator. FYI. _______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
