Re: forcing SCO connection patch

Re,

Le mardi 26 février 2008 à 20:28 +0100, Marcel Holtmann a écrit :
> No. That is wrong. Using sync setup commands apply to SCO and eSCO.
> No  
> need to force anything here. Let the Bluetooth firmware inside the  
> chip do the right thing.

So I have to assume LM=device firmware and Host=device driver, the
separation between the two finally makes sense.

Here is a corrected version of the other patch.

Regards,

Guillaume B.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

--- net/bluetooth/hci_event.c.orig	2008-02-26 17:20:11.000000000 +0100
+++ net/bluetooth/hci_event.c	2008-02-26 21:19:04.000000000 +0100
@@ -1313,6 +1313,11 @@
 	hci_dev_lock(hdev);
 
 	conn = hci_conn_hash_lookup_ba(hdev, ev->link_type, &ev->bdaddr);
+	if (!conn && ev->link_type==SCO_LINK) {
+		conn = hci_conn_hash_lookup_ba(hdev, ESCO_LINK, &ev->bdaddr);
+		if (conn)
+			conn->type=SCO_LINK;
+	}
 	if (!conn)
 		goto unlock;