On Sat, 13 Apr 2019 at 12:14, Alexey Dokuchaev wrote:
> On Sat, Apr 13, 2019 at 11:44:25AM -0700, Adrian Chadd wrote:
> > Hm, is this a problem with our usb3 stack itself?
> >
> > If you send me a pull request against ath3k I'll merge it into my git
> > tree just for completeness.
>
> If you
On Sat, Apr 13, 2019 at 11:44:25AM -0700, Adrian Chadd wrote:
> Hm, is this a problem with our usb3 stack itself?
>
> If you send me a pull request against ath3k I'll merge it into my git
> tree just for completeness.
If you tell me how to implement Linuxish usleep_range() correctly in our
Hi,
There's some work done on the ath(4) hardware for 11a parts done by Sam
Leffler. I fixed it for 11n parts. It's in FreeBSD-HEAD.
I figured out how to get it mostly working on the AR93xx/AR94xx parts too
but it turns out there are some significant hardware changes in how the MAC
schedules
Hm, is this a problem with our usb3 stack itself?
If you send me a pull request against ath3k I'll merge it into my git tree
just for completeness.
Maybe we need to loop in hps@ with a bunch of usbdump output to see what
the transactions look like...
-adrian
On Sat, 13 Apr 2019 at 07:21,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237083
--- Comment #3 from Alexander Sieg ---
Just loading the kernel module will produce the error. And `service bluetooth
start ubt0` will provide the same error.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237083
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org
--- Comment #2
