linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ajay KV <ajay.kv@globaledgesoft.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Re : BLE -Multiple connection
Date: Thu, 23 Aug 2012 09:50:08 -0400	[thread overview]
Message-ID: <50363510.8070902@globaledgesoft.com> (raw)
In-Reply-To: <CAJdJm_NkobxyO=Ks=hdMxNjHNb1jSMotNPCcLrtwq+bjKxkJYw@mail.gmail.com>

On 08/22/2012 12:01 PM, Anderson Lizardo wrote:
> Hi Ajay,
>
> On Wed, Aug 22, 2012 at 7:18 PM, Ajay KV<ajay.kv@globaledgesoft.com>  wrote:
>>          First of all, sorry for my ignorance . Following are the steps i did
>> in my test case.  i am also using dual mode dongles , so as you said  spec
>> is not allowing us to do  this operation
>> [snip]
>
> I remembered that the Core spec mentions that it is not required for a
> controller to support more than one connection. Maybe it is the case
> for the dongles you have? In this case, the controller will not allow
> to send connectable advertising because of the active connection.
>
> (sorry, I could not find the section of the spec that mentions this)
>
> If you close the connection, are you able to run "hciconfig hci0
> leadv" again on "A"?
>
> Regards,


Hi ,

	yes , exactly the moment the connection get terminates ,  i could able 
to enable advertise again. The intresting point is that during connected 
mode , even advertise disable  is also giving the same "command 
disallowed" error.

regards

  reply	other threads:[~2012-08-23 13:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <503545C5.80607@globaledgesoft.com>
2012-08-22 12:24 ` Re : BLE -Multiple connection Anderson Lizardo
2012-08-22 23:18   ` Ajay KV
2012-08-22 16:01     ` Anderson Lizardo
2012-08-23 13:50       ` Ajay KV [this message]
2012-08-23 19:10         ` Anderson Lizardo

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=50363510.8070902@globaledgesoft.com \
    --to=ajay.kv@globaledgesoft.com \
    --cc=anderson.lizardo@openbossa.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).