All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander van Grieken <sander@outrightsolutions.nl>
To: linux-bluetooth@vger.kernel.org
Subject: AVRCP future
Date: Wed, 1 Sep 2010 16:03:02 +0200	[thread overview]
Message-ID: <201009011603.02153.sander@outrightsolutions.nl> (raw)

Hi All,

I've been looking into AVRCP a bit lately, since I'm interested in the 'Remote Control 
from Separate Controller' usecase as described in the AVRCP spec, section 2.3.1.1.

However, from the BlueZ source, it seems an AVRCP connection is only set up/allowed when 
there is a AVD sink present, which is in violation of the bluetooth spec, section 2.3.2

Also, the recent progress made by João Paulo Rechi Vita bind the control and audio stream 
closely together (basically disabling the control once audio is not pulseaudio-routed to 
the bluetooth peer).

Now, my questions:

- Is anyone working on AVRCP, besides jprvita?
- Aside from the proposed D-Bus API in doc/control-api.txt, has anyone done some research 
how an AVRCP1.4 interface should look?
- Are there objections to conforming to section 2.3.2, i.e. untying the AVRCP connection 
from the A2DP connection?

I'm willing to put some effort in improving AVRCP, but before I go off blindly coding such 
stuff, please give as much feedback as possible :)

grtz,
Sander

             reply	other threads:[~2010-09-01 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01 14:03 Sander van Grieken [this message]
2010-09-01 18:57 ` AVRCP future Johan Hedberg
2010-09-02  8:20   ` Sander van Grieken
2010-09-02 12:56     ` Luiz Augusto von Dentz
2010-09-02 21:18       ` Sander van Grieken

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=201009011603.02153.sander@outrightsolutions.nl \
    --to=sander@outrightsolutions.nl \
    --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.