From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] avrcp and dbus
Date: Thu, 01 Dec 2005 09:21:37 -0700 [thread overview]
Message-ID: <438F2311.9050103@xmission.com> (raw)
In-Reply-To: <1133371554.18079.37.camel@blade>
Marcel
>>I have my test app ("avrecv") accepting connections and ack'ing
>>passthrough commands.
>
> sounds promising. Keep up with it.
Ok, well I found almost everything I need. The only thing I'm not
finding is the format for a volume up/down sent back to the headset.
Have you seen with your sniffer what those frames look like?
I'm assuming it's also sent as a passthrough to the panel device but I'm
guessing/experimenting to find the value of the volume up/down operands :(
Passthrough may not be right for volume changes... the headset neither
acks nor naks those commands sent to its panel.
> I think it is far to earlier to think about D-Bus integration.
Fine. Once we have real a2dp alsa integration then it'll be more clear
how avrcp fits in.
brad
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-12-01 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 16:32 [Bluez-devel] avrcp and dbus Brad Midgley
2005-11-30 17:25 ` Marcel Holtmann
2005-12-01 16:21 ` Brad Midgley [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=438F2311.9050103@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).