lramos.procomp wrote: > regarded as a stable code. Furthermore, I don't know if SiLabs disclosed all > information needed to build a reliable driver. As far as I could deduce, the > driver was built based on USB monitorings, and not on the specs, adding some > extra risk.
Yes this is the way it was written (usb monitoring / sniffing). SiLabs did nothing to support it. The closest SiLabe came to linux support was a binary only driver for redhat 9. The working driver in >= 2.6.13 is working well, I am using it on a regular basis. > Plainly: what is the status of the cp2101 driver? If I have to use it, > should I take an extra care of monitoring it in order to identify abnormal > behaviour, etc.? Or, more clearly, should I take it as special? > I have a few production systems running with 2.6.14 and 2.6.15 that have been running OK. They are not using EHCI (usb 2.0) though. USB 2.0 may be ok, but to be safe I disabled EHCI. -- --- Karl Hiramoto <[EMAIL PROTECTED]> http://karl.hiramoto.org/ ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
