From: Mat Martineau <mathewm@codeaurora.org>
To: Suraj Sumangala <suraj@Atheros.com>
Cc: "Gustavo F. Padovan" <padovan@profusion.mobi>,
Arun Kumar SINGH <arunkr.singh@stericsson.com>,
Anurag Gupta <anurag1303@gmail.com>,
Peter Krystad <pkrystad@codeaurora.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: BT 3.0 HS Support in BlueZ
Date: Thu, 19 May 2011 09:58:04 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1105190939240.22147@localhost6.localdomain6> (raw)
In-Reply-To: <4DD4AB14.9050401@Atheros.com>
On Thu, 19 May 2011, Suraj Sumangala wrote:
> Hi Mat,
>
> On 5/19/2011 2:28 AM, Mat Martineau wrote:
>>
>> Gustavo,
>>
>> On Mon, 9 May 2011, Gustavo F. Padovan wrote:
>>
... snip ...
>>>
>>> Isn't Extended Flow Specification a required feature for AMP? I haven't
>>> seen
>>> it in your implementation.
>>
>> Extended Flowspec is needed to create an L2CAP channel directly on
>> AMP, but the implementation you're looking at does not implement the
>> "create channel" feature. Channels are created on BR/EDR and moved
>> to AMP, which does not require extended flowspec.
>>
>
> Why don't we have to use EFS for channels moved from BDR? Is it because we
> assume that the QoS provided by AMP will be better than BDR?
Only "Best Effort" is supported by this implementation so QoS is
equivalent on either controller type. EFS is optional when creating
channels on BR/EDR, and the spec does not require EFS when moving to a
Best Effort AMP link. We've extensively interop'd AMP channel moves
without EFS.
--
Mat Martineau
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-05-19 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 17:36 BT 3.0 HS Support in BlueZ Anurag Gupta
2011-04-19 18:04 ` Gustavo F. Padovan
2011-05-05 7:26 ` Arun Kumar SINGH
2011-05-05 14:13 ` Luiz Augusto von Dentz
2011-05-05 20:15 ` Gustavo F. Padovan
2011-05-05 23:27 ` Mat Martineau
2011-05-08 12:27 ` Arun K. Singh
2011-05-09 22:52 ` Gustavo F. Padovan
2011-05-18 20:58 ` Mat Martineau
2011-05-19 5:31 ` Suraj Sumangala
2011-05-19 16:58 ` Mat Martineau [this message]
2011-05-19 18:40 ` Gustavo F. Padovan
2011-05-20 5:17 ` Suraj Sumangala
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=alpine.DEB.2.00.1105190939240.22147@localhost6.localdomain6 \
--to=mathewm@codeaurora.org \
--cc=anurag1303@gmail.com \
--cc=arunkr.singh@stericsson.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
--cc=pkrystad@codeaurora.org \
--cc=suraj@Atheros.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox