From owner-freebsd-hardware Wed Apr 17 23: 4:54 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id C2F7137B41D for ; Wed, 17 Apr 2002 23:04:51 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id QAA14419; Thu, 18 Apr 2002 16:03:55 +1000 Date: Thu, 18 Apr 2002 16:04:31 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Nick Hibma Cc: Peter Haight , Subject: Re: Reading from the USB ugen device. In-Reply-To: <004501c1e612$ede6a4c0$7800420a@vanlaarhoven.org> Message-ID: <20020418160144.T13784-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 17 Apr 2002, Nick Hibma wrote: > > Here the problem may be the more immediate one that usb returns EIO > > instead of EWOULDBLOCK when it can't proceed. > > EIO is only returned in case of error. I was mistaken. EWOULDBLOCK can never > be returned because the ugen driver can't know whether or no the transfer is > going to block. There is no such thing as a poll for data on the USB bus. It seems to sometimes return ETIMEDOUT, which causes the same problem. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message