DXVA_COPPStatusHDCPKeyData - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// dxva.h
typedef struct _DXVA_COPPStatusHDCPKeyData {
GUID rApp;
ULONG dwFlags;
ULONG dwHDCPFlags;
GUID BKey;
GUID Reserved1;
GUID Reserved2;
} DXVA_COPPStatusHDCPKeyData;
View the official Windows Driver Kit DDI referenceNo description available.
The DXVA_COPPStatusHDCPKeyData structure describes a High-bandwidth Digital Content Protection (HDCP) receiver or repeater key selection vector (KSV).
rAppSpecifies a 128-bit random number, used once. This random number is generated by the requesting application and supplied to the display driver in the rApp member of the DXVA_COPPStatusInput structure.
dwFlagsSpecifies additional status information that might be relevant to the calling application. The display driver should set dwFlags to the COPP_StatusNormal (0x00) value from the COPP_StatusFlags enumeration type or to a valid ORed combination of the following COPP_StatusFlags:
dwHDCPFlagsSpecifies the current HDCP characteristics of the device connected to a Digital Video Interface (DVI) or High-Definition Multimedia Interface (HDMI) output connector. The display driver can set dwHDCPFlags to COPP_HDCPRepeater (0x01) from the COPP_StatusHDCPFlags enumeration type to indicate that the device is a repeater.
BKeySpecifies the HDCP receiver or repeater KSV (Bksv), as defined by HDCP Specification Revision 1.1, in the least significant 40 bits.
Reserved1Reserved. Should be set to zero (GUID_NULL).
Reserved2Reserved. Should be set to zero (GUID_NULL).
The display driver returns status about the HDCP key through the pOutput parameter of COPPQueryStatus. The DXVA_COPPStatusOutput structure describes the returned status information. The display driver should cast the HDCP key status to a pointer to a DXVA_COPPStatusHDCPKeyData structure and return the status information in the COPPStatus member of DXVA_COPPStatusOutput.
Applications initiate a query for HDCP key data to determine if the receiver or repeater device is revoked; they can then disable protected content flow to the device. Applications must obtain lists of revoked KSVs by processing System Renewability Messages (SRMs). In coordination with Digital Content Protection LLC, owners of HDCP licensing applications should not let protected content flow to HDCP repeaters for COPP version 1.0.
DXVA_COPPSetProtectionLevelCmdData