On Mon, Jun 14, 2010 at 4:43 PM, Michal Nazarewicz <m.nazarewicz@xxxxxxxxxxx> wrote: > Updated the INF file for the g_ether gadget. It should work with most > recent Windows systems now. The file has been also renamed to > linux-rndis.inf rather then linux.inf. > > Signed-off-by: Michal Nazarewicz <m.nazarewicz@xxxxxxxxxxx> > Signed-off-by: Kyungmin Park <kyungmin.park@xxxxxxxxxxx> > --- > On Wed, 09 Jun 2010 17:33:51 +0200, Greg KH <greg@xxxxxxxxx> wrote: >> How about putting the following on the file: >> ; based on a example .inf file that was: >> ; Copyright (c) Microsoft Corporation >> ; and released under the MLPL as found at >> ; http://msdn.microsoft.com/en-us/cc300389.aspx#MLPL >> ; For use only on Windows operating systems. >> ; > > As requested only with a little bit different wording. > > Still, I am not sure what to do with the serial INF. > I cannot even find the original file Xiaofan posted > not mentioning any associated license. I mean, I would > leave it as is without changes but dunno... I think all the INF file templates ultimately comes from DDK/WDK. For example, the RNDIS template is from here. And the title says WDK. http://msdn.microsoft.com/en-us/library/ff570620%28VS.85%29.aspx For the CDC-ACM INF, the original template may well be from an ancient DDK. Anyway, here are some places to infer the CDC-ACM INF file. http://support.microsoft.com/kb/837637/en-us (important for Vista/Win7) http://msdn.microsoft.com/en-us/library/ff542605%28VS.85%29.aspx (same as above). http://msdn.microsoft.com/en-us/library/ff543241.aspx (for 2000/XP) http://msdn.microsoft.com/en-us/library/ff542491%28v=VS.85%29.aspx http://msdn.microsoft.com/en-us/library/ff542559.aspx Worse come worse, you might contact Microsoft about the license. The Microsoft Driver News group has a lot of experts including Microsoft employees who are very helpful. microsoft.public.development.device.drivers -- Xiaofan http://mcuee.blogspot.com -- 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
