Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Marcus Redeker <marcus@openremote.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Device class not writeable via dbus
Date: Thu, 16 Apr 2015 10:01:06 +0200	[thread overview]
Message-ID: <5181722.aJ0IxrIXHx@uw000953> (raw)
In-Reply-To: <A1432115-C15B-4A07-BB90-E6A731C20B3B@openremote.org>

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?

PS
Please don't top post on ML.

> > 
> > 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.
> > 
> > 
> 

-- 
Best regards, 
Szymon Janc

  reply	other threads:[~2015-04-16  8:01 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 [this message]
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
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=5181722.aJ0IxrIXHx@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcus@openremote.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox