On Fri, 10 Sep 2010, Greg KH wrote: > > > There are tools that parse this value, so we can't make it a string :( > > > > Do these tools assume particular field widths? If they do, how will > > they cope with a 4-digit SuperSpeed entry? > > I looked at usbview, and it can handle if the field gets bigger. I > think that's the only tool that parses this file. > > Actually, usbview is pretty "dead" these days, and I can easily change > it to handle this modification. Still, we shouldn't break the existing versions of usbview. > vmware used to have some logic that worried about this file, but I don't > think it relies on it anymore, but I could be wrong. It might be nice > to test a windows vmware instance on a Linux host with this change. Hmm. Not only do I not have VMWare installed, I also don't have any wireless or USB-3.0 hardware to provoke the new Speed values with. Sarah, is there anybody at Intel who can test this? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
