Windows 10 Driver Publishing Workflow
Driver Targeting Background
Yüklə 159,22 Kb.
|
- Bu səhifədəki naviqasiya:
- Computer Hardware IDs
- Tips for consistent CHIDs
Driver Targeting
Driver targeting ensures the correct driver is installed on the correct hardware. Traditionally, this is done by a four-part HWID differentiation when needed on buses that support such targeting. Partners submit these drivers to the Windows Hardware DevCenter Dashboard for distribution. However, sometimes the four-part HWIDs are not specific enough. For example:
Generic HWIDs are used for a variety of reasons. Constraining the systems to which a driver is distributed mitigates the issues highlighted above. With Windows 10 computer hardware IDs (CHIDs) can be used to better target drivers to specific systems.
Computer Hardware IDs (CHIDs) are defined in the Specifying Hardware IDs for a Computer article on MSDN: http://msdn.microsoft.com/en-us/library/windows/hardware/ff552325(v=vs.85).aspx For Windows 10, several new CHIDs have been added that incorporate Baseboard Manufacturer and Baseboard Product information. They have been included into the CHID hierarchy as illustrated in Table 3Error: Reference source not found. The table shows the hierarchy in descending order of specificity. The CHIDs that are new to Windows 10 are highlighted in bold. Table : CHID Definitions
OEMs will need to provide the correct CHID information to the driver publisher. The ComputerHardwareIds.exe tool (http://msdn.microsoft.com/en-us/library/windows/hardware/ff543505(v=vs.85).aspx), included in the Windows Desktop Tools SDK, can help facilitate reporting CHIDs from a known set of System Management BIOS (SMBIOS) values. Note that the ComputerHardwareIds.exe tool performs two different tasks:
By default the tool will display the system’s current SMBIOS values, which will be used to generate the various CHIDs. It also displays the CHIDs that are generated. You can use this default behavior of the tool to determine the CHIDs for any given system by running the tool on it.
You can simulate which CHIDs will be generated by Windows by running the tool with passing in various SMBIOS values, such as manufacturer, family, SKU, and so on. The tool will use those inputted values to generate CHIDs representing the inputted data. This is useful if you want to determine which CHIDs would be generated on a system with specific SMBIOS data values.
Note that CHIDs are generated based on case sensitive SMBIOS values. Therefore care must be taken to ensure that systems do not mix cases in SMBIOS text values. Similarly UNICODE characters are not specially treated. Therefore upper and lower case versions of special characters, such as the Turkish dotted and un-dotted letter I, are treated uniquely: I, ı, İ and i are not the same. Note that the tool will only compute CHIDs for which there is data available. If an SMBIOS data field is missing (or it is null), then any related CHIDs are not generated. For example if the SMBIOS SKU field is null then CHIDs 0, 3, 4 6 and 7 (from Table Error: Reference source not found) will not be available for that particular system.
|