Hi Luiz, On Tue, Jan 19, 2010, Luiz Augusto von Dentz wrote: > Also the problem with this being in the device path is that ofono may > not be registered as an agent on connect (both ways) which will cause > the connection to drop and the round trips to resolve device path only > makes it worse, if this happen to be on adapter path this would not be > a problem since we know before hand who to call. I don't think this is an issue in the case of a per-adapter handsfree agent. Typically the agent would be registered upon the creation of the device object. Yes, in theory a HFP connection establishment may occur before ofono manages to register an agent for the device but the connection doesn't need to be dropped because of it. Since it's the HF-role device (i.e. us) that sends the initial AT command in HFP SLC establishment bluetoothd could just sit quietly waiting until an agent registers itself. When an agent finally gets registered bluetoothd would (after replying to the registration method call) immediately call the NewConnection() method for the agent. Johan -- 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
