> I think "OP" is you. Since this is your circuit, it would be hard to have > prior > reports. Oh, i see. Thought you are talking about somebody else :-). > OWFS certainly doesn't know or care about hubs -- it just uses libusb to > enumerate USB devices and libusb for all communication. Yes that's how i expected. And of course the error is not caused by owfs itself.
> I realize your circuit only uses a few mA, but perhaps you are supplying a > larger current to the 1-wire bus (which you are powering) than you realize? Althought the bus is planed with a length of about 50 meters and 20-30 devices there is only one 18S20P for testing at the moment. I have a 100mA Fuse in the 5V supply line of the usb bus. There *can't* be a large current. In the meantime i compiled debuging support in the usb kernel modules. Now the failure looks like this: uhci_hcd 0000:00:11.3: reserve dev 4 ep81-INT, period 1, phase 0, 36 us uhci_hcd 0000:00:11.3: release dev 4 ep81-INT, period 1, phase 0, 36 us uhci_hcd 0000:00:11.3: reserve dev 4 ep81-INT, period 1, phase 0, 36 us uhci_hcd 0000:00:11.3: release dev 4 ep81-INT, period 1, phase 0, 36 us usb 2-1: uhci_result_common: failed with status 500000 usb 2-1: owfs timed out on ep0out len=-8/0 usb 2-1: owfs timed out on ep0out len=-8/0 usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd owfs rqt 64 rq 1 len 0 ret -110 usb 2-1: owfs timed out on ep0out len=-8/0 Perhaps this should be a topic on linux-usb-devel mailinglist? Best wishes, Klaus ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
