Re: [Bluez-devel] Patch: inheritance problem in gsta2dpsink

Fabien Chevalier
2007-10-09T08:01:51Z

[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]

Hi all,

Adding more pepper on this already spicy conversation. :-)
> Hey
>
> I asked Marcel the same thing a while back.
>
> It would make sense to factor the common stuff into unix.c or create
> an ipc.c for that. We can link these to each plugin without messing
> around with libraries.
>
> Brad
>
> On 10/8/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>> Hi Luiz,
>>
>>> I guess we really need a tiny library for ipc, we dont want to
>>> duplicate code from
>>> pcm_bluetooth.c again in a2dpsink, it might happen that someone need this
>>> in another plugin or so.
>> no no and no. I don't care what other plugins (outside bluez-utils) need
>> and want at the moment.

Well, *I do* care.
As i told you back in Montpellier, i need a way to plug an external
(proprietary) hardware accelerated audio system onto the audio service.
In fact i could start working on such a library right away, provided
that it is LGPL, so that i can link a proprietary stuff on top of it.
Even if it is not packaged as an external library at first, provided i
can somehow copy the code out of bluez tree and rebuild a LGPL library
out of it would be acceptable as a first step. :-)
If that can't be done then i'm gonna go grumble in a corner and we will
have missed an opportunity to move the bluez audio system forward. :-(
And remembering what Marcel told us during the meeting, the IPC API is
not public because "we don't really know what we're doing".
My answer to that is:
- having worked on audio stuff for some time now, i think i know what
i would be doing if i was to work on this API : which mean it would be
made stable pretty quickly.
- We'd better start stabilizing the API before too much effort has
been put on the gstreamer plugin or any other plugin, otherwise we will
have to fix them all afterwards.

A last thing : this is likely to be a one time offer, because i need to
start working on this stuff as soon as today. If we miss the window i
won't be able to spent company time on this library, which mean i will
only be able to get involved on my spare time, which i kind of lack
these days...

As always : comments are welcomed !!

>> It is perfectly fine to link an object file more
>> than once.
Sure it is, we just loose some disk space.

Cheers,

Fabien

[-- Attachment #2: fchevalier.vcf --]
[-- Type: text/x-vcard, Size: 242 bytes --]

begin:vcard
fn:Fabien CHEVALIER
n:CHEVALIER;Fabien
org:SILICOM
adr:;;4 rue de Jouanet; RENNES ATALANTE;;35700;FRANCE
email;internet:fchevalier@silicom.fr
title:Software & Studies Engineer
tel;work:+33 (0) 2 99 84 17 17
version:2.1
end:vcard

[-- Attachment #3: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]