Partager via


BSP Catalog Data

The following table shows the Catalog fields for each board support package (BSP). The Driver Updater uses these fields to determine the best driver to add to your platform.

Catalog field Use Description
DefaultDrivers Strongly recommended. An implementation GUID for each type of driver that a BSP supports.
BSPPlatformDir Required. The BSP platform directory where the BSP source is located. Platform Builder uses this information to determine where to build the BSP.
CPUSizeMultiplier Optional.
Default = 1.0.
The size multiplier associated with a specific BSP.

Platform Builder estimates how large the OS image is based on the features selected. Many of these items are BSP-dependent, with the actual size depending on the compiler/linker for that BSP. The default for this field is 1.0, based on the size of the same feature in a retail build of a CEPC platform.

If the image size for your BSP is smaller or larger than that of a CEPC with identical features, you can specify a floating-point multiplier for Platform Builder to use in its size calculations.

If the size of the OS image tends to run 10 percent larger for your BSP, the CPUSizeMultipler value should be set to 1.10.

<BSP-specific size field> Optional.
Default = 0.
This tells Platform Builder approximately how many bytes this BSP takes in the final image.

See Also

Device Driver and BSP Updater

Last updated on Wednesday, April 13, 2005

© 2005 Microsoft Corporation. All rights reserved.