linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Danis <frederic.danis@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC] doc: add org.bluez.Handsfree interface
Date: Fri, 19 Aug 2011 11:08:49 +0200	[thread overview]
Message-ID: <4E4E2821.5040206@linux.intel.com> (raw)
In-Reply-To: <20110812135543.GA4168@joana>

Hello Gustavo,

Le 12/08/2011 15:55, Gustavo Padovan a écrit :
> * Frédéric Danis<frederic.danis@linux.intel.com>  [2011-08-12 15:28:00 +0200]:
>
>> This change allows to share the same interface for both Handsfree HF
>> and AG (only diffrence is interface name), and most part of the code.
>>
>> This will imply to rename and update audio/gateway.[ch] to be more hfp
>> generic (moving it to audio/hfp.[ch], renaming APIs from gateway_...()
>> to hfp_...()).
>
> what will be the future of the current implementation of the HFP Audio Gateway
> implementation in BlueZ. Will it be  deprecated?
>
> 	Gustavo

I do not know what will be the future, this proposal just add a new 
interface allowing an external application (like oFono) to implement the 
Handsfree Audio Gateway profile in a similar way than for current 
Handsfree headset.

This allows the application to focus on profile implementation, letting 
management of Bluetooth part (SDP advertisement, connection, 
authentication, authorization, ...) to BlueZ.

Fred

-- 
Frederic Danis                            Open Source Technology Centre
frederic.danis@intel.com                              Intel Corporation


      reply	other threads:[~2011-08-19  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 13:28 [RFC] doc: add org.bluez.Handsfree interface Frédéric Danis
2011-08-12 13:55 ` Gustavo Padovan
2011-08-19  9:08   ` Frederic Danis [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=4E4E2821.5040206@linux.intel.com \
    --to=frederic.danis@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).