Hi,
@ Mikko
Thanks for your immediate reply.
The bluetooth-frwk is already supporting mobile, IVI, TV, wearable, etc.
It means the bluetooth-frwk is suitable and sole solution for Tizen:common.
@ Zheng Wu
For this reason, I don't encourage to merge NTB code now in Tizen:common (tizen branch).
Regards,
Seungku
------- Original Message -------
Sender : Ylinen, Mikko<[email protected]>
Date : 2014-12-23 13:54 (GMT+09:00)
Title : Re: [Dev] [Tizen 3.0] bluetooth-frwk / NTB
Hi,
On Tue, Dec 23, 2014 at 4:43 AM, 김승구 <[email protected]> wrote:
@ 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
|
|
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
