When is the checklist process required?
As the list of items in the checklist is quite extensive, we will provide
reasonable guidelines on when the entire checklist process needs to be done.
-
When delivering a new driver.
-
When delivering a dramatically changed driver (new functionality, major
rewrites, upgrades to ddi8).
-
When releasing a new HBA model.
NOTE:
If there are other variations of
the new HBA model which are relatively the same (same chipset, same
driver code and firmware, perhaps different connectors, differential
vs. single ended), then we would only require a sanity test (see
below) of the
similar models instead of the full-blown certification.
-
Re-certification is not required if the driver has been updated with
some bug fixes, unless the extent of the fixes is significant.
However, sanity testing (see below) and testing key problem areas must be done.
Although re-certification in this case is not required,
we recommended that the automated hbacert
test suite is re-run for regression testing of the updated driver,
regardless of the level of change in the code.
-
Re-certification of unchanged drivers and hardware is not required for
SVR5 update releases, unless significant changes have been made
to the SDI infrastructure.
However, sanity testing (see below) must be done.
Although re-certification in this case is not required,
we recommended that the automated hbacert
test suite is re-run for regression testing of the existing driver
on the updated operating system.
The checklist process should begin at the time the new/updated driver
or HBA model is first discussed with SCO.
You should review the checklist requirements and compare them to your
current development and testing plans.
Any requirements which are not in your current plan for the HBA
driver should be discussed with SCO at an early phase of development.
We are not required to list the vendor's HBA as "Certified"
until the terms of the HBA Certification Requirements Checklist
have been met and any exceptions discussed and accepted.
Sanity testing HBAs
``Sanity testing'' in the context of HBA testing
means doing the following:
-
Perform a UnixWare 7 installation and surface analysis using the
HBA Controller under test as the primary controller of the boot disk.
-
Perform a UnixWare 7 installation and surface analysis using one
instance of the HBA under test for a disk OTHER than the boot disk.
-
Use another type of controller for the boot disk so that only one
instance of the driver under test is being used on the system.
Next topic:
Overview description of the checklist
Previous topic:
Using the HBA Certification Checklist
© 2005 The SCO Group, Inc. All rights reserved.
OpenServer 6 and UnixWare (SVR5) HDK - June 2005