[PATCH 0/6] Move Attrib client (including: should we disconnect or not?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

The move itself is pretty simple, but when implementing it, I took a decision
and I would like to hear your opinion about it.

With this patch series, the behaviour is that we never disconnect from
a LE device unless we are told so, i.e. org.bluez.Device.Disconnect(),
is that what is expected from us?


Cheers,
--

Vinicius Costa Gomes (6):
  Move Attrib client to the core
  Register Attrib interface when loading device from storage
  Register Attrib interface after Primary Service discovery
  Remove _init and _exit methods from Attrib client
  Add support for re-using the attrib channel
  Fix disconnecting when primary service discovery is done

 Makefile.am      |    4 ++--
 attrib/client.c  |   49 ++++++++++++++++++-------------------------------
 attrib/client.h  |    6 +++---
 attrib/manager.c |   47 -----------------------------------------------
 src/adapter.c    |    5 +++++
 src/device.c     |   20 +++++++++++++-------
 6 files changed, 41 insertions(+), 90 deletions(-)

--
1.7.4.1

--
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


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux