From 332472cb6cc8d889547a25a80a0cffdbe047d7f4 Mon Sep 17 00:00:00 2001 From: Mat Martineau Date: Mon, 7 May 2012 09:52:04 -0700 Subject: [PATCH] Bluetooth: Correctly configure L2CAP streaming mode header type In order to support extended window sizes with L2CAP streaming mode, an extended window size option must be included in the outgoing configuration request when an application has requested a transmit window larger than the default transmit window. Streaming mode does not have a transmit window, so initialization of the transmit window data structures was not taking place. However, the transmit window socket option does trigger use of extended headers, which are required for full streaming mode support and qualification. Utilizing the existing transmit window initialization code enables extended header use. CRs-fixed: 355437 Change-Id: I7bf25b7a70bb2b68c0f5bfd42b2b46b99d68e990 Signed-off-by: Mat Martineau --- net/bluetooth/l2cap_core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c index 9f9f17d2f31..a7b95d3f05f 100644 --- a/net/bluetooth/l2cap_core.c +++ b/net/bluetooth/l2cap_core.c @@ -3365,6 +3365,7 @@ done: break; case L2CAP_MODE_STREAMING: + l2cap_setup_txwin(pi); rfc.txwin_size = 0; rfc.max_transmit = 0; rfc.retrans_timeout = 0;