Linux bluetooth development
 help / color / mirror / Atom feed
From: Mat Martineau <mathewm@codeaurora.org>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, pkrystad@codeaurora.org,
	padovan@profusion.mobi
Subject: Re: [RFCv0 0/5] extended window size and extended control field support
Date: Tue, 30 Aug 2011 09:10:01 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1108300842410.14580@mathewm-linux> (raw)
In-Reply-To: <1314688721-16742-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>


Hi Andrei -

On Tue, 30 Aug 2011, Emeltchenko Andrei wrote:

> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> First draft patches applied to my previous EFS patches. Please comment.
>
> Adds support for extended window size option (EWS) and extended control
> field. Code partly based on Atheros patches sent a year ago and Qualcomm
> code git://codeaurora.org/kernel/msm.git.
>
> To decode EWS option and extended control field please apply patch to hcidump
> which I sent to linux-bluetooth.
>
> Andrei Emeltchenko (5):
>  Bluetooth: extended window size option support
>  Bluetooth: l2cap extended control field support
>  Bluetooth: EWS: support extended seq numbers
>  Bluetooth: remove magic numbers in l2cap
>  Bluetooth: prevent unneeded fragmentation in l2cap
>
> include/net/bluetooth/l2cap.h |  304 ++++++++++++++++++++++----
> net/bluetooth/l2cap_core.c    |  481 +++++++++++++++++++++++++----------------
> net/bluetooth/l2cap_sock.c    |   11 +-
> 3 files changed, 562 insertions(+), 234 deletions(-)
>
> -- 
> 1.7.4.1

Extended window size is next on my list to upstream.  As you probably 
noticed, the git://codeaurora.org/kernel/msm.git code has a slightly 
different approach to handling the two control field types.  The 
fields are handled in a struct that's part of the bt_cb control block, 
and only read/written in wire format when the frame is first received 
or about to be sent.  Are there any issues with this method (other 
than the fact that I haven't upstreamed it yet)?  Some of the 
subsequent L2CAP state machine changes depend on this.

Please let me know if there are specific features from the 
git://codeaurora.org/kernel/msm.git code base that you would like to 
prioritize for upstreaming - there's a lot to do to bring in those 
L2CAP and AMP changes, and I'll have more time to devote to it in 
mid-September.  I think we can gain a lot by reviewing each other's 
patches and coordinating our efforts.

Regards,

--
Mat Martineau
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum


  parent reply	other threads:[~2011-08-30 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30  7:18 [RFCv0 0/5] extended window size and extended control field support Emeltchenko Andrei
2011-08-30  7:18 ` [RFCv0 1/5] Bluetooth: extended window size option support Emeltchenko Andrei
2011-08-30  7:18 ` [RFCv0 2/5] Bluetooth: l2cap extended control field support Emeltchenko Andrei
2011-08-30  7:18 ` [RFCv0 3/5] Bluetooth: EWS: support extended seq numbers Emeltchenko Andrei
2011-08-30  7:18 ` [RFCv0 4/5] Bluetooth: remove magic numbers in l2cap Emeltchenko Andrei
2011-08-30  7:18 ` [RFCv0 5/5] Bluetooth: prevent unneeded fragmentation " Emeltchenko Andrei
2011-08-30 16:10 ` Mat Martineau [this message]
2011-08-30 18:18   ` [RFCv0 0/5] extended window size and extended control field support Marcel Holtmann
2011-08-31 17:53     ` Mat Martineau
2011-08-30 21:06   ` 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=alpine.DEB.2.02.1108300842410.14580@mathewm-linux \
    --to=mathewm@codeaurora.org \
    --cc=Andrei.Emeltchenko.news@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=padovan@profusion.mobi \
    --cc=pkrystad@codeaurora.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