public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Stockwell" <dstockwell@frequency-one.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Cc: "Marcel Holtmann" <marcel@holtmann.org>,
	"Johan Hedberg" <johan.hedberg@gmail.com>
Subject: Connecting to audio_service.Control (or other interfaces)
Date: Fri, 27 Jun 2008 15:50:34 -0500	[thread overview]
Message-ID: <028701c8d897$74b68880$6701a8c0@freqonedev> (raw)

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

The interface descriptions for audio-api.txt appear to be somewhat stagnant (for one area, you are probably waiting for me).

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)?

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?

How much of what is in audio-api.txt is or will be obsolete under 4.x?

David Stockwell

[-- Attachment #2: Type: text/html, Size: 1480 bytes --]

             reply	other threads:[~2008-06-27 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 20:50 David Stockwell [this message]
2008-06-27 21:18 ` [Bluez-devel] Connecting to audio_service.Control (or other interfaces) Johan Hedberg
2008-06-28  1:27   ` [Bluez-devel] Connecting to audio_service.Control (or otherinterfaces) David Stockwell

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='028701c8d897$74b68880$6701a8c0@freqonedev' \
    --to=dstockwell@frequency-one.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=johan.hedberg@gmail.com \
    --cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox