From: event <event.riga@gmail.com>
To: Michele Noberasco <michele.noberasco@tiscali.it>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] BlueZ support for audio gateway role (HFP/HSP)
Date: Fri, 23 Jan 2009 09:34:36 +0200 [thread overview]
Message-ID: <664d43d60901222334h4e1cb498hf8b3b01433e3ab92@mail.gmail.com> (raw)
In-Reply-To: <2C0A35D3-4DD9-4089-8061-F596A8A5A4B8@tiscali.it>
On Thu, Jan 22, 2009 at 18:43, Michele Noberasco
<michele.noberasco@tiscali.it> wrote:
> Hello list,
>
> some time ago my company tasked me to develop this feature, but
> unfortunately they changed their mind before I could complete development. I
> sought to finish it on my own, but my spare time is dwindling lately.
>
> So I thought that someone might be interested to pick development up where I
> left it off.
>
> If anyone is interested, I'm willing to provide the source code of my own
> work. I implemented it for HSP up to the actual creation of audio channels
> (excluded). Mostly implemented and working is rfcomm connection and event
> passing ("RING", ...).
>
> My modifications are made against bluez-3.36 (latest version of the 3.x
> branch), but I think it should be trivial to forward port them to bluez 4
> (if you have a look at audio/gateway.c you will notice there is nothing in
> there), so I would provide a patch that applies against that codebase.
>
> Best regards,
> Michele Noberasco
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Hello Michele,
I'm doing the same function just now :).
So please send your code and I will look there for something I've missed.
Vale,
Leonid Movshovich
next prev parent reply other threads:[~2009-01-23 7:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 16:43 [PATCH] BlueZ support for audio gateway role (HFP/HSP) Michele Noberasco
2009-01-23 7:34 ` event [this message]
2009-01-23 8:32 ` Michele Noberasco
2009-01-28 5:54 ` Marcel Holtmann
2009-01-29 8:34 ` Michele Noberasco
2009-01-29 8:46 ` event
2009-02-05 5:06 ` Zhao Forrest
2009-02-05 7:22 ` event
2009-02-09 5:38 ` Zhao Forrest
2009-02-09 9:49 ` event
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=664d43d60901222334h4e1cb498hf8b3b01433e3ab92@mail.gmail.com \
--to=event.riga@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michele.noberasco@tiscali.it \
/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