From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCHv5 12/19] android/socket: Send RFCOMM channel to framework
Date: Tue, 19 Nov 2013 15:30:02 +0200 [thread overview]
Message-ID: <1384867809-18135-13-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1384867809-18135-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
Framework expects channel to be send.
---
android/socket.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/android/socket.c b/android/socket.c
index ad09a2c..e620d10 100644
--- a/android/socket.c
+++ b/android/socket.c
@@ -493,6 +493,11 @@ static void sdp_search_cb(sdp_list_t *recs, int err, gpointer data)
goto fail;
}
+ if (write(rfsock->fd, &chan, sizeof(chan)) != sizeof(chan)) {
+ error("Error sending RFCOMM channel");
+ goto fail;
+ }
+
rfsock->real_sock = g_io_channel_unix_get_fd(io);
rfsock->channel = chan;
connections = g_list_append(connections, rfsock);
--
1.7.10.4
next prev parent reply other threads:[~2013-11-19 13:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 13:29 [PATCHv5 00/19] Socket HAL Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 01/19] android/hal-sock: Print bdaddr string instead of pointer Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 02/19] android/socket: Add get RFCOMM default channel Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 03/19] android/socket: Define structs and implement listen Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 04/19] android/socket: Implement socket accepted event Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 05/19] android/socket: Implement Android RFCOMM stack events Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 06/19] android/socket: Implement RFCOMM events Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 07/19] android/socket: Send accept signal to Android through hal_fd Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 08/19] android/socket: Write channel to Android fd Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 09/19] android/socket: Implement socket connect HAL method Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 10/19] android/socket: Parse SDP response and connect Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 11/19] android/socket: Implement HAL connect call Andrei Emeltchenko
2013-11-19 13:30 ` Andrei Emeltchenko [this message]
2013-11-19 13:30 ` [PATCHv5 13/19] android/socket: Send connect signal on connect Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 14/19] android/socket: Close file descriptor after sending Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 15/19] android/socket: Add SDP record for OPP profile Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 16/19] android/socket: Add MAS uuid to profile table Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 17/19] android/socket: Add SPP " Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 18/19] android/socket: Add PBAP SDP record Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 19/19] android/socket: Add SPP " Andrei Emeltchenko
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=1384867809-18135-13-git-send-email-Andrei.Emeltchenko.news@gmail.com \
--to=andrei.emeltchenko.news@gmail.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).