All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcus Redeker <marcus@openremote.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Szymon Janc <szymon.janc@tieto.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: Device class not writeable via dbus
Date: Thu, 16 Apr 2015 12:08:56 +0200	[thread overview]
Message-ID: <20F8C232-B06F-4723-8B1A-6E60A14E3B68@openremote.org> (raw)
In-Reply-To: <CABBYNZKtkTp2-VuP8oEiiKm7AV1n190bcXNXiGjggUWF7w4-Pw@mail.gmail.com>


> On 16.04.2015, at 11:36, Luiz Augusto von Dentz <luiz.dentz@gmail.com> wrote:
> 
> Hi Marcus,
> 
> On Thu, Apr 16, 2015 at 11:53 AM, Marcus Redeker <marcus@openremote.org> wrote:
>> 
>>> On 16.04.2015, at 10:15, Luiz Augusto von Dentz <luiz.dentz@gmail.com> wrote:
>>> 
>>> Hi Szymon, Marcus,
>>> 
>>> On Thu, Apr 16, 2015 at 11:01 AM, Szymon Janc <szymon.janc@tieto.com> wrote:
>>>> Hi Marcus,
>>>> 
>>>> On Thursday 16 of April 2015 09:09:28 Marcus Redeker wrote:
>>>>> 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?
>>> 
>>> It is possible to change at runtime by using systemd hostname plugin
>>> then change the org.freedesktop.hostname1.Chassis property, but Im not
>>> sure how easy is to change that. Anyway the point is that this should
>>> not changed by applications at will as it could break discovery
>>> filtering, even thought filtering by class is probably broken by
>>> design.
>>> 
>>> --
>>> Luiz Augusto von Dentz
>> 
>> This would allow to change the name of the bluetooth adapter but not the device class.
>> The name can already be changed using the read/write alias property which is no problem.
> 
> Looks like you know more than us how BlueZ works, perhaps you want to
> tell me what is this code for:
> 
> http://fpaste.org/211586/76181142/
> 
> Btw, BLE don't really have a class it has appearance which is not
> quite the same, we may actually have a different property for
> appearance along with a main.conf entry to set it and also a
> conversion from chassis to appearance.
> 
> 
> 
> -- 
> Luiz Augusto von Dentz

Sorry, if I stated something wrong. I did not check the BlueZ code.
I don’t know BlueZ at all and I am just trying to look at it from a user prospective who is trying to use dbus and BlueZ to create an application.

Looking at the complete file hostname.c, I can see that changing the Chassis property would indeed change the device class but only to predefinded values desktop, server, laptop, handset and tablet.
I will not be able to use it to change to HID device class 0x000540

-Marcus

  reply	other threads:[~2015-04-16 10:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 19:03 Device class not writeable via dbus Marcus Redeker
2015-04-16  6:48 ` Szymon Janc
2015-04-16  7:09   ` Marcus Redeker
2015-04-16  8:01     ` Szymon Janc
2015-04-16  8:15       ` Luiz Augusto von Dentz
2015-04-16  8:53         ` Marcus Redeker
2015-04-16  9:36           ` Luiz Augusto von Dentz
2015-04-16 10:08             ` Marcus Redeker [this message]
2015-04-16 10:35               ` Luiz Augusto von Dentz
2015-04-16  8:44       ` Marcus Redeker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20F8C232-B06F-4723-8B1A-6E60A14E3B68@openremote.org \
    --to=marcus@openremote.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=szymon.janc@tieto.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.