Matthias Schniedermeyer wrote: > For the record: > > I just went to my local hardware dealer and bought 5 out of about a > dozen hubs and ended up with 3 different chipsets (each different from > the chipset of the formerly used hub). > > With every 3 of this hubs i just successfully copied 7GB of data with no > errors. > > So i will throw >dozen of the faulty hubs into the box where i collect > my e-waste.
This makes me wonder if we should keep a list somewhere of hardware that have such problems. Problems we can't work around from a code level. For example, my VIA firewire controller has similar problems... and the linux-firewire folks will tell you the VIA firewire controllers suck. I'm thinking the linux-usb site should have "the following hardware has significant problems" with a list of the problems next to each hardware. Thoughts? -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
signature.asc
Description: OpenPGP digital signature
