-o dev=[device name]
|
[device name] is the path name of the device being tested. The default value is ses.
Since the current SunVTS infrastructure doesn't allow specifying multiple devices under the dev suboption, this suboption is not used in dpmtest. A new suboption dpmdev has been introduced to satisy this requirement.
|
dpmdev=[device1+device2...]
|
device1, device2,... represent the SES/SSC100 devices being tested. The default value is all the SSC100s present in the system.Note: The values for the dpmdev suboption can be device names such as ses0, ses1, ssc100@16, ssc100@1a, etc. Multiple values can be specified with a '+' (plus sign) seperator. An absolute path through fibre paths to devices are allowed (for expample, /dev/es/ses0) as dpmdev suboption values. However, absolute paths through a i2c path to devices are not allowed because commas are not allowed as part of a suboption value. Commas delimit suboptions in the options string (for example, /devices/pci@9, 700000/ebus@1/i2c@1, 30/controller@0, 16:ssc100).
Note: The following devices in the Sun Fire V880 system may be specified for dpmdev suboption values:
Fibre Path:
-
ses0 - fibre path to base backplane's SSC100 (/dev/es/ses0) device on loopA.
-
ses1 - fibre path to base backplane's SSC100 (/dev/es/ses1) device on loopB. This is valid only when a CrystalB+ PCI card present in the system.
I2C Path:
-
ssc100@16 - base backplane's SSC100 device on loopA through a i2c path.
-
ssc100@1a - base backplane's SSC100 device on loopB through a i2c path.
-
ssc100@1c - expansion backplane's SSC100 device on loopA through a i2c path.
-
ssc100@1e - expansion backplane's SSC100 device on loopB through a i2c path.
Note: ssc100@1c and ssc100@1e will be valid only when an expansion backplane is present in the system.
|