From: "Peter Krystad" <pkrystad@codeaurora.org>
To: "'Greg Hazel'" <ghazel@gmail.com>,
"'Andrei Emeltchenko'" <andrei.emeltchenko.news@gmail.com>
Cc: <linux-bluetooth@vger.kernel.org>
Subject: RE: BT_AMP_POLICY and RFCOMM
Date: Tue, 24 Jan 2012 09:45:48 -0800 [thread overview]
Message-ID: <003501ccdac0$022a89e0$067f9da0$@org> (raw)
In-Reply-To: <8B1F83F9-649A-4B59-A620-774A60E64D2C@gmail.com>
Greg,
> -----Original Message-----
> From: linux-bluetooth-owner@vger.kernel.org [mailto:linux-bluetooth-owner@vger.kernel.org]
> On Behalf Of Greg Hazel
> Sent: Tuesday, January 24, 2012 1:57 AM
> To: Andrei Emeltchenko
> Cc: linux-bluetooth@vger.kernel.org
> Subject: Re: BT_AMP_POLICY and RFCOMM
>
> On Jan 24, 2012, at 12:57 AM, Andrei Emeltchenko wrote:
> > On Tue, Jan 24, 2012 at 12:36:23AM -0800, Greg Hazel wrote:
> >> On Jan 24, 2012, at 12:27 AM, Andrei Emeltchenko wrote:
> >>> On Mon, Jan 23, 2012 at 08:15:16PM -0800, Greg Hazel wrote:
> >>>>
> >>>> I'm trying to set BT_AMP_POLICY on an RFCOMM socket to
> >>>> BT_AMP_POLICY_PREFER_AMP. In return I'm getting "Operation not supported
> >>>
> >>> BTW: Why would you need to set this? Functionality is not supported yet so
> >>> nothing will change.
> >>
> >> Oh, I had not made it far enough into bluez to notice it had not been implemented. My
> question still stands I suppose, but is obviously predicated on support being added
> eventually.
Since l2cap ertm is required for channels on AMP the rfcomm layer is unnecessary, it makes
more sense for obex profiles to be modified to use l2cap ertm sockets directly, which do/will
support AMP.
> Is this the right mailing list to ask about the AMP bluetooth work contained in msm and
> android-msm?
Probably not :)
E-mail me or post to https://www.codeaurora.org/forums/viewforum.php?f=4
Peter.
--Peter Krystad
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2012-01-24 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 4:15 BT_AMP_POLICY and RFCOMM Greg Hazel
2012-01-24 8:27 ` Andrei Emeltchenko
2012-01-24 8:36 ` Greg Hazel
2012-01-24 8:57 ` Andrei Emeltchenko
2012-01-24 9:57 ` Greg Hazel
2012-01-24 17:45 ` Peter Krystad [this message]
2012-01-24 20:59 ` ghazel
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='003501ccdac0$022a89e0$067f9da0$@org' \
--to=pkrystad@codeaurora.org \
--cc=andrei.emeltchenko.news@gmail.com \
--cc=ghazel@gmail.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