public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] ACL connection handle
Date: Tue, 25 Mar 2008 08:39:33 -0600	[thread overview]
Message-ID: <d89ddf300803250739ga372a9fy6d1aa4eff033be0e@mail.gmail.com> (raw)
In-Reply-To: <8f5c4ad0803250600q4b36a962w27e57fc3210ebd09@mail.gmail.com>

Matt

this would be a good topic for bluez-devel. Are you subscribed over there?

>    I am using the infineon.When I play through the uart, I will give -D
> bluetooth option to aplay  and this  will create an acl as well as sco
> connection and route audio through uart.But if I am  using the pcm interface
> , I will  route  audio to the pcm interface  on the host connected to the bt
> module and use aplay without the bluetooth option right?,So I have to create
> an acl connection and then use the hcitool cmd to  switch the SCO interface
> before I do aplay .So is that necessary to give the command from inside the
> audio service ?How would I establish the acl connection? Can I use rfcomm
> connect ?

The bt alsa plugin does only make sense when getting audio over hci,
but the audio service was designed so you could use d-bus to make it
negotiate the connection and then get the audio through another route,
eg the pcm.

You could run the bluetooth negotiation yourself when going through
pcm, but it would be better use of the infrastructure to patch the
audio service so it can be used for both the pcm and hci cases. iirc,
the audio service assumes you'll use one kind of routing the whole
time you run it, so that would have to be changed to be a runtime
setting set through d-bus.

The audio service might be patched to, for example, invoke an external
program between establishing the acl and sco connections. that could
take an acl handle and do the infineon magic.

I'm not sure there is a way to pull this off in a way that Marcel
would accept upstream, but even if you have to do a custom patch to
the audio service to make it work the way you need it I think you'll
be able to pull it together more quickly.

-- 
Brad

-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-03-25 14:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 12:01 [Bluez-users] ACL connection handle Paul
2008-03-25 12:16 ` Brad Midgley
2008-03-25 13:00   ` Paul
2008-03-25 14:39     ` Brad Midgley [this message]
2008-03-26 16:27       ` Marcel Holtmann
2008-03-27  3:43         ` Brad Midgley
2008-03-27 15:10           ` Marcel Holtmann
2008-03-28  3:05             ` 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=d89ddf300803250739ga372a9fy6d1aa4eff033be0e@mail.gmail.com \
    --to=bmidgley@gmail.com \
    --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