Solaris Ready Device Driver Criteria

Solaris Ready

Resources

I/O Technologies
Solaris Ready Program
Partner Advantage Products Catalog
Partner Advantage Program
Solaris Product Line
Solaris Software
Developer Resources
Device Drivers
BigAdmin: Solaris 10
System administrators
Sun Developer Network:
For developers
Solaris 10 Knowledge
Technical knowledge
Solaris Ready Device Driver Critera

Device Driver Eligibility

Subject

6/22/05 Rev 2.5 Base Line Criteria Device Driver

Objective

Outline of Criteria for entry into Solaris Ready Program for Device Driver for all Sun Platforms.

Goals of the Program include qualifying  Device Driver products for the Solaris Ready Program, promoting customer awareness, and enabling identification and selection of high quality add-on  products for Sun's platform customers. Acknowledging that hardware may be built by other partners.

A Device Driver element consists of a loadable software module which is compliant with the Solaris Device Driver Interface. A Device Driver includes pseudo driver, streams driver, block driver, and character drivers. Hardware interfaces are specific to individual chip interfaces, and will not be covered in this criteria. Sun's Solaris Ready Program shall add the additional criteria to Device Driver products.

Company Criteria:

1. Channel distribution, service and support in geographies worldwide.
2. Ability to provide vendor updates.
3. Agreement to support newer versions of the Solaris OS in a timely manner (where applicable).
4. Acquire Sun platforms for the development and support of the Solaris OS.

Product Criteria:

1. Meet the Solaris Ready Platform Support, Installation Criteria, Diagnostics, Additional Criteria as listed below.
2. Ensure documentation describes installation.
3. Documentation for updates and patches on company website or CD-ROM.
4. Include sufficient packaging materials and other materials unique to the product.
5. Device Driver installation and system identification of driver software.
6. Shall not threaten the security or the integrity of the Solaris OS.
7. Shall not access memory that is not specifically allocated or associated with the device driver.
8. Must detect and behave appropriately when server shutdown is initiated.
9. Shall use some mechanism to avoid data corruption caused by concurrent read/write access by users.

Product Support:

1. Make pre-sales specification and product information available on line.
2. Provide product warranty and technical support information.
3. Maintain a  supported Sun system configuration list for customers, including supported system configurations and known restrictions or conflicts.

Platform Support:

1. Product must be operable on all Sun platforms, or identified in documentation for specific platform issues.
2. The duty cycle shall be applicable for the product type for 24 continuous hours.

Installation Criteria:

1. System V Package Installation Format using pkgadd(1M) and pkgrm(1M) utilities.
2. Solaris Boot Verification with Driver.
3. Solaris DDI Compliance of device drivers.
4. Power Management (such as Energy Star) as applicable.
5. Interoperability with other device drivers and system components.
6. Installation on UltraSPARC hardware and on Sun hardware based on the AMD Opteron processor.
7. Support for 64bit Solaris OS.

Diagnostics:

1. Self Diagnostic to isolate failure.
2. User level diagnostic for end user use.

Additional Criteria:

1. Complete the Basic Test section of the Solaris Ready testing of Third Party PCI Cards shall be used.
2. Functional tests of device drivers as applicable to the product type.
3. The products should function as described in product documentation manuals on UltraSPARC and/or Sun x64(AMD Opteron processor-based) platforms, where applicable.
4. Vendor is required to inform Sun of any changes/revisions to their hardware, firmware or software at least 1 month in advance of the change. Vendor products that are obsolete or modified within the 6 month period of nomination will need to be re-tested.
5. Partner hardware required for testing Device Drivers shall be tested at the same time. Partner hardware manufactured by a different partner shall be required to pass verification status.