public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luiz Augusto von Dentz" <luiz.dentz@gmail.com>
To: "Fabien Chevalier" <fabchevalier@free.fr>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>,
	Johan Hedberg <johan.hedberg@nokia.com>,
	Brad Midgley <bmidgley@xmission.com>
Subject: Re: [Bluez-devel] Patch: inheritance problem in gsta2dpsink
Date: Tue, 9 Oct 2007 18:17:59 -0300	[thread overview]
Message-ID: <2d5a2c100710091417s1dc1adddh4e3020b81595fe24@mail.gmail.com> (raw)
In-Reply-To: <470B5184.1070507@free.fr>

Hi Fabien

On 10/9/07, Fabien Chevalier <fabchevalier@free.fr> wrote:
> I was more thinking of as a complete rewrite of ipc.h (we should find it
> another name btw : lets call it newipc.h for now ;-) ).
> I already started thinking to how i would like to see it look.
> It should be relatively lightweight, expose directly a message based API
> (as you would find on most RTOS), with just a few functions to create
> and free a session to the audio daemon, and to retrieve the data socket,
> so that each user wouldn't have to know the tricks about ancilliary data
> passing :-)
> I fact it should be so lightweight that i think we could static inline
> all the functions, and thus we wouldn't even need a *.c file.
>
> I'm waiting for comments, int the meantime i'm gonna start drafting a
> newipc.h :-)

Good, I need to rework ipc anyway since there is no capabilities exchange
between the daemon and the plugin and that cause some problems to make
plugin able choose codec parameters. Right now the daemon choose the best
option it find and return to plugin, we should change that so the plugin could
get the device capabilities and choose the best option by it own.

Thiago is having a good progress with gstreamer plugin, so this is a very good
opportunity to work together and make it happen.

My name suggestion is: libbtaudio

Btw I have no problem with LGPL.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-10-09 21:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01 21:31 [Bluez-devel] Patch: inheritance problem in gsta2dpsink thiagoss
2007-10-05 19:36 ` thiagoss
2007-10-08 17:56   ` Luiz Augusto von Dentz
2007-10-08 22:56     ` Marcel Holtmann
2007-10-09  1:32       ` Brad Midgley
2007-10-09  8:01         ` Fabien Chevalier
2007-10-09  8:44           ` Marcel Holtmann
2007-10-09 10:01             ` Fabien Chevalier
2007-10-09 21:17               ` Luiz Augusto von Dentz [this message]
2007-10-10  0:51                 ` Marcel Holtmann
2007-10-10 13:31                   ` Luiz Augusto von Dentz
2007-10-10 14:09                     ` 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=2d5a2c100710091417s1dc1adddh4e3020b81595fe24@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bmidgley@xmission.com \
    --cc=fabchevalier@free.fr \
    --cc=johan.hedberg@nokia.com \
    /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