From: Radek (Fotopiper) <fotopiper@o2.pl>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Device class in hcid.conf - Problems setting the correct description of the device.
Date: Sun, 8 Jul 2007 00:09:09 +0200 [thread overview]
Message-ID: <20070708000909.7be17b99@localhost> (raw)
In-Reply-To: <1183622873.6351.79.camel@aeonflux.holtmann.net>
On Thu, 05 Jul 2007 10:07:53 +0200
Marcel Holtmann <marcel@holtmann.org> wrote:
> > I've set the class for my Linux devices a while back (a year or two
> > back), but then the list was easily available. Still the operation wasn't
> > fast - the specs describe the class bit by bit... which a bit differs form
> > the way hcid.conf require it to be put.
> > Did somebody found a easy way to set up the device class?
>
> you can use the D-Bus interface. Especially the SetMinorClass() method.
Thank you very much! :)
I'm starting to appreciate Bluez migration to dbus.
For those who are less eager to learn the dbus ;)
$ dbus-send --system --print-reply --dest=org.bluez /org/bluez/hci0
org.bluez.Adapter.SetMinorClass string:"laptop"
hciconfig hci0 class
and input the class into hcid.conf
Or stick with d-bus interface.
My best regards.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-07-07 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 13:55 [Bluez-users] Device class in hcid.conf - Problems setting the correct description of the device Radek
2007-07-05 8:07 ` Marcel Holtmann
2007-07-07 22:09 ` Radek [this message]
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=20070708000909.7be17b99@localhost \
--to=fotopiper@o2.pl \
--cc=bluez-users@lists.sourceforge.net \
/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.