MLP Report

regulations, the output level requirement for
headphones is dropped from >= 1000 mVrms
to >= 120 mVrms. This provides freedom for
manufacturers to meet both the EU <= 150 mVrms
@ 32 Ohms and the WLP >= 120 mVrms @ 32
Ohms requirements. The Fidelity Test tests
headphones at 300 Ohm load, though. Without
knowledge of the output impedance at the jack,
the test cannot extrapolate what the output level at
32 Ohms would have been from the output level at
300 Ohms. The test assumes that the output level
at 32 Ohms will be *less* than the output level at
300 Ohms, though. So any measurement >= 120
mVrms at 300 Ohms "could be" a passing result,
depending on the output impedance.
Resolution Description:
This errata covers headphone output level failures
where the output level >= 120 mVrms (-45.41
dBV.) 120 mV is -18.42 dBV. Any headphone
output level at 32 Ohms that is less than -18.42
dBV is a legitimate failure, even if it is targeted at
EU compliance. Any headphone output level
greater than 1 Vrms (0.707 Vrms for mobile
systems) is a legitimate pass, regardless of EU
compliance.
Windows 7
PCI Hardware
Compliance Test
For Systems
6/1/2011
401
Erratum
Issue Description:
The following PCI Compliance test failure is
acceptable: Bit 15 (Bridge Configuration Retry
Enable) in the Device Control register (offset 8h)
in the PCI Express Capability table must be
read-only and always return 0 as it is reserved
for devices other than PCI Express to PCI/PCI-X
Bridges. Assertion 13A41D3E-2576-41DC-
A67C-525DA3637CEA This failure is acceptable
because this is a PCIe 1.1 feature and the WLP
requires compliance with only PCIe 1.0a.
Windows 7 64-bit
Windows 7
PCI Hardware
Compliance Test
For Systems
6/1/2011
923
Erratum
Issue Description:
Assertion FAE18121-9177-4FB2-A081-
0D04C285EFF2 Bit range 15:0 (Extended
Capability ID)in the Enhanced Capability
Header register (offset 0h) in the Unrecognized
Enhanced Capability ID 13 table is Dh. It must
be in the range [0x0 - 0xB] as all other
Capability IDs are reserved.
Resolution Description:
This erratum is in place because the PCI
Compliance test doesn't recognize Extended
Capability IDs greater that 0xB. The PCI
Compliance test will be updated to correct this
in the future.
Windows 7 64-bit
Windows 7
PCI Hardware
Compliance Test
For Systems
6/1/2011
1241
Erratum
Issue Description:
This happens because the PCI Compliance test
assumes that if the Data Link Layer Link Active
Reporting Capable bit in the Link Capabilities
Windows 7 64-bit