| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
CALLBACK_WITH_FAILURE used data structure freed just beforehand
|
| | |
|
| |
|
|
|
|
|
|
| |
It was a cause of confusion for little gain to have separate
functions for registering profiles with extra information, for
example "role" and "features". We remove those helper functions
in favor of a single one with more parameters, "role" and
"feature" when NULL, will be ignored.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This patch glues together the dundee driver interface with the
D-Bus Profile1 interface.
When the dundee driver requests a connection, it will call the
Device1's ConnectProfile.
|
| |
|
|
|
|
|
| |
This patch declares the external dundee Profile handler. It
contains the initial implementation of the D-Bus Profile1
interface and methods responsible for handling Bluetooth
connections.
|
| |
|
|
|
| |
This patch adds the dundee device struct to the our Bluetooth
device representation.
|
| |
|
|
|
| |
This patch adds the functions to be called when the dundee will
connect or disconnect with a Bluetooth device.
|
| |
|
|
|
| |
When a bluetooth device property change and this property is Alias,
we need to refresh our representation of this device.
|
| |
|
|
|
| |
This patch tracks the GDBusProxy for Bluetooth devices in order to
be able to get their properties.
|
| |
|
|
|
| |
This patch adds a hash that will store every known bluetooth
device that implements DUN service.
|
| |
|
|
|
| |
This patch adds callbacks to track additions of BlueZ related
interfaces.
|
| |
|
|
| |
This patch adds the BlueZ 5 support file for dundee.
|
| |
|
|
|
| |
The BlueZ 4 support file for dundee has now been renamed to
bluez4.c to make it easier to add a BlueZ 5 support file.
|
| |
|
|
| |
This typo was preventing dundee from sending the signal.
|
| |
|
|
|
|
|
|
|
|
| |
As BlueZ 5 introduced backwards incompatible API changes, and we want to
keep support for BlueZ 4 based plugins for some time, we need to separate
the plugins that are based on BlueZ 4 from the ones based on BlueZ 5.
The bluetooth.c plugin has now been renamed to bluez4.c and the hfp_hf.c
plugin is renamed to hfp_hf_bluez4. This will make it easy to add a
HFP HF plugin for BlueZ 5.
|
| |
|
|
|
|
|
| |
By default, both stderr and syslog messages go to the systemd journal,
which results in duplicate messages being logged.
Thanks to Vinicius Costa Gomes for pointing out this problem.
|
| |
|
|
|
|
| |
If the ATD*99# dial fails for some reason, NO CARRIER, for example, we
need to disconnect the bluetooth link and do further clean up on
disconnect_callback().
|
| |
|
|
|
|
|
| |
If we do not shut it down the fd can remain opened. This make impossible
to try a re-connect: busy is returned in this case.
We call shutdown here to make sure that the link is always closed.
|
| |
|
|
|
| |
If something goes wrong the PPP handshake can stall, then we just add a
timer to return an error after a certain timeout (15 seconds).
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
