public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: ngh@isomerica.net
To: linux-bluetooth@vger.kernel.org
Cc: Nathan Holstein <nathan@lampreynetworks.com>
Subject: [PATCH] *** SUBJECT HERE ***
Date: Wed, 29 Apr 2009 21:42:23 -0400	[thread overview]
Message-ID: <1241055744-12140-1-git-send-email-ngh@isomerica.net> (raw)

From: Nathan Holstein <nathan@lampreynetworks.com>

This is a revamping of the previous patches that I submited.  I started from
scratch, rebase all the changes onto the latest bluetooth-testing (2.6.30-rc3).
While applying the changes, I attempted to clean up the code and apply the
input from Marcel and Gustavo.

Unfortunately, I did not get a chance to test this for regressions vs. the
previous version of the code.  I did remove the code which segmented outgoing
PDUs: it wouldn't have worked with the current tx window=1, and would have
produced memory leaks.

The code is available from git://staticfree.info/git/el2cap on branch "ertm".

Nathan Holstein (9):
  Add #defines and data structures for enhanced L2CAP
  Add support for sending enhanced L2CAP data
  Add support for sending L2CAP S-frames.
  Append RFC option when configuring an L2CAP socket.
  Add support for parsing enhanced L2CAP configuration options.
  Add support for receiving data over an enhanced L2CAP channel
  Check the FCS of a received L2CAP packet.
  Reassemble segmented L2CAP PDUs upon reception
  Add support for negotiating new L2CAP options after a failed
    configuration

 include/net/bluetooth/bluetooth.h |    3 +-
 include/net/bluetooth/l2cap.h     |  124 +++++++-
 net/bluetooth/l2cap.c             |  607 ++++++++++++++++++++++++++++++++++---
 3 files changed, 673 insertions(+), 61 deletions(-)


             reply	other threads:[~2009-04-30  1:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30  1:42 ngh [this message]
2009-04-30  1:42 ` [PATCH] Add support for negotiating new L2CAP options after a failed configuration ngh
2009-04-30  2:01 ` [PATCH] *** SUBJECT HERE *** Marcel Holtmann
2009-04-30 16:12   ` 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=1241055744-12140-1-git-send-email-ngh@isomerica.net \
    --to=ngh@isomerica.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=nathan@lampreynetworks.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