Patrik
> -----Original Message-----
> From: Patrick Ohly [mailto:[email protected]]
> Sent: Monday, November 17, 2014 11:47
> To: Xu, Martin
> Cc: Kis, Zoltan; [email protected]
> Subject: Re: [Dev] discuss on NTB
I'd like to use this mail to summarize our discussion, and end our debate. :)

Firstly, from technical point, we do not have any disagreement with each other.

Secondly, so as to the understand of phrase 1 Multi-user requirement, we are 
also learning it, as I said before, currently, the feedback from Dominique's 
team is that it works fine. But I still need to get confirmation. The Phrase 1 
support is the requirement Tizen-3.0 common team. I need to do that to make 
sure NTB can be integrate into Tizen-3.0

Third, I hope you know I do know the issues you mentioned to current Bluetooth 
framework even Tizen. Myself and my team spent a lot of efforts and trying our 
best to resolve them. We worked very closely with Samsung and Comms upstream, 
we have our plan and strategy, but we need to step by step to do that. Just 
like Dominique has summarized, we need to sync with upstream, we need to sync 
with Samsung. It is not easy, but we are trying our best to push things 
forward. NTB-0.2 has resolved some of the issues, and the following release 
will continue to address the other issues. But before that we must push NTB 
into Tizen-3.0, that is our first priority task. And you know after long time 
work with Samsung comms team, they also agree to work with us to merge NTB into 
Tizen-3.0.

So as to TCT test, through that test I want to show People, we have finished 
all the Tizen existing CAPI, that is all we are working on and the target for 
the first step work plan.

And so as to the feature missing on CAPI, you mentioned, that is the different 
task. And that is the CAPI issue itself. But we are quite glad to work with 
people on it, that is also our goal to deliver a perfect Tizen Comms stack.

Thanks! 
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to