Hi Arik, On Wed, Feb 1, 2012 at 6:48 PM, Arik Nemtsov <arik@xxxxxxxxxx> wrote: > Hey Anderson, > > On Fri, Dec 2, 2011 at 20:34, Anderson Lizardo > <anderson.lizardo@xxxxxxxxxxxxx> wrote: >> This series implements two new features for GATT Time Profile (server role): >> >> * Reference Time Update Service (RTUS), with two drivers (called "providers" >> here): dummy (for testing) and timed (for N9/harmattan) >> * Support for current time notifications > > This series looks good overall. Are you planning to go ahead with it > (with a non-RFC series)? Sure. This will happen in the very near future (at most next week). But for now we will drop the "providers" patches, because we are about to also send D-Bus API that implements the functionality externally. But even with the initial implementation, most Time clients will be supported just fine. They will just not be able to update the phone's own time or be notified of manual changes to the phone time (this will be supported with the D-Bus API). >> We are aware of the current plan of moving platform specific code out of BlueZ >> (to agents communicating over D-Bus). Is it feasible to be done now for GATT >> servers as well? > > It seems this is handled well in your series. Or did you want to move > some more functionality to D-Bus? We plan to have everything which was in "providers" implemented on external a Agent which communicates over D-Bus. This is necessary to avoid introducing extra dependency on BlueZ for each platform we may support. We will send a RFC for this Time Agent API real soon. Please comment :) Best Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil -- 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
