Ok, so it's because in theory the firmware could be buggy and need
patching via the ath3kfw tool (which gosh I really should just import
into -head already) before it starts up.
can you clone https://github.com/erikarn/ath3k and try to load in what
it thinks the right patch set / config fil
Hi!
Ok so the device ID via USB changes when you've loaded firmware, and
ng_ubt should attach to it.
-adrian
___
freebsd-bluetooth@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "
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: at usbus1
After loading firmware, it become
Ooooh 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 wrote:
>
> > Ok so the device ID via USB changes when you've loaded firmware, and
> > ng_ubt
