From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Mat Martineau <mathewm@codeaurora.org>
Cc: Arun Kumar SINGH <arunkr.singh@stericsson.com>,
Anurag Gupta <anurag1303@gmail.com>,
pkrystad@codeaurora.org, linux-bluetooth@vger.kernel.org
Subject: Re: BT 3.0 HS Support in BlueZ
Date: Mon, 9 May 2011 19:52:47 -0300 [thread overview]
Message-ID: <20110509225246.GB2203@joana> (raw)
In-Reply-To: <alpine.DEB.2.00.1105051548540.4213@localhost6.localdomain6>
Hi Mat,
* Mat Martineau <mathewm@codeaurora.org> [2011-05-05 16:27:17 -0700]:
>
> On Thu, 5 May 2011, Gustavo F. Padovan wrote:
>
> > Hi Arun,
> >
> > * Arun Kumar SINGH <arunkr.singh@stericsson.com> [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.
--
Gustavo F. Padovan
http://profusion.mobi
next prev parent reply other threads:[~2011-05-09 22:52 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 [this message]
2011-05-18 20:58 ` Mat Martineau
2011-05-19 5:31 ` Suraj Sumangala
2011-05-19 16:58 ` Mat Martineau
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=20110509225246.GB2203@joana \
--to=padovan@profusion.mobi \
--cc=anurag1303@gmail.com \
--cc=arunkr.singh@stericsson.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mathewm@codeaurora.org \
--cc=pkrystad@codeaurora.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).