System and Method to Abstract Hardware Routing via a Correlatable Identifier

• US 20120180076A1
• Filed: 01/10/2011
• Published: 07/12/2012
• Est. Priority Date: 01/10/2011
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Shutt, Mark W., Joshi, Anand P., Bolen, Austin, Boyd, Patrick O., El Haj Mahmoud, Samer, Edwards, William C. III
• Granted Patent: US 8,819,708 B2
• Time in Patent Office: Days
• US Class Current: 719/327
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers

Abstract

An information handling system includes a firmware management infrastructure. The firmware management infrastructure includes a database that identifies a correspondence between members of a set of device paths and members of a set of correlatable identifier strings. A device path represents a platform-specific reference to an object at the information handling system and a correlatable identifier string represents a platform independent reference to the object. Programs can access the database using an application programming interface.

Claims

1. A computer implemented method comprising:

receiving a first Unified Extensible Firmware Interface (UEFI) device path at a UEFI driver, the UEFI driver including a table identifying a mapping between each respective member of a set of UEFI device paths and a corresponding member of a set of correlatable identifier strings;

determining that the first UEFI device path is included in the set of UEFI device paths; and

providing a first correlatable identifier string in response to the determining.

2. The method of claim 1 further comprising providing a displayable text string corresponding to the first UEFI device path and to the first correlatable identifier in response to the determining.

3. The method of claim 1 wherein the correlatable identifier string is a fully qualified device descriptor.

4. The method of claim 1 wherein the correlatable identifier string provides a reference to an object at an information handling system, the reference being platform-independent.

5. The method of claim 1 wherein receiving the first UEFI device path comprises receiving the first UEFI device path at an application programming interface (API), the API accessible by another UEFI driver.

6. The method of claim 1 wherein receiving the first UEFI device path comprises receiving the first UEFI device path at an application programming interface (API), the API accessible by a UEFI application.

7. The method of claim 1 wherein the UEFI driver is a UEFI boot services driver.

8. The method of claim 1 wherein the UEFI driver is a UEFI runtime services driver.

9. The method of claim 1 wherein the UEFI device path defines a logical location of an object at an information handling system, the UEFI device path being platform specific.

10. A computer implemented method comprising:

receiving a first correlatable identifier string at a Unified Extensible Firmware Interface (UEFI) driver, the UEFI driver including a table identifying a mapping between each respective member of a set of device paths and a corresponding member of a set of correlatable identifiers strings;

determining that the first correlatable identifier string is included in the set of correlatable identifier strings; and

providing a first correlatable identifier in response to the determining.

11. The method of claim 10 further comprising providing a displayable text string corresponding to the first device path and to the first correlatable identifier string in response to the determining.

12. The method of claim 10 wherein the correlatable identifier string is a fully qualified device descriptor.

13. The method of claim 10 wherein the correlatable identifier string provides a reference to an object at an information handling system, the reference being platform-independent, and wherein the UEFI device path defines a logical location of an object at an information handling system, the UEFI device path being platform specific.

14. The method of claim 10 wherein receiving the first correlatable identifier string comprises receiving the correlatable identifier string at an application programming interface (API), the API accessible by a UEFI driver or a UEFI application.

15. An information handling system comprising:

a firmware management infrastructure including a database, the database identifying a correspondence between a first device path of a set of device paths and a first correlatable identifier string of a set of correlatable identifier strings, wherein the first device path represents a platform-specific reference to an object at the information handling system and the first correlatable identifier string represents a platform independent reference to the object; and

an application programming interface (API) to support access to the database by a first program.

16. The system of claim 15 wherein the database further identifies a correspondence between a first displayable text string of a set of displayable text strings and the first device path.

17. The system of claim 15 wherein the firmware management infrastructure comprises a Unified Extensible Firmware Interface.

18. The system of claim 15 wherein the first correlatable identifier string is a fully qualified device descriptor.

19. The system of claim 15 wherein the database and the API are provided by a Unified Extensible Firmware Interface (UEFI) driver or by a UEFI application.

20. The system of claim 15 wherein the first device path is a Unified Extensible Firmware Interface device path.