All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Using ofono HFP
Date: Tue, 28 Sep 2010 21:50:44 -0500	[thread overview]
Message-ID: <4CA2A984.4030208@gmail.com> (raw)
In-Reply-To: <AANLkTin6yP6y+TPgbrMeQ=2QnKKkpLy8-eSGTb3LZDOf@mail.gmail.com>

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

Hi Moises,

On 09/28/2010 09:33 PM, Moises Silva wrote:
> On Mon, Sep 27, 2010 at 9:26 PM, Zhang, Zhenhua <zhenhua.zhang@intel.com> wrote:
>>
>> Right. See bluez/audio/unix.c for BlueZ part SCO code that cooperate with pulseaudio. BlueZ sends SCO fd to pulseaudio via UNIX
>> type socks.
> 
> This put me in the right direction and I have a clearer idea of how to
> do it. I found odd though that it seems I need to copy the ipc.c and
> ipc.h files into my own app. Any reason they are not part of
> libbluetooth API?
> 
> Another thing that puzzles me is that supposedly DBUS >= 1.3 is needed
> to be able to pass file descriptors. However as you pointed out and
> per ipc.c the file descriptor is sent using a unix socket. Why the
> need for DBUS file descriptor passing?
> 

There are two descriptors involved here.  DBus 1.3 is needed to have
BlueZ pass the RFCOMM file descriptor to oFono for the control socket.
E.g. the socket where AT commands are being passed.  This is done by
using HandsfreeGateway and HandsfreeAgent.  See doc/hfp-api.txt in BlueZ.

The second descriptor (what ipc.c and ipc.h deal with) is used to pass
the SCO fd to PulseAudio or gStreamer.  This fd is used for Audio.
Marcel or Johan might know better, but I think the reason for ipc.c and
ipc.h was that DBus did not support fd-passing at the time BlueZ audio
integration work was being done.

Regards,
-Denis

  parent reply	other threads:[~2010-09-29  2:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-26 15:51 Using ofono HFP Moises Silva
2010-09-27  0:26 ` Denis Kenzior
2010-09-27  0:37   ` Moises Silva
2010-09-28  1:26   ` Zhang, Zhenhua
2010-09-28  2:45     ` Moises Silva
2010-09-28  3:23       ` Zhang, Zhenhua
2010-09-28  3:57         ` Moises Silva
2010-09-29  2:33     ` Moises Silva
2010-09-29  2:44       ` Zhang, Zhenhua
2010-09-29  2:50         ` Moises Silva
2010-09-29  2:50       ` Denis Kenzior [this message]
2010-10-02 22:27         ` Moises Silva
2010-10-08  3:25           ` Zhang, Zhenhua
2010-10-08 17:59             ` Moises Silva
2010-10-14 12:00               ` Pekka Pessi
2010-10-22 14:05                 ` Moises Silva

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=4CA2A984.4030208@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.org \
    /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.