Skip to content

Almost-duplicate paragraph #3

@langston-barrett

Description

@langston-barrett

Put another way, the GUID forms a contract: If the UEFI Driver finds a protocol
with a particular GUID, it may assume that the contents of the protocol are as
specified for that protocol. If the contents of the protocol are different, the
driver that published the protocol is assumed to be in error.
In some ways, GUIDs are can be viewed as contracts. If a UEFI Driver looks up a
protocol with a certain GUID, the structure under the GUID is well defined. If
the GUID is duplicated, this 1:1 mapping breaks. If a GUID is copied and
applied to a new protocol, the users of the old protocol call the new protocol
expecting the old interfaces or vice versa. Either way, the results are never
good.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions