Received: from relay9-d.mail.gandi.net (relay9-d.mail.gandi.net [217.70.183.199]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id DB4FE781B7C for <~alpine/devel@lists.alpinelinux.org>; Fri, 31 Jan 2020 08:43:56 +0000 (UTC) Received: from webmail.gandi.net (webmail22.sd4.0x35.net [10.200.201.22]) (Authenticated sender: michel.piquemal@ipik.org) by relay9-d.mail.gandi.net (Postfix) with ESMTPA id 63939FF80B for <~alpine/devel@lists.alpinelinux.org>; Fri, 31 Jan 2020 08:43:56 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 31 Jan 2020 09:43:56 +0100 From: macmpi To: ~alpine/devel@lists.alpinelinux.org Subject: Fixing Pi Bluetooth (audio) support Message-ID: <78d3ad30b7e1a3f2327bfa07f1e28f0a@ipik.org> X-Sender: spam@ipik.org User-Agent: Roundcube Webmail/1.3.8 Current mdev.conf statement for loading bluetooth firmware on Pi devices has a number of pitfalls, particularly when it comes to transmit significant data streams, like for a2dp audio: - serial port connection baudrate is insufficient - btattach does not work properly, and hciattach (though depreciated) remains the only option for now (consistently reported in bluez-alsa github issues & al.) As a reference one can refer to how Pi Foundation do setup bluetooth [1], which reliably works. I tested that script on Alpine (with one slight edit as /dev/serial is /dev/ttyAMA0), it just works great. I can see 2 options to fix that for good in Alpine: 1) integrate that patched btuart script in /lib/mdev/ and have mdev.conf rule link to it 2) create a new pi-bluetooth package that adds a pi-bluetooth service at boot, which uses same script Which would be the proposed option? Thanks for feedback and suggestions [1]https://github.com/RPi-Distro/pi-bluetooth/blob/master/usr/bin/btuart