public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Bedot <littletux@zarb.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Connecting to a two-way headset
Date: Mon, 18 Feb 2008 16:25:19 +0100	[thread overview]
Message-ID: <1203348319.7074.8.camel@localhost> (raw)
In-Reply-To: <BLU140-W76F2261C8313336A0D258CB200@phx.gbl>

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

Hello,

Le dimanche 17 février 2008 à 17:07 +0000, mountain rides a écrit :
> Hi,
> 
> Apologies if I'm asking a repeated question, but my search just now didn't pick up any answers.
> 
> I'm trying to get a speaker-and-microphone headset working.
> 
> More exactly . . .
> 
> I have a new Sony Ericsson HBH-PV702 Bluetooth headset - that is, a headset not with just speakers, but with both a speaker and microphone.  
> 
> I also have a Dell Inspiron 6400 with Bluetooth built-in

You're mixing a bluetooth 2.0 chip and a bluetooth 1.2 headset, you may
need, in addition of wise suggestions from Leszek, to use this kernel
patch.

Regards,

Guillaume B.


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

--- net/bluetooth/hci_event.c.orig	2008-02-18 14:02:20.000000000 +0100
+++ net/bluetooth/hci_event.c	2008-02-18 15:19:04.000000000 +0100
@@ -1313,8 +1313,15 @@
 	hci_dev_lock(hdev);
 
 	conn = hci_conn_hash_lookup_ba(hdev, ev->link_type, &ev->bdaddr);
-	if (!conn)
-		goto unlock;
+	if (!conn) {
+		if (ev->link_type==SCO_LINK) {
+			conn = hci_conn_hash_lookup_ba(hdev, ESCO_LINK, &ev->bdaddr);
+			if (!conn)
+				goto unlock;
+			else
+				conn->type=SCO_LINK;
+			}
+	}
 
 	if (!ev->status) {
 		conn->handle = __le16_to_cpu(ev->handle);

[-- 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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2008-02-18 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17 17:07 [Bluez-users] Connecting to a two-way headset mountain rides
2008-02-18  2:38 ` Leszek Koltunski
2008-02-18 15:25 ` Guillaume Bedot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-18 11:45 Peter Wurmsdobler
2008-02-19  2:49 ` Leszek Koltunski
2008-02-19 20:26 ` Stefan Seyfried

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=1203348319.7074.8.camel@localhost \
    --to=littletux@zarb.org \
    --cc=bluez-users@lists.sourceforge.net \
    /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