Date: Wed, 18 May 2016 18:53:05 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Karl Denninger <karl@denninger.net>, freebsd-usb@freebsd.org Subject: Re: Oddity with ugen Message-ID: <c7f9cab2-d0ec-7ca6-c382-1ae1dbd04e63@selasky.org> In-Reply-To: <8dfad53f-e8a6-68b7-37e2-d5cd95768ceb@denninger.net> References: <b24c5a9a-cb18-c014-75ab-9b923853a70c@denninger.net> <46bd6efe-5335-f659-0b07-5107b0e9a326@selasky.org> <af57a994-2e7a-c0d0-1d84-a333c2b2096b@denninger.net> <b04006da-8b3b-7daa-e8d0-0cea8d1583ed@selasky.org> <8dfad53f-e8a6-68b7-37e2-d5cd95768ceb@denninger.net>
index | next in thread | previous in thread | raw e-mail
On 05/18/16 17:53, Karl Denninger wrote: > I'm reasonably sure that the Pi2 itself and the base USB code is ok, > however, because there is another USB device also in use by the same > software (it emulates a serial port and so attaches on the serial > driver; Hi, When you are using /dev/usb/X.Y.Z the IN-endpoints will be polling for data all the time. I've seen devices that return crap data if you try to read from them while you are not supposed to get data, in typical ping-pong protocol scenarios. Using libusb might be a better solution. --HPShome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c7f9cab2-d0ec-7ca6-c382-1ae1dbd04e63>