search for: ff547089

....e. > > {amd64,i386}/Win{XP,2003,2008,2008R2,2012,2012R2,7,8,8.1} > > or switch to the names passed to inf2cat in its /os parameter, i.e. > > XP_X86,Server2003_X86,...,8_X64,Server8_X64,6_3_X86,6_3_X64,Server6_3_X64 > (https://msdn.microsoft.com/en-us/library/windows/hardware/ff547089(v=vs.85).aspx) > > Whatever convention is chosen it needs to be followed thereafter. Yup - very important that once we decide what the naming convention is going to be, we stick with it. Moving drivers around or using ad-hoc naming schemes causes churn in virt-v2v and probably other projec...

On Wed, Nov 18, 2015 at 11:31:17PM -0500, Li Jin wrote: > > > > In any case the *.inf files don't seem to have any distinguishing > > > > feature which would allow us to check this. > > > > > > > > Maybe this doesn't matter? > > > > > > Let me explain how it works: > > > We don't make any difference between

...ing used in that virtio-win rpm, i.e. {amd64,i386}/Win{XP,2003,2008,2008R2,2012,2012R2,7,8,8.1} or switch to the names passed to inf2cat in its /os parameter, i.e. XP_X86,Server2003_X86,...,8_X64,Server8_X64,6_3_X86,6_3_X64,Server6_3_X64 (https://msdn.microsoft.com/en-us/library/windows/hardware/ff547089(v=vs.85).aspx) Whatever convention is chosen it needs to be followed thereafter. The main problem with this proposal is that I don't know how to implement it: there are multiple vendors of virtio-win packages, and, for licensing reasons, they don't even share the source code, so it's...

...6}/Win{XP,2003,2008,2008R2,2012,2012R2,7,8,8.1} > > > > or switch to the names passed to inf2cat in its /os parameter, i.e. > > > > XP_X86,Server2003_X86,...,8_X64,Server8_X64,6_3_X86,6_3_X64,Server6_3_X64 > > (https://msdn.microsoft.com/en-us/library/windows/hardware/ff547089(v=vs.85).aspx) > > > > Whatever convention is chosen it needs to be followed thereafter. > > Yup - very important that once we decide what the naming convention is > going to be, we stick with it. Moving drivers around or using ad-hoc > naming schemes causes churn in virt...

...,2008R2,2012,2012R2,7,8,8.1} >> > >> > or switch to the names passed to inf2cat in its /os parameter, i.e. >> > >> > XP_X86,Server2003_X86,...,8_X64,Server8_X64,6_3_X86,6_3_X64,Server6_3_X64 >> > (https://msdn.microsoft.com/en-us/library/windows/hardware/ff547089(v=vs.85).aspx) >> > >> > Whatever convention is chosen it needs to be followed thereafter. >> >> Yup - very important that once we decide what the naming convention is >> going to be, we stick with it. Moving drivers around or using ad-hoc >> naming scheme...