Hi Wu,
NTB is currently not applied by any profile.
So, in my opinion, we don't need to maintain dual-stack at this time
.
Please also consider the below thread.
Thanks,
Seungku
@ Mikko
IMO, 'nothing for T:C' is not an option.
[Kim] Does it mean Tizen:common is mandatory for Tizen 3.0?
Tizen Common is the base for all profiles and Tizen bluetooth framework/stack
needs to be such that all profiles can use what's in common.
It should be noticed NTB is by no means IVI specific work. The original goal (or one of them)
of bluetooth-frwk NG (i.e., 'NTB') was to re-implement Tizen bluetooth-frwk to
support easier integration of profile specific functionality.
As I wrote earlier, the next IVI release will use 'bluetooth-frwk'. Corentin has done
a lot of fixing to get Tizen BT Web API to work with BT CAPI + bluetooth-frwk. Because of
this, there's no push from IVI to get NTB integrated.
"dual stack" and "nothing for T:C" are not options. We need to have a single solution
and have it integrated in T:C first.
-- Mikko
------- Original Message -------
Sender : Zheng, Wu<[email protected]>
Date : 2014-12-26 18:57 (GMT+09:00)
Title : RE: RE: [Tizen 3.0] bluetooth-frwk / NTB
Hi Kim,
Please check the following points. Thanks.
Zheng Wu
From: 김승구 [mailto:[email protected]]
Sent: Tuesday, December 23, 2014 10:44 AM
To: Zheng, Wu
Cc: 전태수; 편도현; 바가바; 우태진; 정지훈; Xu, Martin; [email protected]; Jia, Pei P
Subject: Re: RE: [Tizen 3.0] bluetooth-frwk / NTB
@ Mikko
IMO, 'nothing for T:C' is not an option.
[Kim] Does it mean Tizen:common is mandatory for Tizen 3.0?
@ Wu
Hi Kim,
Thanks for you to pay attention to the status of NTB.
The following points are my answer.
>1. Is NTB decided to be in Tizen:IVI?
To my knowledge, In the plan of IVI, NTB will be used. At current, NTB can’t be used for Tizen;IVI in Tizen 3.0.
We are trying to fix the related issues of Tizen:IVI in Tizen3.0. So that NTB can be accepted for Tizen;IVI in Tizen 3.0.
[Kim] From Mikko's thread, it will not be included in the next IVI release.
IVI 14.4 is targeted to be released soon. As time is limited, IVI 14.4 will not adopt NTB. But in the long run, NTB will keep readiness for active profiles, including but not limited to IVI.
>2. Is NTB planning to be in Tizen:common?
1. To my knowledge, In the plan of Tizen:Common, NTB will be used. However, at current, NTB can’t be enabled in Tizen:Common.
You have suggested that NTB will be merged to platform/core/api/bluetooth with a Marco to split the current bluetooth package and NTB. We think that it is feasible solution for dual stack. We will accept the solution. (Thanks for your suggestion).
[Kim] We first have suggested this, but Martin did not agree on this suggestion. Can you please check this?
I have talked the topic with Martin. The suggestion can be accepted.
2. Therefore, NTB will be merged to platform/core/api/bluetooth with a Marco to implement dual stack.
[Kim] I think it would be better to merge NTB after confirming Tizen bluetooth direction and deciding to be in IVI release.
For Tizen Bluetooth, we think we (Intel and Samsung team) discussed this lots of times in the past. To me, the goal is to have an unified solution to provide better support to different profiles and emerging features. The initiative we are working on NTB is to solve problems like we need more simple Bluetooth-Frwk design and support multi-user mode and so on. We don’t think NTB is already perfect and fully error-free, but, as the design goal describes, it could help to solve some real problems we are facing today.
For NTB integration, we think it’s the appropriate time to do this so in Tizen 3.0 we have more flexibility to adapt to different requests. Also, please note we have taken long time to do stabilize work and pass TCT test, so NTB is ready now.
At the same time, according to our plan and NTB integration solution(we (Intel and Samsung team) have discussed it for a long time), NTB should be merged at this time to match the related milestone in our plan too.
3. At current, the Marco will not be default enabled. Therefore, NTB will not be enabled in Tizen Branch too. It will not impact any feature and platform.
We will continue to develop NTB in platform/core/api/bluetooth to match the related requirements.
After matching the related requirements, the Marco will be default enabled and NTB will be default enabled in Tizen branch too.
[Kim] If it will not be used for next Tizen:IVI release, I don't think NTB code need to be merged in Tizen branch.I think developing in devel branch is more rational until NTB is decided to be included in Tizen:IVI release (or other profile release). At that time, we can tell Tizen bluetooth is supporting dual stack, isn't it?
As I mentioned earlier, the target of NTB is not to provide dedicated support to IVI or specific profile only, so I can’t see any reason to narrow/bind NTB usage with a specific profile.
Any suggestion? Thanks.
Best Regards
Zheng Wu
Regards,
Seungku
From: 김승구 [mailto:[email protected]]
Sent: Monday, December 22, 2014 2:26 PM
To: Zheng, Wu; [email protected]
Cc: 전태수; 편도현; 바가바; 우태진; 정지훈; Xu, Martin
Subject: [Tizen 3.0] bluetooth-frwk / NTB
Dear Mr. Zheng Wu,
As we already know, bluetooth for Tizen 3.0 is agreed to be dual stack(bluetooth-frwk/NTB) architecture. I have several questions regarding this. Would you please give your opinion about below questions?
1. Is NTB decided to be in Tizen:IVI?
I could see some reported issues regarding IVI NTB at [email protected]. So, I want to know Intel has confirmed to use NTB for TIzen:IVI in Tizen 3.0.
2. Is NTB planning to be in Tizen:common?
From "[Dev] NTB-0.3 has released", I could see "NTB-3.0 has been release and is ready for integration into Tizen-3.0 common". However, NTB is not currently supporting mobile profile as well as wearable profile, so I think it cannot be Tizen:common (please refer https://wiki.tizen.org/wiki/Common). In my opinion, bluetooth-frwk for Tizen:mobile, NTB for Tizen:IVI, and nothing for Tizen:common are appropriate solution for the dual stack because no stack is supporting every profile (e.g., mobile, IVI, wearable, etc.).
Based on your answer, I will suggest the specific plan for bluetooth dual stack such as git repository, branch, etc.
Regards,
Seungku
|
|
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
