Skip to content

Commit

Permalink
Update SetupDataPkg/Docs/Profiles/Overview.md
Browse files Browse the repository at this point in the history 
Co-authored-by: Aaron <[email protected]>
  • Loading branch information
@kuqin12 @apop5
kuqin12 and apop5 authored Oct 31, 2023
1 parent d895a39 commit a9da1b7
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion SetupDataPkg/Docs/Profiles/Overview.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,8 @@ following the statements outlined in the [section above](#flow).
Platforms also can provide a 2-character name and/or 1-byte ID for each profile. These are used to identify the profile
by the selector, which could be BMC, OS, or other.

In firmware, the name and ID are provided in the `gProfileFlavorNames` and `gProfileFlavorIds`, respectively. Platforms
In firmware, the name and ID are auto generated and can be accessed through `gProfileFlavorNames` and `gProfileFlavorIds`, respectively. Platforms

can elect to create HOBs for these meta data information and provide them to the selector. See example [here](https://github.com/microsoft/mu_oem_sample/tree/release/202302/OemPkg/OemConfigPolicyCreatorPei).

To integrate the name and ID into the build, platforms can add the following to their build by following the statements:
Expand Down

0 comments on commit a9da1b7

Please sign in to comment.