On 09/10/2010 12:53 PM, Pavan Savoy wrote:
Nope, I haven't applied the kernel patches...
But my kernel diff to the latest kernel is only regarding the "block"
and "unblock" to black list devices....
do I need some patches in kernel for enabling/disabling BLE too ?
I thought it just sends out the commands to controller...
You are right. You don't need to have the kernel patches.
I did some tests here and everything goes ok.
Check the hcidump output below:
2010-09-10 14:13:19.032099 < HCI Command: Unknown (0x08|0x000a) plen 1
0000: 01 .
2010-09-10 14:13:19.070320 > HCI Event: Command Complete (0x0e) plen 4
Unknown (0x08|0x000a) ncmd 2
0000: 00
I just did a hciconfig hci0 leadv
Regards,
Anderson Briglia
On Fri, Sep 10, 2010 at 8:40 AM, Anderson Briglia
<anderson.briglia@xxxxxxxxxxxxx> wrote:
Hi Pavan,
Try to make a hciconfig reset before setting leadv.
Are you using that kernel patches I send before, right?
Regards,
Anderson Briglia
On 09/09/2010 03:58 PM, Pavan Savoy wrote:
I have an LE enabled BT controller, and I happened to send across a
simple "leadv" from the recently updated hciconfig
I got back the following data
"4 e 5 1 a 20 c 3a" and hence
"Can't set advertise mode on hci0: Success (0)"
and 0xC I guess by the BT spec means the command is disallowed (for
reasons unknown?....)
So I'm just wondering, am I supposed to run some HCI-VS commands to
enable LE? I mean I should ask my vendor I agree, but anyone who has
got it working.. do they run some VS commands before enabling LE
advertising?
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
