All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Renaud <andre@bluewatersys.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Headset+Alsa problems (without Pulse Audio)
Date: Thu, 14 Jul 2011 10:38:17 +1200	[thread overview]
Message-ID: <4E1E1E59.2000602@bluewatersys.com> (raw)
In-Reply-To: <20110713080934.GA14678@dell.ger.corp.intel.com>

Hi Johan,
On 13/07/11 20:09, Johan Hedberg wrote:
> Regarding the other issues, unfortunately I can't really help you there.
> I've never really looked into these ALSA user-space plugins in detail.
> It's not a big surprise though that it doesn't work: it seems like the
> last time ctl_bluetooth.c got major changes was back in 2007 (i.e.
> no-one seems to have had much interest in maintaining it since then).
> 
> You should also know that unless someone puts effort into adding support
> for the D-Bus Media API (doc/media-api.txt) then pcm_bluetooth.c and
> ctl_bluetooth.c will be removed in the BlueZ 5.0 release along with the
> pure unix socket based interface for audio.

Can you confirm for me then that Pulse Audio is the only real supported
mechanism for getting Bluetooth headsets to work under Linux? If support
for the ctl/pcm bluetooth modules is about to be dropped, I'm pretty
sure we're not going to want to start out with that mechanism.

Regards,
Andre

  reply	other threads:[~2011-07-13 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13  4:38 Headset+Alsa problems (without Pulse Audio) Andre Renaud
2011-07-13  8:09 ` Johan Hedberg
2011-07-13 22:38   ` Andre Renaud [this message]
2011-07-13 23:04     ` Johan Hedberg
2011-07-13 23:19       ` Andre Renaud

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=4E1E1E59.2000602@bluewatersys.com \
    --to=andre@bluewatersys.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.