Date: Thu, 11 Apr 2019 12:52:42 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Matthias Apitz <guru@unixarea.de> Cc: freebsd-wireless@freebsd.org Subject: Re: Atheros AR5B22 WLAN+Bluetooth support on FreeBSD Message-ID: <20190411125242.GA64046@FreeBSD.org> In-Reply-To: <20190411104647.GA3864@c720-r342378> References: <CADGo8CXuS6oWqbMx=g-4FipQMZh%2B4mp6u%2BOTX0pAx_M58LYLZg@mail.gmail.com> <CAJ-VmommKkeioPDEF%2BCiT9k-3pNZa39ELJsuU8C1hHZ9%2BsvRtA@mail.gmail.com> <20190409160344.GA83271@FreeBSD.org> <20190410152250.GA37191@FreeBSD.org> <20190411092758.GA6899@FreeBSD.org> <20190411104647.GA3864@c720-r342378>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 11, 2019 at 12:46:47PM +0200, Matthias Apitz wrote:
> > ...
> > I've just stumbled upon this email* of Adrian's that tells how to enable
> > Bluetooth Coexistence by adding ``hint.ath.0.btcoex_profile="wb222"'' to
> > /boot/device.hints (for AR9462 cards). I've done that, and logs tell me
> > it is enabled, but Bluetooth still does not work:
> >
> > % dmesg | grep -i coex
> > ath0: Enabling WB222 BTCOEX
> > # hccontrol inquiry
> > ... repeated attempts, plenty of devices around ...
> > Inquiry complete. Status: No error [00]
>
> I own an Acer C720 and set the same in /boot/device.hints. After boot it
> says in dmesg:
>
> $ dmesg | grep ath
> ath0: <Atheros AR946x/AR948x> mem 0xe0400000-0xe047ffff at device 0.0 on pci1
> ath0: RX status length: 48
> ath0: RX buffer size: 4096
> ath0: TX descriptor length: 128
> ath0: TX status length: 36
> ath0: TX buffers per descriptor: 4
> ath0: ath_edma_setup_rxfifo: type=0, FIFO depth = 16 entries
> ath0: ath_edma_setup_rxfifo: type=1, FIFO depth = 128 entries
> ath0: Enabling WB222 BTCOEX
> ...
>
> But I don't know how to further enable any BT device.
What does "usbconfig list" say about your BT device? Mine is
0x0930:0x021c, which is AR3012 with sflash firmware according to
the Linux' drivers/bluetooth/ath3k.c. Ubuntu users had reported*
similar problems:
"My BT seems to work to some extent.. answers to commands etc.
But it doesn't discover anything
sudo hcitool -i hci0 inq gives nothing.. even though devices
are discoverable."
Which apparently might be solved by updating the card's firmware:
commit 0a9640c85c781a4ec0c82f16fbf7333b7ce6daa6
Author: Costa Yao
Date: Wed Jul 4 17:38:09 2012 +0800
ar3k: add patch and sysconfig for Qualcomm Atheros AR9462
add patch and sysconfig for Qualcomm Atheros AR9462
Signed-off-by: Costa Yao
Signed-off-by: Ben Hutchings
This commit is from 2012, but I'm not sure how relevant it is to
FreeBSD because it seems that ATH_EEPROM_FIRMWARE is disabled by
default in our ath(4); then again, I have no real knowledge about
our drivers and how ath3k/ath9k (BT/WiFi) parts are handled.
./danfe
*) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1024884
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1394368
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190411125242.GA64046>