From: Radek (Fotopiper) <fotopiper@o2.pl>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Device class in hcid.conf - Problems setting the correct description of the device.
Date: Wed, 4 Jul 2007 15:55:27 +0200 [thread overview]
Message-ID: <20070704155527.63ef9dfa@localhost> (raw)
Hello Everybody,
I've just decided to set a correct device class on my Linux box (a
notebook to be exact) and I've come to unexpected problem - there is no
description of class (in hcid.conf man page the description is not complete, to
say the least).
I've looked up google and it seams that the "Assigned Number" list became
confidential (the page to which the pdf specification redirects is member-only on
bluetooth.org)
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?
My best regards to you all!
-------------------------------------------------------------------------
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
next reply other threads:[~2007-07-04 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 13:55 Radek [this message]
2007-07-05 8:07 ` [Bluez-users] Device class in hcid.conf - Problems setting the correct description of the device Marcel Holtmann
2007-07-07 22:09 ` Radek
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=20070704155527.63ef9dfa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox