Dynamic BIOS Interface File Selection for System Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Computer systems often come with static MOF files that may not support all configurations, leading to unnecessary inclusion of device support for non-existent hardware, such as temperature sensors or security credentials, due to the inability to edit or replace MOF files after compilation.
Innovation Solution
A plurality of interface files are stored in non-volatile storage, allowing the processor to determine the system configuration and select an appropriate pre-compiled or uncompiled interface file for use by the operating system to access the BIOS, enabling dynamic support for specific hardware configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a static MOF file is used to provide BIOS access, then the interface file is simple and easy to manufacture, but it cannot adapt to different system configurations and includes unnecessary device support
Solution Approach 1:
The patent divides a single static MOF file into multiple segmented interface files, each tailored to specific system configurations. The system is divided into configuration categories (e.g., with temperature sensors, without temperature sensors, with security credentials, without security credentials), and each category has its own interface file. This segmentation allows the system to select the appropriate interface file based on the actual hardware configuration, eliminating unnecessary device support while maintaining adaptability.
2Quantity of substance
If a single MOF file supports all configurations, then it provides universal compatibility, but it includes unnecessary support for non-existent hardware increasing file size and complexity
Solution Approach 1:
The patent extracts and removes unnecessary device support from the interface file. Instead of including all possible device support in a single comprehensive MOF file, the system extracts only the relevant device support needed for each specific configuration. For example, if a system does not have temperature sensors, the interface file for that system will not include temperature sensor support code, thereby reducing file size while maintaining configuration-specific adaptability.
3Ease of operation
If the MOF file is compiled before system assembly, then it is ready for use, but it cannot be edited or replaced to match actual system configuration
Solution Approach 1:
The patent applies preliminary action by pre-compiling multiple interface files for different system configurations before system assembly. Each interface file is pre-compiled and optimized for a specific configuration scenario. During system assembly, the actual hardware configuration is determined, and the corresponding pre-compiled interface file is selected and used. This eliminates the need for post-assembly editing or replacement of the MOF file, as the appropriate file is already compiled and ready for use.
Data Source
AI summary
A computer may comprise a processor and first storage device coupled to the processor. The first storage device contains a basic input/output system (BIOS) executable by the processor. The system may also comprise a second storage device coupled to the processor. The second storage device may contain a management interface usable by an operating system to access the BIOS. A plurality of interface files may also be provided, each interface file being usable by the management interface to access the BIOS and each interface file defining one or methods for use by the interface or BIOS. Upon execution of the BIOS, the processor is to determine a configuration of the system and, based on the determined configuration, to select a particular interface file for use during run-time.