Configurable Option ROM Dispatch Policy Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing firmware systems lack flexibility in managing multi-image option ROMs, requiring manual source code modifications and lengthy development times for configuring device initialization policies during boot processes, especially when transitioning between legacy and UEFI compliant systems.

Innovation Solution

Implementing a configurable option ROM dispatch policy system that allows users to dynamically select and modify which ROM image to execute during boot through a user interface, reducing the need for source code modifications and enabling auto-generation of setup pages for managing these policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If firmware code is used to implement option ROM dispatch policy, then the system can execute only one option ROM per device during boot, but the policy cannot be modified once the firmware image is created

Engineering Contradiction:
Improveboot process stabilityVSAvoidpolicy configurability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The firmware is segmented into a base firmware image and a separate configurable policy table. The policy table stores dispatch policies for different device types and can be modified independently of the firmware image, allowing policy changes without regenerating the entire firmware. This segmentation resolves the contradiction by separating the immutable boot execution logic from the configurable policy settings.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A policy table acts as an intermediary between the firmware execution logic and the configuration settings. The table mediates between the fixed firmware image and the need for configurable policies by storing policy data that can be read and modified during system operation, enabling adaptability without changing the core firmware code.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If source code modifications are made to configure option ROM dispatch policies, then the desired boot behavior can be achieved, but development and testing time increases significantly

Engineering Contradiction:
Improvepolicy configuration easeVSAvoiddevelopment and testing time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

Instead of modifying source code, the system uses a configurable policy table that copies the desired boot behavior through data configuration rather than code changes. This allows developers to configure dispatch policies by modifying data structures rather than writing new code, dramatically reducing development and testing time while maintaining the same functional outcome.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If firmware image is regenerated to apply policy changes, then the new policies can be executed, but the process becomes complex and time-consuming

Engineering Contradiction:
Improvesystem configuration flexibilityVSAvoidfirmware update process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The firmware system is segmented into a stable base image and a modifiable policy table. This segmentation allows policy changes to be applied by modifying only the policy table data rather than regenerating the entire firmware image, reducing complexity and time requirements for configuration updates while maintaining system adaptability.

Inventive Principle:
Principle #1Segmentation

4Ease of operation

If manual configuration of option ROM policies is performed, then specific device initialization tasks can be controlled, but the process is error-prone and time-consuming

Engineering Contradiction:
Improveconfiguration precisionVSAvoidconfiguration time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system provides pre-defined policy templates and data structures that can be copied and configured rather than building from scratch. Developers can select and modify existing policy configurations, reducing both the time required and errors associated with manual configuration while maintaining precise control over device initialization tasks.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10768942B1Option ROM dispatch policy configuration interface
Publication Date: 2020.09.08 AMERICAN MEGATRENDS
  • US10768942B1 patent drawing
  • US10768942B1 patent drawing
  • US10768942B1 patent drawing

AI summary

A computer-implemented method renders user interfaces for devices with multi-image option ROMs according to option ROM dispatch policies associated with the devices. The option ROM dispatch policies can specify whether the multi-image option ROM for the device is enabled or disabled. The option ROM dispatch policies can also specify the image of the multi-image option ROM to execute during boot. The multi-image ROM can include a UEFI compliant image and a legacy BIOS image. The computer-implemented method may receive user selections modifying the option ROM dispatch policies via the rendered user interfaces.