From: "David Stockwell" <dstockwell@frequency-one.com>
To: "Shivendra Agrawal" <ag.shivendra@gmail.com>,
<linux-bluetooth@vger.kernel.org>
Subject: Re: AVRCP 1.4 : Future on Target Role
Date: Tue, 19 Oct 2010 20:40:21 -0500 [thread overview]
Message-ID: <7175717E42B642A0B74D2E3060DF6FDA@freqoneremote> (raw)
In-Reply-To: <AANLkTi=jnPSWAiYWWE6Z_oPswA-uXSOWWMfZKfcfgegH@mail.gmail.com>
Your observation that AVRCP 1.3 is not implemented is correct, and I am
(finally!) actively back at work on implementing AVRCP 1.3, based on the
control-api.txt documentation. IMO, this would be a good foundation for
1.4.
For my purposes, I am not keen on 1.4, personally I find it overcomplicated
for what should be a relatively simple interface; however, obviously others
differ.
Do you have an AVRCP CT (other than a headset) that you are working with?
David Stockwell
--------------------------------------------------
From: "Shivendra Agrawal" <ag.shivendra@gmail.com>
Sent: Tuesday, October 19, 2010 1:16 AM
To: <linux-bluetooth@vger.kernel.org>
Subject: AVRCP 1.4 : Future on Target Role
> Hi All,
>
> I have been looking at AVRCP 1.4 in BlueZ and intending to
> enhance/develop this profile for the target role. I have been
> following the discussion initiated by Sander van Grieken earlier last
> month, and as I understand, they are premitive and has scope for
> further enhancements.
>
> In the current BlueZ implementation, control-api.txt mentions few
> methods e.g. SendVendoeDependent, ChangePlayback..., that are not
> referred/implemented in the code, or I may be unable to find at right
> place.
> Further, there are some more AVRCP 1.4 TG specific Notify and Browsing
> commands that can be added.
>
> I am willing to define some preliminary interface APIs for Target
> Media Applications to register itself with BlueZ, and would come back
> with some idea proposal for your suggestions on improvements.
>
> I am keen to receive your feedback with some ideas and thoughts to put
> my effort in right direction.
>
> Question:
> Is anyone working on AVRCP 1.4 Target role profile development?
>
> Regards,
> Shivendra
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-20 1:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 6:16 AVRCP 1.4 : Future on Target Role Shivendra Agrawal
2010-10-19 8:31 ` Luiz Augusto von Dentz
2010-10-20 1:40 ` David Stockwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-19 9:47 Sander van Grieken
2010-10-19 16:14 ` Luiz Augusto von Dentz
2010-10-20 4:27 ` Shivendra Agrawal
2010-10-20 22:24 ` David Stockwell
2010-10-21 8:30 ` Waldemar.Rymarkiewicz
2010-10-21 21:27 ` David Stockwell
2010-10-23 15:50 ` João Paulo Rechi Vita
[not found] ` <AANLkTimGO9-_odEX-=8Lttw1D3M=X+DWJH0w45W8nMtT@mail.gmail.com>
[not found] ` <AANLkTi=g+8UDsSQBnqBWk=Ly=xCmfvwX_ZCMsn_kU9Fb@mail.gmail.com>
2010-10-27 6:57 ` shivendra.agrawal@stericsson.com
2010-10-27 7:33 ` Gustavo F. Padovan
2010-10-27 8:46 ` shivendra.agrawal@stericsson.com
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=7175717E42B642A0B74D2E3060DF6FDA@freqoneremote \
--to=dstockwell@frequency-one.com \
--cc=ag.shivendra@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox