Skip to content

Conversation

@bobekjan
Copy link
Contributor

Users are encouraged to use this PR as a reference for use-cases where custom display EDID blob is preferred or required for properly functioning display on their platform.

Please note that you will need to replace the EDID blob hard-coded in the source with your own blob; the one included in this PR is taken from the VESA EDID 1.4 Standard and serves reference purposes only.

Expose an instance of EFI_EDID_OVERRIDE_PROTOCOL to force the UEFI
display driver to use a custom EDID binary blob. This is useful
e.g. for use cases where the attached display device is fixed and
known in compile-time, but does not support reading EDID in runtime.

Additionally, include EFI_EDID_OVERRIDE_ENABLE_HOT_PLUG in the
attributes to force the display output to be activated even when the
driver fails to detect any attached display device.

The included EDID binary blob is taken from:

  VESA Enhanced EDID Standard, Release A, Rev.2 (EDID 1.4); Appendix A
  (Sample EDIDs), Example 2.

Signed-off-by: Jan Bobek <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants