Hi Frederic, On Wed, Nov 23, 2011 at 5:58 AM, Frederic Danis <frederic.danis@xxxxxxxxxxxxxxx> wrote: > The new telephony D-Bus interface is just in charge of performing SDP > publication and RFComm connection. All Telephony related code is managed by > the agent (i.e. oFono). How t > I take a look to the Phone Alert Status and Alert Notification and I thought > that this should be implemented in the agent, or in a BlueZ service > accessible by the agent through D-Bus. I'm wondering what exactly has been discussed/decided on the BlueZ summit. Are we supposed to move everything "platform specific" to agents and remove all drivers from BlueZ? Are we okay with have BlueZ depending on multiple agents? Besides that, I think your proposed Telephony API is too tied to HFP/HSP. I think it is interesting to have a more generic API so that other telephony related profiles (e.g. LE ones) could reuse it without requiring their own agent based API. Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
