From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] avrcp start
Date: Tue, 29 Nov 2005 19:08:33 -0700 [thread overview]
Message-ID: <438D09A1.4030909@xmission.com> (raw)
In-Reply-To: <438CD881.8060405@xmission.com>
guys
> little stuck. I am not finding constants for anything they talk about in
> AVRCP. Things like play/track back/track forward operands, opcodes
i just found the snippet in the docs about how they piggyback on 1394
for a lot of this stuff, so now i'm digging there. if nothing else, i'll
look for the constants in the linux 1394 headers.
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
next prev parent reply other threads:[~2005-11-30 2:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 17:24 [Bluez-devel] avrcp start Brad Midgley
2005-11-29 20:37 ` Marcel Holtmann
2005-11-29 22:38 ` Brad Midgley
2005-11-30 2:08 ` Brad Midgley [this message]
2005-11-30 3:29 ` Marcel Holtmann
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=438D09A1.4030909@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).