* Any plan to make telephony backend changeable in runtime?
@ 2010-04-27 6:54 Zhu Yanhai
2010-04-27 9:42 ` Johan Hedberg
0 siblings, 1 reply; 2+ messages in thread
From: Zhu Yanhai @ 2010-04-27 6:54 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Liu, Bing Wei, Martin Xu, Zhu, Peter J, Zhang, Vivian
Hi,
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?
Thanks,
Zhu Yanhai
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Any plan to make telephony backend changeable in runtime?
2010-04-27 6:54 Any plan to make telephony backend changeable in runtime? Zhu Yanhai
@ 2010-04-27 9:42 ` Johan Hedberg
0 siblings, 0 replies; 2+ messages in thread
From: Johan Hedberg @ 2010-04-27 9:42 UTC (permalink / raw)
To: Zhu Yanhai
Cc: linux-bluetooth, Liu, Bing Wei, Martin Xu, Zhu, Peter J,
Zhang, Vivian
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-04-27 9:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-27 6:54 Any plan to make telephony backend changeable in runtime? Zhu Yanhai
2010-04-27 9:42 ` Johan Hedberg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).