From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCHv1 00/16] Socket HAL
Date: Thu, 14 Nov 2013 17:11:39 +0200 [thread overview]
Message-ID: <1384441915-23966-1-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
This is initial code implementing socket HAL. Receiving files
through OPP currently works.
Changes:
* v1: Rebased and use static src address, hal_fd removed from structure and closed after sent to framework,
added connect calls and SDP parsing, added cleanup_rfcomm function, minor fixes.
* RFC Initial
For tracking rfcomm sockets I use structure rfslot which has following
fields:
- real_sock - real RFCOMM socket
- fd - fd to communicate with Android framework
- hal_fd - fd passed to Android framework with CMSG
Andrei Emeltchenko (16):
android/hal-sock: Add debug flag printing
android/hal-sock: Use static local adapter address
android/hal-sock: Add connect signal to socket
android/hal-sock: Define structures for socket HAL
android/hal-sock: Initial listen handle
android/hal-sock: Implement socket accepted event
android/hal-sock: Implement Android RFCOMM stack events
android/hal-sock: Implement RFCOMM events
android/hal-sock: Implement accept signal over Android fd
android/hal-sock: Write channel to Android fd
android/hal-sock: Implement socket connect HAL method
android/hal-sock: Parse SDP response and connect
android/hal-sock: Implement HAL connect call
android/hal-sock: Send RFCOMM channel to framework
android/hal-sock: Send connect signal on connect
android/hal-sock: Close file descriptor after sending
android/hal-msg.h | 2 +
android/hal-sock.c | 8 +-
android/socket.c | 496 +++++++++++++++++++++++++++++++++++++++++++++++++++-
android/socket.h | 7 +
4 files changed, 505 insertions(+), 8 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-11-14 15:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 15:11 Andrei Emeltchenko [this message]
2013-11-14 15:11 ` [PATCHv1 01/16] android/hal-sock: Add debug flag printing Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 02/16] android/hal-sock: Use static local adapter address Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 03/16] android/hal-sock: Add connect signal to socket Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 04/16] android/hal-sock: Define structures for socket HAL Andrei Emeltchenko
2013-11-15 12:29 ` Luiz Augusto von Dentz
2013-11-14 15:11 ` [PATCHv1 05/16] android/hal-sock: Initial listen handle Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 06/16] android/hal-sock: Implement socket accepted event Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 07/16] android/hal-sock: Implement Android RFCOMM stack events Andrei Emeltchenko
2013-11-15 0:00 ` Marcel Holtmann
2013-11-15 9:23 ` Andrei Emeltchenko
2013-11-15 9:32 ` Marcel Holtmann
2013-11-14 15:11 ` [PATCHv1 08/16] android/hal-sock: Implement RFCOMM events Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 09/16] android/hal-sock: Implement accept signal over Android fd Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 10/16] android/hal-sock: Write channel to " Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 11/16] android/hal-sock: Implement socket connect HAL method Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 12/16] android/hal-sock: Parse SDP response and connect Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 13/16] android/hal-sock: Implement HAL connect call Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 14/16] android/hal-sock: Send RFCOMM channel to framework Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 15/16] android/hal-sock: Send connect signal on connect Andrei Emeltchenko
2013-11-14 15:11 ` [PATCHv1 16/16] android/hal-sock: Close file descriptor after sending 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=1384441915-23966-1-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).