lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 30 Jul 2010 15:16:20 -0700
From:	Greg KH <greg@...ah.com>
To:	David Brownell <david-b@...bell.net>
Cc:	Michał Nazarewicz <m.nazarewicz@...sung.com>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	Dries Van Puymbroeck <Dries.VanPuymbroeck@...imo.com>,
	Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: [PATCHv5 2/3] USB: gadget: Use new composite features in some
 gadgets

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ