From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] org.bluez.Audio
Date: Sun, 10 Dec 2006 16:51:17 +0100 [thread overview]
Message-ID: <457C2CF5.9040007@free.fr> (raw)
In-Reply-To: <457655A2.6030001@xmission.com>
Hi Brad & Marcel,
I got a number of interrogations regarding the various methods/signals
exposed here. I noticed a few things that won't work. To be able to
pinpoint these issues one by one, i think there is a need to draw some
diagrams that show the dynamic aspects of things. I'm gonna try drawing
a few of those before the end of the year : hopefully i will find some
spare time as i'm gonna be in hollidays from Xmas till new year...
Cheers,
Fabien
> Marcel
>
> I rewrote the dbus proposal. If what's here looks ok we can start
> thinking about the named pipe, ipc, or whatever we use for sending audio
> and file descriptors around.
>
> http://bluetooth-alsa.sourceforge.net/future.html
>
> Brad
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-12-10 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 5:31 [Bluez-devel] org.bluez.Audio Brad Midgley
2006-12-06 20:43 ` Jose Vasconcellos
2006-12-06 21:24 ` Brad Midgley
2006-12-10 15:51 ` Fabien Chevalier
2006-12-12 16:45 ` Brad Midgley
2006-12-12 19:53 ` Fabien Chevalier
2006-12-12 20:24 ` Brad Midgley
2006-12-10 15:51 ` Fabien Chevalier [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=457C2CF5.9040007@free.fr \
--to=fabchevalier@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.