From owner-freebsd-wireless@freebsd.org Mon Apr 15 12:30:14 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BC671572847 for ; Mon, 15 Apr 2019 12:30:14 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF378771E1; Mon, 15 Apr 2019 12:30:13 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id CFEA15E0A; Mon, 15 Apr 2019 12:30:13 +0000 (UTC) Date: Mon, 15 Apr 2019 12:30:13 +0000 From: Alexey Dokuchaev To: Adrian Chadd Cc: "freebsd-wireless@freebsd.org" , Hans Petter Selasky Subject: Re: Atheros AR5B22 WLAN+Bluetooth support on FreeBSD Message-ID: <20190415123013.GB22516@FreeBSD.org> References: <20190411125242.GA64046@FreeBSD.org> <20190411131328.GA4909@c720-r342378> <20190411131859.GA17806@FreeBSD.org> <20190411142350.GA71446@FreeBSD.org> <20190412171218.GA16463@FreeBSD.org> <20190413142006.GA59512@FreeBSD.org> <20190413191419.GB13742@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: DF378771E1 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.89 / 15.00]; TAGGED_RCPT(0.00)[]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_SHORT(-0.90)[-0.896,0]; NEURAL_HAM_MEDIUM(-0.99)[-0.990,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US]; NEURAL_HAM_LONG(-1.00)[-0.999,0] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Apr 2019 12:30:14 -0000 On Sat, Apr 13, 2019 at 12:35:30PM -0700, Adrian Chadd wrote: > On Sat, 13 Apr 2019 at 12:14, Alexey Dokuchaev wrote: > > ... > > 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." I understand, and it makes sense to give hints to the scheduler from the kernel side, but less so when calling uslee() from userland. > Just pick a value in between. :-) Oh well, maybe that'll do. ./danfe