Claudio, > -----Original Message----- > From: Claudio Takahasi [mailto:claudio.takahasi@xxxxxxxxxxxxx] > Sent: Friday, March 16, 2012 9:44 PM > To: Ganir, Chen > Cc: BlueZ development; Anderson Lizardo > Subject: Re: [PATCH v3 0/3] GATT: Change the way GATT Plugins are > enabled/disabled > > Hi Chen Ganir, > > On Wed, Mar 14, 2012 at 8:31 AM, Anderson Lizardo > <anderson.lizardo@xxxxxxxxxxxxx> wrote: > > Hi Chen, > > > > On Wed, Mar 14, 2012 at 7:16 AM, <chen.ganir@xxxxxx> wrote: > >> From: Chen Ganir <chen.ganir@xxxxxx> > >> > >> This patch set is a result of the discussion on the #bluez channel. > >> > >> Consolidate the --enable_<profile> for gatt profiles into a single > >> switch, called --enable_gatt. > >> > >> In addition, modify the AttributeServer propery in the main.conf to > >> EnableGatt option (default=false) and make sure all GATT plugins > query > >> this option before trying to load (in the _init function of the > >> plugin) > >> > >> This is v3 of the patch set - fixed as suggested on the mailing > list. > > > > Looks good to me. > > > > Regards, > > -- > > Anderson Lizardo > > Instituto Nokia de Tecnologia - INdT > > Manaus - Brazil > > How are you planning to enable/disable HoG? > IMO, the input D-Bus API needs to be aligned, it should be the same > for HID over BR/EDR and HID over GATT. > > The point is: should "--disable-input" disable HoG also? > HOG Should be dependent on both --enable-gatt and --disable-input. You can not have HOG if input is disabled, or if gatt is disabled. > BR, > Claudio. Thanks, Chen Ganir ��.n��������+%������w��{.n�����{��� �^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
