From: Ajay <ajay.kv@globaledgesoft.com>
To: linux-bluetooth@vger.kernel.org
Subject: BLE issue - Reusing Existing LE physical link
Date: Wed, 07 Nov 2012 22:14:04 +0530 [thread overview]
Message-ID: <509A8FD4.1080800@globaledgesoft.com> (raw)
Hi ,
I came across an issue as part of my "BLE test tool project" . After
the first successful connection of BLE l2cap connection (client server)
, we just retains the physical link without calling le_connection
cancel() (logical link is closed) (patch has been added). But second
time i wanted to use the existing connection , without calling
hci_le_connect() . but here l2cap connect fails . I noticed in normal
acl link , the same scenario is working on existing link. so can we
do the same working on BLE link . (ubuntu 11.10 and kernel 3.2.5)
--
Thanks & regards
AJAY KV
GlobalEdge software Ltd
8892753703
next reply other threads:[~2012-11-07 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 16:44 Ajay [this message]
2012-11-09 8:11 ` BLE issue - Reusing Existing LE physical link Vinicius Costa Gomes
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=509A8FD4.1080800@globaledgesoft.com \
--to=ajay.kv@globaledgesoft.com \
--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).