Date: Wed, 10 Feb 2010 20:01:28 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Hans Petter Selasky <hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: usb_interrupt_read blocks "forever" sometimes Message-ID: <201002102001.37306.doconnor@gsoft.com.au> In-Reply-To: <201002100923.20377.hselasky@c2i.net> References: <201002101738.30753.doconnor@gsoft.com.au> <201002100923.20377.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart4506954.qxt5DIKHBA Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 10 Feb 2010, Hans Petter Selasky wrote: > I would not recommend using signals with libusb. It is not portable. > Currently signals are ignored. What you would have to do, is to use OK. > the timeout argument which you are doing, and have a timekeeper > variable somewhere, or create another thread. Still, when using the > timeout there is a chance you can loose data. The problem is that the timeout seems to be ignored sometimes - that is=20 the only reason I was playing with alarm() at all. I have the timeout set to 100 (milliseconds?) yet I find if I restart=20 the program every now and then it will get stuck on the first read. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart4506954.qxt5DIKHBA Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBLcnz55ZPcIHs/zowRAi7HAJ9cWCUiD9XsV9jruMxqTir8Z9+OBgCfe/up vcT/PskCJD/Hl6abDjet1Ng= =6olO -----END PGP SIGNATURE----- --nextPart4506954.qxt5DIKHBA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201002102001.37306.doconnor>