On Sat, 13 Apr 2019 at 12:14, Alexey Dokuchaev <[email protected]> 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 tell me how to implement Linuxish usleep_range() correctly in our > userland, I can do that. :-) > usleep_range() is just the same as usleep() at either min, max or a value in between. It's just a hint to the scheduler that says "look, don't sleep exactly for this amount of time to wake me up; here are my bounds that are fine so if you schedule something else before then don't forget about me." Just pick a value in between. :-) > > > Maybe we need to loop in hps@ with a bunch of usbdump output to see what > > the transactions look like... > > CC'ed (sorry for the lack of context hps@, but it's hard with Adrian's > top-post replies). Please see the archives for the gory details. > Sorry, life is busy nowdays - I was making breakfast and keeping two kids from eating things they shouldn't. Top posting is quick. :) -a _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "[email protected]"
