* [Bluez-devel] inquiry_info device class to string
@ 2004-10-19 8:19 postmaster
2004-10-19 9:23 ` Stephen Crane
2004-10-19 11:03 ` Marcel Holtmann
0 siblings, 2 replies; 3+ messages in thread
From: postmaster @ 2004-10-19 8:19 UTC (permalink / raw)
To: bluez-devel
Hi there
Im sort of new to bluetooth and bt development but its going ok so far=2E =
Im
writing a little tool which displays all current devices in range=2E Since=
my
code uses ripped parts from hcitool scan i can succesfully enumerate the
device address and name, my question is , how do I parse the device_class=
item from the inquiry_info structure ? Say device ID is 001, i want to
convert it to an human readable string like 001 =3D=3D Phone, 002 =3D=3D A=
udio
etc=2E=2E=2E where can i find an translation list for this ? after a heavy=
google
battle i found a PalmOS site which mentions the bluetooth specs, but the
prop is , i can find only parts of it and my 'bluetooth unreveiled' book i=
s
currently beeing shipped to me (i hope its mentioned there)=2E I hope im n=
ot
forced to use a sdptool query since some 'light' devices dont have it
onboard, like headsets etc
thanks for the help !
Ed=2E
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web=2Ecom/ =2E
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bluez-devel] inquiry_info device class to string
2004-10-19 8:19 [Bluez-devel] inquiry_info device class to string postmaster
@ 2004-10-19 9:23 ` Stephen Crane
2004-10-19 11:03 ` Marcel Holtmann
1 sibling, 0 replies; 3+ messages in thread
From: Stephen Crane @ 2004-10-19 9:23 UTC (permalink / raw)
To: bluez; +Cc: bluez-devel
Hi,
On Tue, 2004-10-19 at 09:19, postmaster@spamzed.com wrote:
> Im sort of new to bluetooth and bt development but its going ok so far. Im
> writing a little tool which displays all current devices in range. Since my
> code uses ripped parts from hcitool scan i can succesfully enumerate the
> device address and name, my question is , how do I parse the device_class
> item from the inquiry_info structure ? Say device ID is 001, i want to
> convert it to an human readable string like 001 == Phone, 002 == Audio
> etc... where can i find an translation list for this ? after a heavy google
> battle i found a PalmOS site which mentions the bluetooth specs, but the
> prop is , i can find only parts of it and my 'bluetooth unreveiled' book is
> currently beeing shipped to me (i hope its mentioned there). I hope im not
> forced to use a sdptool query since some 'light' devices dont have it
> onboard, like headsets etc
See hciconfig.c in bluez-utils.
Cheers,
Steve
--
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bluez-devel] inquiry_info device class to string
2004-10-19 8:19 [Bluez-devel] inquiry_info device class to string postmaster
2004-10-19 9:23 ` Stephen Crane
@ 2004-10-19 11:03 ` Marcel Holtmann
1 sibling, 0 replies; 3+ messages in thread
From: Marcel Holtmann @ 2004-10-19 11:03 UTC (permalink / raw)
To: bluez; +Cc: BlueZ Mailing List
Hi Ed,
> Im sort of new to bluetooth and bt development but its going ok so far. Im
> writing a little tool which displays all current devices in range. Since my
> code uses ripped parts from hcitool scan i can succesfully enumerate the
> device address and name, my question is , how do I parse the device_class
> item from the inquiry_info structure ? Say device ID is 001, i want to
> convert it to an human readable string like 001 == Phone, 002 == Audio
> etc... where can i find an translation list for this ? after a heavy google
> battle i found a PalmOS site which mentions the bluetooth specs, but the
> prop is , i can find only parts of it and my 'bluetooth unreveiled' book is
> currently beeing shipped to me (i hope its mentioned there). I hope im not
> forced to use a sdptool query since some 'light' devices dont have it
> onboard, like headsets etc
it is not the Bluetooth specification directly. It is in the assigned
numbers document on the Bluetooth website:
https://www.bluetooth.org/foundry/assignnumb/document/baseband
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-10-19 11:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-19 8:19 [Bluez-devel] inquiry_info device class to string postmaster
2004-10-19 9:23 ` Stephen Crane
2004-10-19 11:03 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox