Hi Lizardo, On Fri, Nov 04, 2011, Anderson Lizardo wrote: > Following a previously sent RFC, this series implement an internal API that > simplifies GATT service registration on server implementations. It is built on > top of current "low level" attribute API, and both can be used at the same time > without problem. > > It is currently being used for Phone Alert Status and Time profile server > implementations which we are preparing to send upstream (we previously sent RFC > patches for both of them). > > As an example, I converted a service from the GATT example profile (see patch > #4). Note the migration to this API is optional, and can be done incrementally. > > Still not implemented (but can be added later): > > * No support for aggregate format descriptors, included services (also we don't > have any example services using them) > * No support for some GATT descriptors > * No support for "static" characteristic values. Any readable or writeable > characteristic needs a corresponding read or write callback 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
