Re: [PATCH BlueZ 0/2] Initial Time Profile implementation

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

 



Hi Lizardo,

On Fri, Nov 04, 2011, Anderson Lizardo wrote:
> This initial implementation for Time Profile contains the mandatory Current
> Time Service (CTS), including the mandatory Current Time Characteristic and the
> optional Local Time Information Characteristic.
> 
> The only limitation is that notifications for the Current Time Characteristic
> value are not being sent yet. The mechanism to detect changes on the system
> time is platform specific, therefore we need more infrastructure to support
> this and allow multiple platform support.
> 
> Future patches will address this (and also make sure the notifications enabled
> by clients are persistent across reboots), and we will also introduce Reference
> Time Update Service (which also depends on platform specific mechanisms.)
> 
> This series depend on the "High level GATT API for service registration" series
> sent a while ago. Note that, despite the limitation explained above, we
> consider this code ready for upstream inclusion (it is mandatory for server to
> implement it, but not mandatory for the client to enable the notification, it
> can just read the current time on each connection.)

Applied. Thanks.

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


[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