Date: Sat, 9 Apr 2005 17:05:31 -0400 From: David Gilbert <dgilbert@dclg.ca> To: ticso@cicely.de Cc: David Gilbert <dgilbert@dclg.ca> Subject: Re: Tricky USB device. Message-ID: <16984.17307.804041.502108@canoe.dclg.ca> In-Reply-To: <20050408233301.GW96690@cicely12.cicely.de> References: <16982.46075.115518.130213@canoe.dclg.ca> <4256B5EB.9080506@savvis.net> <16982.47024.135663.645297@canoe.dclg.ca> <20050408190514.GS96690@cicely12.cicely.de> <16983.465.572693.73195@canoe.dclg.ca> <20050408233301.GW96690@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Bernd" == Bernd Walter <ticso@cicely12.cicely.de> writes: Bernd> Yes - you must use 1 - there is only one out-endpoint. 0x81 is Bernd> for receiving data and endpoint 0 is the mandandory control Bernd> endpoint. Interrupt Endpoints are not variable in size. Both Bernd> interrupt endpoints are 8 Bytes, so you must read and write Bernd> exact 8 Bytes per transfer - 5 shouldn't work for USB compliant Bernd> devices. I took your earlier advice and just opened ugen0.1 O_RDWR. I've tried sending 5 and 8 byte strings to it without effect. To make the 8 byte strings, I added spaces to the end of my 5 byte strings. I've also got a proper multitester now to verify operation. Bernd> Depends on the device's firmware. I wouldn't be surprised if Bernd> the whole device just hangs after receiving bogus data - it Bernd> seems to be broken in many points. But it may block if the Bernd> device has nothing to send. An easy way to check out is using Bernd> tools like usbdevs -v and see if it hangs when accessing this Bernd> device. usbdevs -v and udesc_dump both operate fine after trying this. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16984.17307.804041.502108>