Re: [Bluez-devel] forcing SCO connection patch

[Guillaume Bedot <littletux@zarb.org>]

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

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.

[-- Attachment #2: also-accept-sco-links-v3.patch --]
[-- Type: text/x-patch, Size: 432 bytes --]

--- 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;
 

[-- Attachment #3: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel