> I've been getting similar reports from users of the ov511 driver: error > -84 (babble), error -110 (timeout), and truncated frames. The common > variable in all cases is a VIA chipset. I would try to track the problem > down, but my host controllers are all either OHCI or Intel UHCI.
I as well have noticed the only chipsets I have problems with are the VIA uhci chipsets. As I said previously, I know a "special" UHCI driver was released by Microsoft/VIA that corrected a lot of problems that were being had with VIA's chipset. I would persue a fix for it myself, but I don't know enough about the host controller code to be able to talk one-to-one to a VIA representative. If the maintainer of one of the *uhci.c drivers were to look into it, I think it definitely be worth doing. > ><We're definitely looking at some low-level USB problems here. The device > ><isn't even enumerating properly -- without that, nothing (and I mean > ><_nothing_) will work. > > > >matt suggested i try the other uhci driver (uhci, in my system), which i did. > >this works. just plain works. so do all other usb devices, apparently. > > > > In most of the reports, uhci only caused these errors when streaming > video from the camera. usb-uhci usually wouldn't enumerate the device at > all. So, I think both drivers have this "bug", but are affected by it to > varying degrees. > > There must be errata for VIA uhci controllers that aren't known outside > of VIA and Microsoft. Perhaps someone more influential than I (and more > versed in UHCI internals) could contact VIA and get the necessary info. I would think so; I haven't seen any fixes in the linux stuff yet. Maybe I'll see about doing some poking around on the net for the issue. Matthew Fredrickson _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
