Re: [XENBUS PATCH v3 2/9] Merge all hardware IDs into one Models entry

[Owen Smith <owen.smith@xxxxxxxxx>]

The XenVbd changes seem fine, but there is a problem if older xenvbd is loaded on this xenbus, where the devices do not cope with a change in the device_id or presence of the vendor device. To work around this, I had to set xenbus's PDOs DeviceID to exclude the PCI vendor ID (e.g. "XENBUS\VEN_XP&DEV_VBD")

Owen

On Wed, Aug 6, 2025 at 8:56 AM Owen Smith <owen.smith@xxxxxxxxx> wrote:

On Mon, Aug 4, 2025 at 4:35 PM Tu Dinh <ngoc-tu.dinh@xxxxxxxxxx> wrote:

 [Inst.NT@INF_ARCH@]
-; DisplayName          Section         DeviceID
-; -----------          -------         --------
-
-%XenBusName_VEND%      =XenBus_Inst,   PCI\VEN_5853&DEV_@VENDOR_DEVICE_ID@&SUBSYS_@VENDOR_DEVICE_ID@5853&REV_01
-%XenBusName_0002%      =XenBus_Inst,   PCI\VEN_5853&DEV_0002
-%XenBusName_0001%      =XenBus_Inst,   PCI\VEN_5853&DEV_0001
+%XenBusName%=XenBus_Inst,\

Comma should be on the vendor device ID line, so if VENDOR_DEVICE_ID is not defined, then the INF section is still valid, although it 'promotes' 0002 to HWID from CompatID

 

+PCI\VEN_5853&DEV_@VENDOR_DEVICE_ID@&SUBSYS_@VENDOR_DEVICE_ID@5853&REV_01\
+,PCI\VEN_5853&DEV_0002\
+,PCI\VEN_5853&DEV_0001

 [XenBus_Inst]
 CopyFiles=XenBus_CopyFiles
 CopyFiles=Monitor_CopyFiles
+FeatureScore=0xFE

The main potential issue here is determining if Microsoft / Windows Update will allow an update distribution to the vendor device ID without distributing for the compatible IDs, so drivers will only install via Windows Update on the vendor device, not on others - if this is not possible, then an alternate method is needed. I've so far not been able to confirm this either way, but it would appear that driver distributions are enabled for a specific HWID.

Owen