linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] avrcp and dbus
Date: Wed, 30 Nov 2005 09:32:49 -0700	[thread overview]
Message-ID: <438DD431.1090607@xmission.com> (raw)

Hi

I have my test app ("avrecv") accepting connections and ack'ing
passthrough commands. Most or all headsets are going to be sending
passthrough only, but we will nak other commands when I figure out how
the nak looks.

If you have avrecv running when you start sending audio to the set, the
headset will turn around and make the avrcp connection. I don't know how
you use the play button to *initiate* the player however... :(

I would like to make this app a multithreaded daemon and hook it up to
dbus for both receiving events from headsets and relaying things back to
the headset (eg volume changes). I will run one thread per connection
and select() between data from the headset and dbus commands for the
same l2cap connection...

Does the dbus approach sound reasonable? Any tips for where to start
with dbus? (I've never written for it)

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

             reply	other threads:[~2005-11-30 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30 16:32 Brad Midgley [this message]
2005-11-30 17:25 ` [Bluez-devel] avrcp and dbus Marcel Holtmann
2005-12-01 16:21   ` Brad Midgley

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=438DD431.1090607@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).