From owner-freebsd-bluetooth@FreeBSD.ORG Sun Jun 9 07:05:47 2013 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B4B871D3; Sun, 9 Jun 2013 07:05:47 +0000 (UTC) (envelope-from plunky@ogmig.net) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) by mx1.freebsd.org (Postfix) with ESMTP id 716541B24; Sun, 9 Jun 2013 07:05:47 +0000 (UTC) Received: from mfilter16-d.gandi.net (mfilter16-d.gandi.net [217.70.178.144]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id D0B9D41C06D; Sun, 9 Jun 2013 09:05:35 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter16-d.gandi.net Received: from relay5-d.mail.gandi.net ([217.70.183.197]) by mfilter16-d.gandi.net (mfilter16-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id Tr2aj+A6lBkm; Sun, 9 Jun 2013 09:05:34 +0200 (CEST) X-Originating-IP: 31.68.199.240 Received: from galant.ogmig.net (unknown [31.68.199.240]) (Authenticated sender: plunky@ogmig.net) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id F177741C05C; Sun, 9 Jun 2013 09:05:32 +0200 (CEST) Received: by galant.ogmig.net (Postfix, from userid 1000) id CE1522600B0; Sun, 9 Jun 2013 08:05:22 +0100 (BST) Date: Sun, 9 Jun 2013 08:05:22 +0100 (BST) From: Iain Hibbert To: Adrian Chadd Subject: Re: What's it going to take to get basic A2DP support into -HEAD? In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-bluetooth@freebsd.org X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jun 2013 07:05:47 -0000 On Sat, 8 Jun 2013, Adrian Chadd wrote: > On 8 June 2013 23:48, Iain Hibbert wrote: > > On Sat, 8 Jun 2013, Adrian Chadd wrote: > > > >> So, given that these headphones pair, what would it take to write up a > >> basic A2DP profile with the minimum-supported codec, and then route > >> audio to it? > > > > it is probably a couple of weeks work; the specification document is not > > that thick.. > > Yeah, I see that. And lots of the codec types are optional, right? I guess so.. and I haven't investigated, how many devices would be able to accept anything except the minimum required anyway. iain