Re: [RFC] Bluetooth: Use non-flushable pb flag by default for ACL data on capable chipsets.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Andrei,

On 12/13/2010 8:08 PM, Emeltchenko Andrei wrote:
  static inline void l2cap_send_cmd(struct l2cap_conn *conn, u8 ident, u8 code, u16 len, void *data)
  {
  	struct sk_buff *skb = l2cap_build_cmd(conn, code, ident, len, data);
+	u8 flags;

  	BT_DBG("code 0x%2.2x", code);

  	if (!skb)
  		return;

-	hci_send_acl(conn->hcon, skb, 0);
+	if (lmp_no_flush_capable(conn->hcon->hdev))
+		flags = ACL_START_NO_FLUSH;
+	else
+		flags = ACL_START;
+
+	hci_send_acl(conn->hcon, skb, flags);
  }

Should we send L2CAP command packets also as flushable packets? Should it be non-flushable?
I thought only L2CAP data frames should be sent as flushable.

Regards
Suraj

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux