Fri, 04 Mar 2016 18:18:22 +0200 було написано Jonathan Anderson
<jonat...@freebsd.org>:
On 4 Mar 2016, at 0:47, Adrian Chadd wrote:
It's a known problem. Someone has to fix the firmware api use. It's just
wrong.
Ok, thanks.
May be workaroundable with https://reviews.freebsd.org/D4236 (restarts the
device
automatically after each failure; but the problem is still here)
Jon
--
Jonathan Anderson
jonat...@freebsd.org
_______________________________________________
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to
"freebsd-wireless-unsubscr...@freebsd.org"
_______________________________________________
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
