From: "Malte J. Wetz" <bluez-users-mlist@malte-wetz.de>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Headset not working
Date: Mon, 7 Jul 2008 12:55:06 +0200 [thread overview]
Message-ID: <200807071255.06344.bluez-users-mlist@malte-wetz.de> (raw)
In-Reply-To: <alpine.LNX.1.10.0807060641520.7069@nge2.ngu.pk>
Am Sonntag, 6. Juli 2008 schrieb jayjwa:
> On Fri, 4 Jul 2008, Martin Mueller wrote:
> -> You can get the patch from:
> http://bluetooth-alsa.cvs.sourceforge.net/*checkout*/bluetooth-alsa/plugz
>/patches/sco-flowcontrol-v4.4.diff?revision=3D1.1 ->
>
> We seem to be talking about different patches. I am refering to the one
> needed to allow older bluetooth (I think it's 1.2?) headsets to work with
> newer kernels, that deals with SCO/ESCO. The one above modifies another
> file. Below is the one I use, and it's working now even on linux-2.6.25.9
> (kernel.org) that I'm currently using.
Well, as I wrote before, I'm already using the SCO/ESCO patch and it does =
not work.
The patch proposed by Martin does apply to current kernel (you just have to =
add =BB-F10=AB to your patch command as some line have moved beyond the def=
ault =
fuzz). But it does no good. Now, whenever I play back something via the =
headset, the entire kernel freezes and even Magic SysRq won't anymore. Only =
a hard reset gets me out of there.
Log files is insuspicous:
Jul 7 12:41:37 triton hcid[8053]: Audio API: received =
BT_GETCAPABILITIES_REQ
Jul 7 12:41:37 triton hcid[8053]: Audio API: sending BT_GETCAPABILITIES_RSP
Jul 7 12:41:37 triton hcid[8053]: Audio API: received =
BT_SETCONFIGURATION_REQ
Jul 7 12:41:37 triton hcid[8053]: config sco - device =3D 00:13:17:CF:C3:D=
5 =
access_mode =3D 2
Jul 7 12:41:40 triton hcid[8053]: pin_code_request (sba=3D00:0A:3A:81:33:1=
C, =
dba=3D00:13:17:CF:C3:D5)
<freeze here>
hci_usb is loaded with force_scofix=3D1. I cannot see any differences.
Still confused,
Malte
-- =
Malte J. Wetz <mail@malte-wetz.de>
Homepage: www.malte-wetz.de (PGP/GPG Keys available on homepage)
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-07-07 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 0:37 [Bluez-users] Headset not working (was: Belkin USB-Dongle blocks USB subsystem) Malte J. Wetz
2008-07-04 4:27 ` jayjwa
2008-07-04 14:17 ` Michael Domann
2008-07-04 16:33 ` Martin Mueller
2008-07-06 11:35 ` jayjwa
2008-07-07 10:55 ` Malte J. Wetz [this message]
2008-07-07 11:32 ` [Bluez-users] Headset not working Martin Mueller
2008-07-07 12:15 ` Malte J. Wetz
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=200807071255.06344.bluez-users-mlist@malte-wetz.de \
--to=bluez-users-mlist@malte-wetz.de \
--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