Hi, On Tue, Oct 7, 2014 at 7:06 AM, Gowtham Anandha Babu <gowtham.ab@xxxxxxxxxxx> wrote: > This patch-set implements MAP 1.2 MAS Instance feature. > > The patch 1,2,3 will handle the Client part(MCE). It passes > the PTS 5.3 test case:TC_MCE_MMI_BV_01_I. > > The patch 4,5,6 will handle the Server part(MSE). It passes > the PTS 5.3 test case:TC_MSE_MMI_BV_02_I. > > Gowtham Anandha Babu (6): > doc/obex-api: Add description about MASInstance request > test/map-client: Add D-Bus API support to make MASInstance request > obexd/client/map: Add API Calls for request and handlers for response > obexd/mas: Add support for providing MASInstance Info as response > obexd/messages: Add prototypes for MASInstance response > obexd/message-dummy: Add MAS Instance description to response > > doc/obex-api.txt | 6 +++ > obexd/client/map.c | 88 ++++++++++++++++++++++++++++++++++++++++++ > obexd/plugins/mas.c | 62 +++++++++++++++++++++++++++++ > obexd/plugins/messages-dummy.c | 18 +++++++++ > obexd/plugins/messages.h | 16 ++++++++ > test/map-client | 9 +++++ > 6 files changed, 199 insertions(+) > > -- > 1.9.1 My plan is to actually do this as the name of the folder for each instance: <MAS 1 info>/telecom/... <MAS 2 info>/telecom/... If there is no info, due to version or lack of support, then we fallback to record description or something like that so we can support multiple instances. -- Luiz Augusto von Dentz -- 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
