Re: [Dev] [Tizen 3.0] bluetooth-frwk / NTB

Mon, 22 Dec 2014 18:44:35 -0800

Title: Samsung Enterprise Portal mySingle

@ 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.

 

>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?

 

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.

 

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?

 

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

Reply via email to