public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] fleshing out audio daemon scenarios
Date: Mon, 04 Jun 2007 17:25:48 +0200	[thread overview]
Message-ID: <1180970748.13429.59.camel@violet> (raw)
In-Reply-To: <d89ddf300706031341t1f38d12ayd8752280f93d9f28@mail.gmail.com>

Hi Brad,

> So I think next step will be to tell the audio daemon to put a headset
> in connected state and then with a basic plugin (no options) put it in
> streaming state and send some audio to it.
> 
> What does the command-line dbus injection stuff look like to get the
> audio daemon to connect to a set? 
> 
> I'll start documenting the minimal approach on the wiki.

no idea. Simply start playing with the code. A lot of stuff will fall
into place automatically and some other stuff needs more thinking, but
without actually trying to do it, we don't know what works and where we
have to fix stuff.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-06-04 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02  4:43 [Bluez-devel] fleshing out audio daemon scenarios Brad Midgley
2007-06-03  8:13 ` Marcel Holtmann
2007-06-03 20:41   ` Brad Midgley
2007-06-04 15:25     ` Marcel Holtmann [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=1180970748.13429.59.camel@violet \
    --to=marcel@holtmann.org \
    --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