All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Andre Renaud <andre@bluewatersys.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Headset+Alsa problems (without Pulse Audio)
Date: Wed, 13 Jul 2011 11:09:34 +0300	[thread overview]
Message-ID: <20110713080934.GA14678@dell.ger.corp.intel.com> (raw)
In-Reply-To: <4E1D2146.2050508@bluewatersys.com>

Hi Andre,

On Wed, Jul 13, 2011, Andre Renaud wrote:
> I'm trying to get a bluetooth headset working on an embedded Linux 
> environment. I don't have the available resources to drag in all of
> Pulse Audio, so this is being done with essentially just bluez 
> and the alsa-libs.
> 
> It all seems to connect & pair properly, but when I go to play audio 
> no sound comes out. There are no complaints, and the 'aplay' command 
> runs for approximately the correct amount of time before exiting 
> cleanly. Using hcidump, I can see that the audio data is being 
> transmitted.
> 
> In the process of investigating this, I found that the amixer command 
> was unable to talk to the bluetooth controls. I eventually tracked 
> this down to a bug in audio/ctl_bluetooth.c. Having fixed it,
> I am now able to list the controls, but unable to change their values
> (I have also made it so that it errors out if it goes to change
> an integer, and the change doesn't take, rather than looping forever).
> 
> Does anyone know what I might be missing, or where I should start
> looking next?

About your patch, could you please send something that can be fed to
"git am". Typically git format-patch + git send-email should be enough
for this. Before that however, fix your code indentation. The BlueZ
coding style is to use *only* tabs whereas what you sent uses spaces.

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.

Johan

  reply	other threads:[~2011-07-13  8:09 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 [this message]
2011-07-13 22:38   ` Andre Renaud
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=20110713080934.GA14678@dell.ger.corp.intel.com \
    --to=johan.hedberg@gmail.com \
    --cc=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.