public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Echtler <echtler@fs.tum.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: strange btsco error
Date: Tue, 22 Feb 2005 12:41:45 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.61.0502221238490.11660@block.bubble> (raw)
In-Reply-To: <Pine.LNX.4.61.0502221045530.11660@block.bubble>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Any experiences with that? Better kernel ALSA or standalone ALSA?

Well, I solved that one by myself (see also 
http://thread.gmane.org/gmane.linux.bluez.devel/3790). Obviously,
kernel ALSA is necessary (I'm using 2.6.10-mh2).

Two things therefore:
1. the B-Speech Elect Headset works fine (now ;)
2. on the bluetooth-alsa site, you should really mention that external
   ALSA drivers (at least 1.0.8) won't work! (as already asked for in 
   the above thread)

Yours, Florian
- -- 
Preserve wildlife - pickle a squirrel today!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFCGxp+7CzyshGvatgRAsMOAKDlUbCE1vJw3zB2W/w4bYa2/6dg+ACcDdvW
HO16/AOvfxJu+Bw5x/flhPg=
=5mjw
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-02-22 11:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-19 10:25 [Bluez-users] strange btsco error Florian Echtler
2005-02-19 21:05 ` [Bluez-users] " Sebastian Roth
2005-02-20  7:59   ` Florian Echtler
2005-02-20 16:18     ` Sebastian Roth
2005-02-22  9:50       ` Florian Echtler
2005-02-22 11:41         ` Florian Echtler [this message]
2005-02-22 20:42           ` Brad Midgley

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=Pine.LNX.4.61.0502221238490.11660@block.bubble \
    --to=echtler@fs.tum.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