Hi, On Tue, Apr 27, 2010, Zhu Yanhai wrote: > For the moment the telephony driver of BlueZ is chose by the > configure script (--with-telephony=xxx) and fixed after build. Is > there any plan to make it configurable during runtime? Actually the idea has been to remove the AT parsing (and therefore also the telephony driver) completely from the BlueZ side and instead just export the RFCOMM socket to an external telephony component. In most cases this would be ofono (it even has basic AT parsing support already) but e.g. android would benefit from this too since they could start using the device framework within bluetoothd and its D-Bus interface for HFP (right now they've got a completely separate thing for it). 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
