From: Anderson Briglia <anderson.briglia@openbossa.org>
To: Pavan Savoy <pavan_savoy@sify.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: set LE advertise not working...
Date: Fri, 10 Sep 2010 14:14:35 -0400 [thread overview]
Message-ID: <4C8A758B.1060708@openbossa.org> (raw)
In-Reply-To: <AANLkTin02sOL89MuUhWe1_nOg4umytfJKRfc=Z_dhpRq@mail.gmail.com>
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@openbossa.org> 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@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>>
>>
>>
next prev parent reply other threads:[~2010-09-10 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 19:58 set LE advertise not working Pavan Savoy
2010-09-10 13:40 ` Anderson Briglia
2010-09-10 16:53 ` Pavan Savoy
2010-09-10 17:49 ` Mike Tsai
2010-09-10 18:14 ` Anderson Briglia [this message]
2010-09-10 19:01 ` Pavan Savoy
2010-09-10 20:35 ` Anderson Lizardo
2010-09-10 21:03 ` Claudio Takahasi
2010-09-10 21:35 ` Mike Tsai
2010-09-10 22:22 ` Pavan Savoy
2010-09-14 11:41 ` Ville Tervo
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=4C8A758B.1060708@openbossa.org \
--to=anderson.briglia@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pavan_savoy@sify.com \
/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.