From: "David Stockwell" <dstockwell@frequency-one.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Connecting to audio_service.Control (or otherinterfaces)
Date: Fri, 27 Jun 2008 20:27:34 -0500 [thread overview]
Message-ID: <02c901c8d8be$25698f80$6701a8c0@freqonedev> (raw)
In-Reply-To: 4C97DD70-6B7E-43A0-8BB0-A1F4328EAEA4@gmail.com
Thanks...I missed seeing the new doc/audio-api.txt
It appears to be the old Headset and Sink, with new object path. That said, the mechanics (esp. SDP browse and pairing) appear to
be more integrated and I will be trying these out ASAP.
DS
----- Original Message -----
From: "Johan Hedberg" <johan.hedberg@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Sent: Friday, June 27, 2008 4:18 PM
Subject: Re: [Bluez-devel] Connecting to audio_service.Control (or otherinterfaces)
Hi David,
On Jun 27, 2008, at 23:50, David Stockwell wrote:
> That said: is it still your intent (or that of the development
> group) that the Object Path for audio-connected devices will be /org/
> bluez/audio/device<n> (where "n" is 0-based)?
In 4.0 with hcid and the plugins there is only one object path
hierarchy and a single object path per remote device (created by
CreateDevice or CreatePairedDevice). These paths have some generic
name plus the remote address and I don't remember right now how it
looks like. Try out those Create*Device methods and find out :)
> I assume that one would have to do any/all pairing against the
> org.bluez.Adapter object (e.g., object path /hci0), creating a
> Device object (e.g., /hci0/dev_00_02_5B_01_A4_74) before connecting
> to the audio Service and creating the audio Device (using the BT
> Address of the remote device, e.g., 00:02:5B:01:A4:74). Do I have
> this right?
No. In 4.x only one method call is needed to set up a new device.
Calling CreateDevice or CreatePairedDevice will cause hcid to perform
SDP discovery and if it finds audio profiles a callback will be fired
into the audio plugin which in turn will register the necessary audio
specific D-Bus interfaces for the new device object.
> How much of what is in audio-api.txt is or will be obsolete under 4.x?
Any API docs outside of the doc/ subdirectory are obsolete. You can
find the 4.x audio API in doc/audio-api.txt
Johan
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-06-28 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 20:50 Connecting to audio_service.Control (or other interfaces) David Stockwell
2008-06-27 21:18 ` [Bluez-devel] " Johan Hedberg
2008-06-28 1:27 ` David Stockwell [this message]
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='02c901c8d8be$25698f80$6701a8c0@freqonedev' \
--to=dstockwell@frequency-one.com \
--cc=bluez-devel@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