From: "David Stockwell" <dstockwell@frequency-one.com>
To: <linux-bluetooth@vger.kernel.org>
Subject: FYI, regarding AVRCP
Date: Fri, 19 Dec 2008 20:24:36 -0600 [thread overview]
Message-ID: <6F8E4829F275487887832A64E4125229@freqonedev> (raw)
Marcel, Johan, et al,
Since our meeting in PortlandI have been busy dealing with both "day
job" issues, as well as finishing up some Intellectual Property issues
surrounding my ongoing evening/weekend project, of which AVRCP and my
remote are a small but critical part. Within the next two weeks I will
reengage AVRCP and expect to soon bring it up to 1.3 (metadata transfer)
as we discussed in Portland. Sorry it has taken so long.
With regard to the question from Park Chan-Yeol, I suggest we consider a
Bluez/DBUS "version" property (for simplicity, a String) for the
org.bluez.Control interface, to allow users to know just what they are
dealing with. Any thoughts?
David Stockwell
next reply other threads:[~2008-12-20 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 2:24 David Stockwell [this message]
2009-01-06 2:56 ` FYI, regarding AVRCP Marcel Holtmann
2009-01-06 5:39 ` 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=6F8E4829F275487887832A64E4125229@freqonedev \
--to=dstockwell@frequency-one.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