Specification Sheet

Host Bridge/DRAM Registers

72 Datasheet, Volume 2 of 2

RW_L

RSVD1: These bits are reserved for future use.

RW_L

OVTATTACK: Override of Unsolicited Connection State Attack and Terminate.

0: Disable Override. Attack Terminate allowed.

1: Enable Override. Attack Terminate disallowed.

This register bit is locked when PAVPE is set.

RW_L

HVYMODSEL: This bit is applicable only for PAVP2 operation mode. This bit is also

applicable for PAVP3 mode only if the per-App memory config is disabled due to the

clearing of bit 9 in the Crypto Function Control_1 register (address 0x320F0).

0: Lite Mode (Non-Serpent mode)

1: Serpent Mode

For enabled PAVP3 mode, this one type boot time programming has been replaced by

per-App programming (through the Media Crypto Copy command). Note that PAVP2 or

PAVP3 mode selection is done by programming bit 8 of the MFX_MODE - Video Mode

RW_KL

PAVPLCK: This bit locks all writeable contents in this register when set (including

itself). Only a hardware reset can unlock the register again. This lock bit needs to be

set only if PAVP is enabled (bit 1 of this register is asserted).

RW_L

PAVPE:

0: PAVP functionality is disabled.

1: PAVP functionality is enabled.

This register is locked when PAVPLCK is set.

RW_L

PCME: This field enables Protected Content Memory within Graphics Stolen Memory.

This memory is the same as the WOPCM area, whose size is defined by bit 5 of this

A value of 0 in this field indicates that Protected Content Memory is disabled, and

cannot be programmed in this manner when PAVP is enabled.

A value of 1 in this field indicates that Protected Content Memory is enabled, and is the

only programming option available when PAVP is enabled. (Note that the processor

legacy Lite mode programming of PCME bit = 0 is not supported. For non-PAVP3 Mode,

even for Lite mode configuration, this bit should be programmed to 1 and

HVYMODESEL = 0).

This bit should always be programmed to 1 if bits 1 and 2 (PAVPE and PAVP lock bits)

are both set. With per-App Memory configuration support, the range check for the

WOPCM memory area should always happen when this bit is set, regardless of Lite or

Serpent mode, or PAVP2 or PAVP3 mode programming.

Bit

Range

Default &

Access

Field Name (ID): Description