On Mon, Dec 10, 2001 at 08:27:30PM +0000, Steven Toth wrote: > Question 1. I'm submitting the ISO tranfer URBs which are all coming back > (via completion handler) with the correct number of packets - but they are > all empty. No errors, status is fine, frame count is increasing as expected > ... just no data. What's the best way to prove 100% that they're coming from > the webcam? I'll happily patch the kernel to output extra diagnostics if > necessary... Any suggestions?
Fill the memory with another pattern (eg. 0xaa or such). If it is changed, it definitely came from the device. Another hint would be the length of each frame. > Question 2. Before the URB is passed to the completion handler, the urb->dev > field is being nullified. What's the rational behind this? It causes There's a potential race how to distinguish when an URB is definitely finished by the HCD. The nulled ->dev prohibits immediate resubmission for example. > dabusb.c to oops when calling "unsigned int pipe = usb_rcvisocpipe > (purb->dev, _DABUSB_ISOPIPE);" Anyone else noticed this? Look like the > driver in 2.4.16 is broke an no one noticed. The dabusb-driver wasn't updated for a long time, since the device also wasn't (commercially) available (at that time...). Since Terratec now starts to sell the DR-Box-1 (their name of the receiver), it will get an update soon. The current dabusb.c can be found in our CVS at http://usb.cs.tum.edu/ > Question 3. SniffUSB starts the logfile with the output below, am I correct > in assuming that this is the same as... > > usb_set_configuration (usbdev, usbdev->config[0].bConfigurationValue) > and > usb_set_interface (s->usbdev, 0, 6); I'm not familiar with SniffUSB... -- Georg Acher, [EMAIL PROTECTED] http://www.in.tum.de/~acher/ "Oh no, not again !" The bowl of petunias _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
