Abstract: Firmware interfaces scale a fixed-font utilized by the firmware interfaces to display glyphs of the fixed-font at a native resolution or a preferred resolution of a display. A conversion factor is generated for scaling the glyphs of the font using the native resolution or the preferred resolution. The glyphs may be scaled using the conversion factor. The scaled glyphs may be stored and utilized to display text of the firmware interface in the native resolution or the preferred resolution.

Abstract: Technologies are described herein for obtaining platform-specific information in a firmware execution environment. A platform-to-driver configuration protocol executes within the firmware execution environment. The platform-to-driver configuration protocol receives a request for platform-specific information from a firmware driver that is also executing in conjunction with the firmware execution environment. The platform-to-driver configuration protocol discovers one or more platform-to-driver agents also executing in the firmware execution environment. The platform-to-driver configuration protocol then queries at least a portion of the platform-to-driver agents to identify one of the platform-to-driver agents as a provider of the requested platform-specific information. A communications session can then be established between the requesting firmware driver and the platform-to-driver agent identified as the provider of the requested platform-specific information.

Abstract: Firmware interfaces scale a fixed-font utilized by the firmware interfaces to display glyphs of the fixed-font at a native resolution or a preferred resolution of a display. A conversion factor is generated for scaling the glyphs of the font using the native resolution or the preferred resolution. The glyphs may be scaled using the conversion factor. The scaled glyphs may be stored and utilized to display text of the firmware interface in the native resolution or the preferred resolution.

Abstract: Technologies are described herein for controlling the selection of drivers in a firmware environment for managing a hardware device based on a user preference. A user preference that specifies one driver being preferred over another driver for the hardware device is received, for example, through a user interface provided by the firmware environment. According to the user preference, a sorted driver pool that contain drivers available for the hardware device is created by listing the preferred driver before the non-preferred driver in the sorted driver pool. A driver stack is then built from the sorted driver pool by examining each driver in the sorted driver pool in the order they are listed in the sorted driver pool. The preferred driver is then put into the driver stack before the non-preferred driver and thus is associated with the hardware device first.