Return-Path: Message-ID: <4DD4AB14.9050401@Atheros.com> Date: Thu, 19 May 2011 11:01:00 +0530 From: Suraj Sumangala MIME-Version: 1.0 To: Mat Martineau CC: "Gustavo F. Padovan" , Arun Kumar SINGH , Anurag Gupta , "pkrystad@codeaurora.org" , "linux-bluetooth@vger.kernel.org" Subject: Re: BT 3.0 HS Support in BlueZ References: <20110419180425.GA2476@joana> <20110505201531.GE2098@joana> <20110509225246.GB2203@joana> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Mat, On 5/19/2011 2:28 AM, Mat Martineau wrote: > > Gustavo, > > On Mon, 9 May 2011, Gustavo F. Padovan wrote: > >> Hi Mat, >> >> * Mat Martineau [2011-05-05 16:27:17 -0700]: >> >>> >>> On Thu, 5 May 2011, Gustavo F. Padovan wrote: >>> >>>> Hi Arun, >>>> >>>> * Arun Kumar SINGH [2011-05-05 09:26:58 +0200]: >>>> >>>>> Hi Gustavo, >>>>> >>>>>>> Does anybody know if >>>>>> bluetooth 3.0 HS spec is >>>>>> supported in BlueZ? >>>>>>> Is AMP supported in BlueZ? >>>>>> >>>>>> There is two different >>>>>> implementations, one by >>>>>> Atheros and another by QuIC. >>>>>> Both never reach upstream, >>>>>> if you look to the list logs >>>>>> you will find them. >>>>> >>>>> >>>>> Any hopes of getting this unified version upstream anytime in near future? I guess this has been on the cards for some time now given that merge process started last august. >>>> >>>> I'm interested in have this on the stack but it doesn't depend on me. >>>> Patches for this are not arriving to the mailing list. Actually we had no real >>>> feedback for AMP since the meeting in Boston. >>> >>> Gustavo, Arun: >>> >>> We do still plan to upstream our Bluetooth 3.0 + HS implementation. I >>> will start work on upstreaming later this month, but I need to merge >>> in all of the recent L2CAP refactoring changes. >>> >>> Also note that Qualcomm and Atheros have announced a merger. >>> >>> You can find the kernel AMP implementation in the codeaurora.org >>> Android git trees: >>> >>> git://codeaurora.org/kernel/msm.git >>> https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=summary >>> >>> The android-msm-2.6.35 and msm-2.6.38 branches contain the AMP code. >>> >>> >>> Please let me know if you have any other questions about AMP. >> >> 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? Regards Suraj