Hi Radoslaw, >-----Original Message----- >From: linux-bluetooth-owner@xxxxxxxxxxxxxxx [mailto:linux-bluetooth- >owner@xxxxxxxxxxxxxxx] On Behalf Of Radoslaw Jablonski >Sent: 09 September 2010 13:47 >To: linux-bluetooth@xxxxxxxxxxxxxxx >Subject: MAP implementation status > > > Hi all, >We plan to start implementation of Message Access Profile Server as >obexd plugin. Before we start with coding part I need to check if >someone else started implementing MAP Server, MNS Server of Map client. >If some code is already available, then we could combine our forces to >add MAP support for OBEXD. This is something I've been focusing on recently. Attached is my modest start to this. My initial strategy - even though its IVI client side I'm most interested in - was to tackle server side, essentially bring up both sides of the interface incrementally. I was going to employ a strategy of, instead of doing it in big bulk, dropping small unobtrusive patches into the trunk, so interested people could see and contribute to the activity. I'm struggling in defining the right level of patch to upstream - maybe folks here can comment on the attached - is it of acceptable substance or would more meat be require to make it a meaningful contribution? I've taken on board the suggestion from Marcel and Johan to focus on SMS data first. That makes sense to me. Hope the above and attached is of use. Looking forward to hearing from you - any thoughts/insights/criticism are most welcome. Regards Tom -------------------------------------------------------------- Intel Shannon Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 Business address: Dromore House, East Park, Shannon, Co. Clare This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
Attachment:
0001-Initial-intro-for-MAP.patch
Description: 0001-Initial-intro-for-MAP.patch
