Ooooooooh wait this is something recentish? Which wifi chipset is this attached to?
I vaguely remember upstream Linux ath3k having a similar issue super recently..... A On Fri, Mar 27, 2020, 11:14 AM <jason-fbsd-blueto...@shalott.net> wrote: > > > Ok so the device ID via USB changes when you've loaded firmware, and > > ng_ubt should attach to it. > > Yes, the device ID does change; no, ng_ubt does not attach to the changed, > correct device ID. > > When the device is plugged, it gets: > ugen1.4: <vendor 0x0cf3 product 0x3000> at usbus1 > > After loading firmware, it becomes: > ugen1.4: <vendor 0x0cf3 product 0x3002> at usbus1 > > Your change, below, instructed ng_ubt to not attach to this device: > > https://svnweb.freebsd.org/base?view=revision&revision=249178 > > static const STRUCT_USB_HOST_ID ubt_ignore_devs[] = { > /* ... */ > { USB_VPI(0x0cf3, 0x3002, 0) }, > > > Please see my full original email: > > https://lists.freebsd.org/pipermail/freebsd-bluetooth/2020-March/002129.html > > And the followup: > > https://lists.freebsd.org/pipermail/freebsd-bluetooth/2020-March/002133.html > > Thanks. > > > -Jason > > _______________________________________________ freebsd-bluetooth@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "freebsd-bluetooth-unsubscr...@freebsd.org"
