Hi Zheng Wu,
> >1/ there is a problem with NFC stack. > Okay, maybe it need some modification to match bluetooth-frwk. > Yes, tizen-extensions-crosswalk requires the NFC stack in order to offer the Tizen NFC Web API. If we move to NTB, NFC needs to be adapted to NTB. > > >2/ NTB daemon should be fired by org.tizen.comms.service activation. > >Do you work on using a specific bluetooth user to manage tizen bluetooth > stack ? > 1. Yes. I can use "guest" user to run it well on tizen common and I didn't > modify any configure. > 2. To tizen common, Of course, The dbus configure file need to be modified > to match the requirement of Tizen common. Not just for Common, for IVI as well... OK. Let's use "guess" user for the moment to check multi-user implementation. > > >3/ Bluez is blocked by RFkill. > Do tizen common use connman to enable/disable BT(including RFKILL)? > If so, I will modify the enable/disable BT. > Tizen Common will use NTB to enable/disable BT. If some user wants to enable/disable BT over bluez, he will have to previously unblock bluetooth rfkill by himself. NTB needs to include rfkill unblocking if needed. Best regards, Corentin > > >I'm wondering how did you test it on Common. Can you let me know ? > Using "guest" user to run NTB daemon. > Using "Alice" user to run Bluez-capi-test > At the same time, Using "Bob" user to run Bluez-capi-test too. > > Best Regards > Zheng Wu > > -----Original Message----- > From: Corentin Lecouvey [mailto:[email protected]] > Sent: Wednesday, October 29, 2014 12:34 AM > To: Zheng, Wu; Le Foll, Dominique; Xu, Martin; Jia, Pei P > Cc: [email protected] > Subject: Re: Multi-user BT wiki > > Hi Zheng Wu, > > I wanted to check NTB on Tizen Common and I met several problems : > > 1/ there is a problem with NFC stack. > nfc-manager-neard component depends on libbluetooth-api.so which is an > internal API inside bluetooth-frwk. > This package needs to be adapted to NTB in order to use core C API. > > 2/ NTB daemon should be fired by org.tizen.comms.service activation. > This service still depends on "app" user which is not in Common anymore. > NTB daemon can not be launched by dbus. > Do you work on using a specific bluetooth user to manage tizen bluetooth > stack ? > > 3/ Bluez is blocked by RFkill. > NTB would have to handle this. > In Common bluetooth is power off after booting, I can not enable it unless > I unblock bluetooth rfkill. > > I'm wondering how did you test it on Common. Can you let me know ? > > I will continue to review multi-user implementation. > > Best regards, > Corentin > > > > On 10/28/2014 02:50 AM, Zheng, Wu wrote: > > Hi all, > > > > NTB has implement the phase1 requirements of Multi-user BT. > > > > The following link is the related NTB wiki of Multi-user BT. > > > > https://wiki.tizen.org/wiki/NTB_Architecture#Multi-user_NTB > > > > Please check it. Thanks. > > > > Best Regards > > Zheng Wu > >
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
