Re: Device class not writeable via dbus

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>> 
>>> You can configure CoD in main.conf
>>> [General]
>>> Class = 0x000100
>>> 
>>> Note the comment that only major and minor bits are considered. Service bits 
>>> are dynamically configured based on registered services.
>>> 
>>> 
>> True, but  I would like todo that through dbus and not manually and have to restart bluetoothd afterwards.
>> Any chance this can be done in the near future?
>> -Marcus
> Class of Device is rather static configuration as those describe form factor
> and that usually doesn't change.
> 
> Why do you need to change CoD on the fly?
> 
> PS
> Please don't top post on ML.
> -- 
> Best regards, 
> Szymon Janc

For home automation sometimes our home controller acta as a virtual keyboard and some devices need the coresponding major/minor device class or else they don’t show them during discovery.
Another user might wants to use his home controller to control bluetooth LE lights which are coming out more and more.
Or maybe Bluetooth LE (GATT) does not need the device class anymore ?
—Marcus

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux