From: Deepthi <deepthi.pv@globaledgesoft.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: HCI rccvmsg() not receiving any data.
Date: Tue, 10 Jul 2012 16:53:26 +0530 [thread overview]
Message-ID: <4FFC10AE.1040605@globaledgesoft.com> (raw)
In-Reply-To: <CABBYNZ+vNjKwrTz2Ck4x0hYRyeBzJsRiQLqZWX7YjOba-EYgQA@mail.gmail.com>
Hello,
hci sendmsg() system call is able to execute properly .However hci
recvmsg() will be in blocked state not able to receive any data in the
other end . How to send & receive the message using HCI RAW socket.
Please help,
Thanks & Regards ,
Deepthi Elizabeth P V
>
prev parent reply other threads:[~2012-07-10 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 12:09 [RFC BlueZ] core: Fix not waiting for discovery to stop before attempting to pair Luiz Augusto von Dentz
2012-07-04 13:30 ` Anderson Lizardo
2012-07-04 14:16 ` Joao Paulo Rechi Vita
2012-07-04 14:35 ` Luiz Augusto von Dentz
2012-07-10 11:23 ` Deepthi [this message]
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=4FFC10AE.1040605@globaledgesoft.com \
--to=deepthi.pv@globaledgesoft.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 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).