Linux bluetooth development
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 0/8] Second round of patches for the l2cap "rewrite"
Date: Fri, 15 Apr 2011 15:17:26 -0300	[thread overview]
Message-ID: <1302891454-10165-1-git-send-email-padovan@profusion.mobi> (raw)

These patches finishes almost all the data separatation bettween an L2CAP
socket and an L2CAP channel. Some missing pieces are:
	- New locking system to the l2cap_channel (together with the a new
	  	backlog recv queue implementation).
	- Keep the state of the connection on strcut l2cap_chan ( and notify
	  	the socket about changes on the state)
	- New ways to retrieve data from bt_sk.
	- New list to search for the psm and scid we can accept a connection
		or receive data (connectionless case)

Then we need to draw an API to access L2CAP channels from l2cap_sock.c and
RFCOMM, and a notify system for L2CAP core tell its users about new data, state
changes, etc.

Please comment.

Regards,

Gustavo F. Padovan (8):
  Bluetooth: Refactor L2CAP channel allocation
  Bluetooth: Move conf_state to struct l2cap_chan
  Bluetooth: Rename l2cap_do_connect() to l2cap_chan_connect()
  Bluetooth: Move some more elements to struct l2cap_chan
  Bluetooth: Move more vars to struct l2cap_chan
  Bluetooth: Move more channel info to struct l2cap_chan
  Bluetooth: Move more vars to struct l2cap_chan
  Bluetooth: Move conn to struct l2cap_chan

 include/net/bluetooth/l2cap.h |   67 +++---
 net/bluetooth/l2cap_core.c    |  578 ++++++++++++++++++++---------------------
 net/bluetooth/l2cap_sock.c    |  236 ++++++++++--------
 net/bluetooth/rfcomm/core.c   |   21 +-
 net/bluetooth/rfcomm/sock.c   |    5 +-
 5 files changed, 465 insertions(+), 442 deletions(-)

-- 
1.7.5.rc1


             reply	other threads:[~2011-04-15 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15 18:17 Gustavo F. Padovan [this message]
2011-04-15 18:17 ` [PATCH 1/8] Bluetooth: Refactor L2CAP channel allocation Gustavo F. Padovan
2011-04-15 18:17   ` [PATCH 2/8] Bluetooth: Move conf_state to struct l2cap_chan Gustavo F. Padovan
2011-04-15 18:17     ` [PATCH 3/8] Bluetooth: Rename l2cap_do_connect() to l2cap_chan_connect() Gustavo F. Padovan
2011-04-15 18:17       ` [PATCH 4/8] Bluetooth: Move some more elements to struct l2cap_chan Gustavo F. Padovan
2011-04-15 18:17         ` [PATCH 5/8] Bluetooth: Move more vars " Gustavo F. Padovan
2011-04-15 18:17           ` [PATCH 6/8] Bluetooth: Move more channel info " Gustavo F. Padovan
2011-04-15 18:17             ` [PATCH 7/8] Bluetooth: Move more vars " Gustavo F. Padovan
2011-04-15 18:17               ` [PATCH 8/8] Bluetooth: Move conn " Gustavo F. Padovan

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=1302891454-10165-1-git-send-email-padovan@profusion.mobi \
    --to=padovan@profusion.mobi \
    --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