All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
To: Gustavo Padovan <gustavo@padovan.org>,
	Michael Knudsen <michaelknudsendk@gmail.com>,
	linux-bluetooth@vger.kernel.org,
	Michael Knudsen <m.knudsen@samsung.com>
Subject: Re: [RFC 3/3] Bluetooth:  Provide mgmt API for reading list of supported codecs
Date: Thu, 3 Jan 2013 19:16:54 -0300	[thread overview]
Message-ID: <20130103221654.GA11342@samus> (raw)
In-Reply-To: <20130103190916.GA2114@joana>

Hi Gustavo,

> 
> We think it is better to read the list of codecs from the SCO socket, we need
> to allow both oFono and PulseAudio to read them without the need of talking to
> BlueZ. Also, bluetoothd has nothing intersting to do with this information.

Take a look at the thread "CSA2: User space aspect"[1]. I have to agree
with Marcel, the mgmt command makes more sense. As how that information
will get to oFono/PulseAudio we have NewConnection() in the Profile API
and SetConfiguration() on the Media API, that may be extended (if
needed).

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


Cheers,
-- 
Vinicius

[1] http://thread.gmane.org/gmane.linux.bluez.kernel/31746

      reply	other threads:[~2013-01-03 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 12:05 [RFC 0/3] Bluetooth: mgmt API for reading supported codecs Michael Knudsen
2012-11-22 12:05 ` [RFC 1/3] Bluetooth: Add HCI feature bit definition for transparent SCO Michael Knudsen
2012-11-22 12:05 ` [RFC 2/3] Bluetooth: Add HCI Coding Format definitions Michael Knudsen
2012-11-22 12:05 ` [RFC 3/3] Bluetooth: Provide mgmt API for reading list of supported codecs Michael Knudsen
2013-01-03 19:09   ` Gustavo Padovan
2013-01-03 22:16     ` Vinicius Costa Gomes [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=20130103221654.GA11342@samus \
    --to=vinicius.gomes@openbossa.org \
    --cc=gustavo@padovan.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=m.knudsen@samsung.com \
    --cc=michaelknudsendk@gmail.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 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.