Date: Sun, 9 Jun 2013 08:05:22 +0100 (BST) From: Iain Hibbert <plunky@ogmig.net> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-bluetooth@freebsd.org Subject: Re: What's it going to take to get basic A2DP support into -HEAD? Message-ID: <alpine.NEB.2.00.1306090800230.681@galant.ogmig.net> In-Reply-To: <CAJ-Vmom7X4BACQ8x_B6u=Zef7TAa8Gn4HdiB77pWU36hNJVQaA@mail.gmail.com> References: <CAJ-VmokxtmkqXBPXfvKzRJ2qxGUe5qN0D-pvsJP-7djDdVE4ag@mail.gmail.com> <alpine.NEB.2.00.1306090731410.584@galant.ogmig.net> <CAJ-Vmom7X4BACQ8x_B6u=Zef7TAa8Gn4HdiB77pWU36hNJVQaA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 8 Jun 2013, Adrian Chadd wrote: > On 8 June 2013 23:48, Iain Hibbert <plunky@ogmig.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.NEB.2.00.1306090800230.681>