[Bluez-users] #define OGF_TESTING_CMD potentially wrong?

[Peter Wurmsdobler <peter@wurmsdobler.org>]

Hello,

a few days ago I posted a message concerning testing, i.e. on how to put 
a Bluetooth module into the test modes specified in the Bluetooth 
specification Core 2.1 (27.07.2007) using:

	hcitool cmd <OGF> <OCF> [params]

In concrete I was interested in HCI_Write_Loopback_Mode and 
HCI_Enable_Device_Under_Test_Mode, for which OCF are defined as 0x0002 
and 0x0003, respectively. OGF is defined as 0x06 in the specification.

hcitool delivers the command at the bluetooth module. However, hcidump, 
which uses #defines and tables from bluez-libs, resolves this commands 
as Unknown, as it would defined in include/hci.h

#define OGF_TESTING_CMD 0x3e

If I used OGF=0x3e in the above hcitool command, hcidump would resolve 
the string correctly, but the bluetooth module would not do what it was 
told to do.

To me it appears that the #define in hci.h is potentially wrong, or 
maybe refers to an older version of the specification, when testing 
might have been vendor specific.

Best regards,
peter


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users