Testing Third-Party PCI Cards

Chapter 3. Test Strategy

Basic Test Phase

In the Basic Test phase, the PCI product must pass common basic tests that evaluate the product for:

PCI 2.1 Compliance

The PCI Driver Development Kit includes a PCI 2.1 compliance checklist, which is a subset of the PCI-SIG PCI compliance checklist. Most of the checklist items will be filled in by the IHV, while the rest will be tested in-house. Sun's PCI 2.1 compliance test (CRDTST14) is provided in the DDK for IHV card self-testing.

SunVTS Operation (wherever applicable)

SunVTS is a tool developed by Sun that can be invoked on a running system to test the system resources by executing built-in diagnostics and tests. At this time, SunVTS tests only Sun branded devices and clones. IHVs can develop their own diagnostics using the SunVTS developer kit. It is Sun's intent to integrate the diagnostics and tests of as many PCI products as possible into SunVTS, to simplify the diagnosis of system problems.

Solaris DDI Compliance

A program called ddbct is available on the Driver Development Web site to test compliance with the Solaris DDI on the executable driver binaries. (See Run the ddbct Compliance Test Script.)

System V Package Installation Format

The test involves using the UNIX? pkgadd(1M) command for driver installation and the pkgrm (1M) command for driver removal. The driver package should be installed in the /opt directory. The actual drivers should normally be installed in the /usr/kernel/drv directory, they can also be installed in /kernel/drv or platform/sun4u/kernel/drv. 64-bit drivers should be installed in platform/sun4u/kernel/drv.

System Power-up With Card and Driver

The platform must boot correctly with the card installed and the driver connected.

Power Management (Energy Star) Compliance

The product will be tested for Energy Star compliance, as applicable. Sun encourages IHVs to make their cards and drivers compliant; more information is available on the Driver Development Web site.