public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Stockwell" <dstockwell@frequency-one.com>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: <linux-bluetooth@vger.kernel.org>
Subject: Re: FYI, regarding AVRCP
Date: Mon, 5 Jan 2009 23:39:24 -0600	[thread overview]
Message-ID: <EE05154550284C96A30F932447EC944F@freqonedev> (raw)
In-Reply-To: 1231210590.13304.21.camel@californication

Hi Marcel...got your previous responses, thanks.  Believe it or not, 
this list works pretty well.

Regards...


> Hi David,
>
> so lets try this again since it seems vger eat my last reply :(
>
>> 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.
>
> great, because I was going to ping you about that part :)
>
>> 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?
>
> Yeah. Looks good to me.
>
> Regards
>
> Marcel
>
> 

      reply	other threads:[~2009-01-06  5:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-20  2:24 FYI, regarding AVRCP David Stockwell
2009-01-06  2:56 ` Marcel Holtmann
2009-01-06  5:39   ` David Stockwell [this message]

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=EE05154550284C96A30F932447EC944F@freqonedev \
    --to=dstockwell@frequency-one.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --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