From: Johan Hedberg <johan.hedberg@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 3/4] Add Routing property to MediaTransport interface
Date: Wed, 19 Jan 2011 20:50:15 +0530 [thread overview]
Message-ID: <20110119152015.GF2112@jh-x301> (raw)
In-Reply-To: <1295344815-1404-3-git-send-email-luiz.dentz@gmail.com>
Hi Luiz,
On Tue, Jan 18, 2011, Luiz Augusto von Dentz wrote:
> From: Luiz Augusto von Dentz <luiz.dentz-von@nokia.com>
>
> This should indicate to the endpoint what routing the transport is using
> ---
> audio/transport.c | 4 ++++
> doc/media-api.txt | 6 ++++++
> 2 files changed, 10 insertions(+), 0 deletions(-)
Pushed upstream, though this brings up the question of who should know
the routing setting. There's no standard HCI command for it which makes
it effectively a platform specific feature which either needs to be
statically "known" in some config file or discovered though some
platform specific plugin. Since we've already got platform specific code
on the PulseAudio side (it needs to know where to write the data in the
PCM case) the knowledge might as well be there and that would make the
property unnecessary. Thoughts?
Johan
next prev parent reply other threads:[~2011-01-19 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 10:00 [PATCH 1/4] Remove IMTU and OMTU properties and return its values on Acquire reply Luiz Augusto von Dentz
2011-01-18 10:00 ` [PATCH 2/4] Updade a2dpsink to use new Acquire API Luiz Augusto von Dentz
2011-01-19 15:16 ` Johan Hedberg
2011-01-18 10:00 ` [PATCH 3/4] Add Routing property to MediaTransport interface Luiz Augusto von Dentz
2011-01-19 15:20 ` Johan Hedberg [this message]
2011-01-18 10:00 ` [PATCH 4/4] Add proper tracking mechanism to NREC Luiz Augusto von Dentz
2011-01-19 15:22 ` Johan Hedberg
2011-01-19 15:14 ` [PATCH 1/4] Remove IMTU and OMTU properties and return its values on Acquire reply Johan Hedberg
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=20110119152015.GF2112@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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