From: martin f krafft <madduck@madduck.net>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset
Date: Tue, 23 Sep 2008 15:00:00 +0200 [thread overview]
Message-ID: <20080923130000.GA848@piper.oerlikon.madduck.net> (raw)
In-Reply-To: <1220634042.6714.89.camel@californication>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
also sprach Marcel Holtmann <marcel@holtmann.org> [2008.09.05.1900 +0200]:
> actually I have none. It simply works for me. And I have tested it a
> lot. There are some rare conditions where the btusb driver is off on the
> 16-bit boundaries, but I am looking at a fix for it. However this will
> not disturb the audio service. You just don't here anything.
Ported original thread from SF list:
http://article.gmane.org/gmane.linux.bluez.devel/16060
I can reproduce the exact same error with a BT250 hooked up via
a different bluetooth adapter to an amd64 machine this time (the
last one was i386), running 2.6.26.
Stuart Pook told me about bluez-utils 4.4 [0] - I am still using 3.36
[1], but the wiki page says that I need 3.16 or newer. Would
I have better luck with 4.4? Where does this stuff come in anyway?
I am running hcid in the background, but I know too little about
ALSA or Bluetooth to be able to see how the two interlink. The wiki
mentions a btaudiod, which 3.36 seems not to have. Is that needed?
0. http://article.gmane.org/gmane.linux.bluez.devel/16113
1. http://bugs.debian.org/499529
--
martin | http://madduck.net/ | http://two.sentenc.es/
"sometimes the urge to do bad is nearly overpowering"
-- ben horne
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-23 13:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 7:36 [Bluez-devel] SCO flowcontrol patch v4.4 on 2.6.25/6 causes hardlocks when connecting to BT device martin f krafft
2008-08-22 8:33 ` Marcel Holtmann
2008-08-26 16:35 ` [Bluez-devel] btusb+sco failing to play sound through Jabra BT500v headset (was: SCO flowcontrol patch v4.4 on 2.6.25/6 causes) " martin f krafft
2008-08-26 17:19 ` Marcel Holtmann
2008-08-26 20:34 ` martin f krafft
2008-08-27 5:18 ` Marcel Holtmann
2008-08-27 21:03 ` martin f krafft
2008-09-05 16:26 ` [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset (was: btusb+sco failing to play sound through Jabra BT500v headset) martin f krafft
2008-09-05 17:00 ` Marcel Holtmann
2008-09-08 20:33 ` martin f krafft
2008-09-23 13:00 ` martin f krafft [this message]
2008-09-23 13:37 ` [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset Stuart Pook
2008-09-29 21:41 ` SCO headset, bluez-4.9 & linux 2.6.27-rc7 -> Unable to install hw params Stuart Pook
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=20080923130000.GA848@piper.oerlikon.madduck.net \
--to=madduck@madduck.net \
--cc=linux-bluetooth@vger.kernel.org \
/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