El día jueves, abril 11, 2019 a las 12:52:42p. m. +0000, Alexey Dokuchaev 
escribió:

> > 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:

# usbconfig list
ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) 
pwr=SAVE (0mA)
ugen1.1: <Intel EHCI root HUB> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=SAVE (0mA)
ugen0.2: <SunplusIT Inc HD WebCam> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=ON (500mA)
ugen1.2: <vendor 0x8087 product 0x8000> at usbus1, cfg=0 md=HOST spd=HIGH 
(480Mbps) pwr=SAVE (0mA)
ugen0.3: <vendor 0x0489 product 0xe056> at usbus0, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON (100mA)

The later vendor 0x0489 product 0xe056 seems to be:

https://cateee.net/lkddb/web-lkddb/BT_ATH3K.html

...
Numeric ID (from LKDDb) and names (from usb.ids) of recognized devices:

    vendor: 03f0 ("HP, Inc"), product: 311d ("Atheros AR9285 Malbec Bluetooth 
Adapter")
    vendor: 0489 ("Foxconn / Hon Hai"), product: e027
    vendor: 0489 ("Foxconn / Hon Hai"), product: e02c ("Atheros AR5BBU12 
Bluetooth Device")
    vendor: 0489 ("Foxconn / Hon Hai"), product: e036
    vendor: 0489 ("Foxconn / Hon Hai"), product: e03c
    vendor: 0489 ("Foxconn / Hon Hai"), product: e03d
    vendor: 0489 ("Foxconn / Hon Hai"), product: e04d ("Atheros AR3012 
Bluetooth")
    vendor: 0489 ("Foxconn / Hon Hai"), product: e04e
    vendor: 0489 ("Foxconn / Hon Hai"), product: e056
    vendor: 0489 ("Foxconn / Hon Hai"), product: e057
    ...

-- 
Matthias Apitz, ✉ [email protected], http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "[email protected]"

Reply via email to