Return-Path: <cyrus@holtmann.org>
Subject: Re: BT_AMP_POLICY and RFCOMM
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Greg Hazel <ghazel@gmail.com>
In-Reply-To: <20120124082739.GA19238@aemeltch-MOBL1>
Date: Tue, 24 Jan 2012 00:36:23 -0800
Cc: linux-bluetooth@vger.kernel.org
Message-Id: <E07C31FC-9B74-4DBA-98F5-765E95B256B7@gmail.com>
References: <D0339DC2-78B0-427D-9FC3-704725A88020@gmail.com> <20120124082739.GA19238@aemeltch-MOBL1>
To: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

On Jan 24, 2012, at 12:27 AM, Andrei Emeltchenko wrote:

> On Mon, Jan 23, 2012 at 08:15:16PM -0800, Greg Hazel wrote:
>> Hi,
>> 
>> 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.

Out of curiosity, is there a bluetooth stack which does support AMP yet?

-Greg