From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Asus WL-BTD202 needs force_scofix
Date: Tue, 22 Jan 2008 12:40:27 +0100 [thread overview]
Message-ID: <1201002028.7978.159.camel@aeonflux> (raw)
In-Reply-To: <1200991632.7006.20.camel@localhost>
Hi Guillaume,
> I'm currently testing bluetooth audio with latest cvs.
>
> I use this dongle and a mono headset (PROF PBH-6W) :
> $ /usr/sbin/lsusb | grep ASUS
> Bus 001 Device 002: ID 0b05:1715 ASUSTek Computer, Inc.
>
> Apparently, it only works with this option set hci_usb :
> options hci_usb force_scofix=1
>
> Recording and playback work, mostly.
> Sometimes noise is produced, retrying once or twice make it work...
>
> Could this option be set as a default in hci_usb.c, or could it have
> some drawback I'm not aware of ?
include the content of /proc/bus/usb/devices for this dongle and create
a kernel patch for hci_usb to always enable the SCO fix.
Regards
Marcel
-------------------------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-01-22 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 8:47 [Bluez-devel] Asus WL-BTD202 needs force_scofix Guillaume Bedot
2008-01-22 11:37 ` [Bluez-devel] [PATCH][HFP] Support for CLIP Alok
2008-01-22 11:40 ` Marcel Holtmann [this message]
2008-01-26 10:42 ` [Bluez-devel] Asus WL-BTD202 needs force_scofix Guillaume Bedot
2008-01-28 8:38 ` Guillaume Bedot
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=1201002028.7978.159.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=bluez-devel@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