On Thursday 25 November 2010 10:23:10 ext Johan Hedberg, you wrote: > > This becomes a problem if we have more than one application "managing" > > voice calls. And I expect that will _be_ the most common case. You have > > the main call UI, but you also have the Bluetooth headset/carkit, the > > USB AT commands port, and possibly some third party call applications. > > Right. At least for HFP the call direction needs to be in the AT+CLCC > reply. I.e. if the bluetoothd ofono telephony driver is used and > bluetoothd starts after one or more calls are already in progress > bluetoothd wouldn't have seen the call setup process and therefore not > know the direction of the call (without this property).
Yeah. For USB CDC ACM gadget functionality, there is basically the same problem. Because oFono assumes it has full control over the modem, most cellular commands have to go through the oFono D-Bus API. However, a number of other commands talk to completely different stuff, including but not limited to: * AT+CBC et al deals with energy management, which is proprietary in Nokia's case and hence cannot be reached from GPL'd oFono. * AT+CKPD, AT+CTSA and friends use either Linux uinput driver or perhaps to the windowing framework (X11, Wayland?). * AT+CBKLT is hooked to the screensaver whatever takes care of it. * AT+CPBR and friends is hooked to the phonebook, which is Qt-based, and therefore inadequate inside oFono. * At Nokia, we also have some non-standard commands for internal use. * Some operators require some funky AT commands of their own. It might not be possible to open-source them, even if we want to. I would like to emphasize that, even if many of those commands are mostly if not only used in testing, they may still need to cooperate with oFono and/or to be present in the end-user devices. Besides, duplicating the implementation effort inside and outside oFono would be a waste of time. All in all, implementing the AT commands DCE emulator inside oFono is not a realistic option. That is not to say that it must be closed-source, at least not most parts of it, but it's going to (have to) talk D-Bus to oFono. -- Rémi Denis-Courmont Nokia Devices R&D, Maemo Software, Helsinki _______________________________________________ ofono mailing list [email protected] http://lists.ofono.org/listinfo/ofono
