On Fri, Jul 30, 2010 at 03:01:50PM -0700, David Brownell wrote: > > > > That's too extreme; the original handful of > > > NetChip IDs were (and are!!) correctly assigned, > > > and there's no reason to change them. In fact, > > > there's a lot of reason to continue using them > > > while config files and drivers expect to see > > > those specific IDs (as is reasonable). That's > > > to avoid breaking working configs... > > > > True, I was thinking that for the class-type devices, we > > could use the > > linux foundation vid, as changing them shouldn't > > matter right? > > There are INF files using NetChip IDs, so > changing them would break stuff. > > Newer interfaces using new VIDS/PIDS? Fine. > > > > Or does Windows really care about the vid/pid for > > a class device somehow? > > My understanding is that it does, since it really > doesn't have a good concept of "class" being the > generic thing. INF files embed VIDS/PIDS even > for drivers implementing class specs. MSFT was > being stupid again... Ok, fair enough. thanks, greg k-h -- 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
