Lines Matching +full:multi +full:- +full:functional
8 cfgadm_pci \- PCI, CompactPCI, and PCI Express Hotplug hardware specific
13 \fB/usr/sbin/cfgadm\fR [\fB-f\fR] [\fB-y\fR | \fB-n\fR] [\fB-v\fR]
14 [\fB-o\fR \fIhardware_options\fR] \fB-c\fR \fIfunction\fR \fIap_id\fR [\fIap_id\fR]
19 \fB/usr/sbin/cfgadm\fR [\fB-f\fR] [\fB-y\fR | \fB-n\fR] [\fB-v\fR]
20 [\fB-o\fR \fIhardware_options\fR] \fB-x\fR \fIhardware_function\fR \fIap_id\fR
26 \fB/usr/sbin/cfgadm\fR [\fB-v\fR] [\fB-s\fR \fIlisting_options\fR]
27 [\fB-o\fR \fIhardware_options\fR] [\fB-l\fR [\fIap_id\fR | \fIap_type\fR]]
32 \fB/usr/sbin/cfgadm\fR [\fB-v\fR] [\fB-o\fR \fIharware_options\fR] \fB-t\fR \fIap_id\fR [\fIap_id\f…
37 \fB/usr/sbin/cfgadm\fR [\fB-v\fR] [\fB-o\fR \fIhardware_function\fR] \fB-h\fR
65 logical \fBap_id\fR is a shorter, and more user-friendly name. For PCI hot
88 APID : absolute-slot-path
90 absolute-slot-path : \fIslot-path\fR[\fI:slot-path\fR[\fI:slotpath\fR ...]]
92 slot-path : [\fIfru-id\fR.]\fIslot-id\fR
93 where \fIfru-id\fR indicates the chassis FRU, if any,
94 containing the \fIslot-id\fR
96 fru-id : \fIfru-type\fR[\fIserialid#\fR]
97 where \fIfru-type\fR is "iob" for PCI Express expansion
101 slot-id: \fIslot-name\fR | \fIdevice-type\fR \fIphysical-slot#\fR |\e
102 \fInexus-driver-name\fR \fInexus-driver-instance\fR.\e
103 \fIdevice-type\fR \fIpci-device-number\fR
110 where \fIslot-name\fR is a name assigned by the platform or hardware itself;
111 \fIdevice-type\fR is either "pcie"for PCI Express devices or "pci" for PCI
112 devices; \fInexus-driver-name\fR is the driver name for the device component;
113 \fIphysical-slot#\fR is the hardware slot number; and \fIpci-device-number\fR
117 First, an \fIabsolute-slot-path\fR is constructed that attempts to describe the
119 for the user . This \fIabsolute-slot-path\fR consists of \fIslot-path\fR
120 components each seperated by a ":" (colon). The leaf or left-most
121 \fIslot-path\fR component describes the device of the attachment point itself
122 while its right adjacent \fIslot-path\fR component up to the right or top-most
123 \fIslot-path\fR component describes the parent up to the root devices,
127 Each \fIslot-path\fR consists of a \fIslot-id\fR optionally preceded by an
128 \fIfru-id\fR, which indicates an expansion chassis containing the device
129 described by \fIslot-id\fR (detailed below). \fIfru-id\fR consists of
130 \fIfru-type\fR followed by an optional \fIserialid#\fR. \fIfru-type\fR is "iob"
132 64-bit hexadecimal number indicating a raw serial number obtained from the
133 expansion chassis hardware, or a 4 upper-case ASCII character sequence for Sun
137 Each \fIslot-id\fR consists of one of three possible forms:
141 \fBslot-id form (1)\fR
145 \fIslot-names\fR
151 \fBslot-id form (2)\fR
155 \fIdevice-type\fR \fIphysical-slot#\fR
161 \fBslot-id form (3)\fR
165 \fInexus-driver-name\fR \fInexus-driver-instance\fR. \fIdevice-type\fR
166 \fIpci-device-number\fR
177 The \fIslot-names\fR in "slot-id form (1)" is taken from the "slot-names"
182 In "slot-id form (2)", \fIdevice-type\fR indicates the device type of the
184 \fIphysical-slot#\fR, take from the "physical-slot#" property of its
188 "slot-id form (3)" is used when all other forms cannot successfully be
189 constructed, and is considered to be the default form. \fInexus-driver-name\fR
190 is the component's driver name; \fInexus-driver-instance\fR is such driver's
191 instance; \fIdevice-type\fR is the same as described in form (2);
192 \fIpci-device-type\fR is the PCI device number as described and used for device
196 In summary of the \fIslot-path\fR component, expanding the optional FRU
197 component that may precede it, \fIslot-path\fR will consist one of the
202 (1) [ iob[serialid#]. ] slot-names
205 nexus-driver-name nexus-driver-instance.
206 device_type pci-device-number
222 if the \fIabsolute-slot-path\fR can fit within the fixed length limit of
223 \fBcfgadm\fR's \fIap_id\fR field, then \fIabsolute-slot-path\fR itself is used
233 (\fIabsolute-slot-path\fR exceeds the \fIap_id\fR length limit) if the last
247 (\fIabsolute-slot-path\fR exceeds the \fIap_id\fR length limit) the default
248 form, "slot-id form (3)", of the last \fIslot_path\fR component is used
253 Whichever final \fIap_id\fR name is used, the \fIabsolute-slot-path\fR is
255 \fB-s\fR or \fB-v\fRoptions. This information can be used to physically locate
257 \fIabsolute-slot-path\fR is tranformed slightly when stored in the information
259 closely denote a topological context. The \fIabsolute-slot-path\fR can include
260 \fIslot-path\fR components that are not hotpluggable above the leaf or
261 right-most \fIslot-path\fR component up to the onboard host slot.
272 \fB\fB-c\fR \fIfunction\fR\fR
342 \fB\fB-f\fR\fR
352 \fB\fB-h\fR \fIap_id\fR | \fIap_type\fR\fR
362 \fB\fB-l\fR \fIlist\fR\fR
372 \fB\fB-o\fR \fIhardware_options\fR\fR
382 \fB\fB-s\fR \fIlisting_options\fR\fR
392 \fB\fB-t\fR \fIap_id\fR\fR
403 \fB\fB-v\fR\fR
409 When the \fB-v\fR option is used with the \fB-l\fR option, the \fBcfgadm\fR
418 \fBslot-name\fR property of the slot's bus node. The information in the Type
419 field is printed with or without the \fB-v\fR option. The occupant \fBType\fR
439 The card in the slot is either a single-function or multi-function device.
442 example, SCSI, \fBethernet\fR, \fBpci-isa\fR, and so forth. If the card is a
443 multi-functional device, \fBMULT\fR will get printed instead.
450 Most PCI cards with more than one device are not multi-function devices, but
453 bridges are \fBpci-pci,\fR a generic PCI to PCI bridge or \fBstpci\fR, a
454 semi-transparent PCI bridge.
462 \fB\fB-x\fR \fIhardware_function\fR\fR
515 Without sub-arguments, print a list of the current LED settings. With
516 sub-arguments, set the mode of a specific LED for a slot.
537 example# \fBcfgadm -x led pci0:hpc0_slot1\fR
548 example# \fBcfgadm -x led=fault,mode=on pci0:hpc0_slot1\fR
557 example# \fBcfgadm -x led=power,mode=off pci0:hpc0_slot0\fR
567 example# \fBcfgadm -x led=active,mode=on pci0:hpc0_slot3\fR
586 example# \fBcfgadm -l\fR
588 c0 scsi-bus connected configured unknown
589 c1 scsi-bus connected unconfigured unknown
590 c2 scsi-bus connected unconfigured unknown
606 The following command lists all DR-capable attachment points:
615 c0 scsi-bus connected configured unknown
616 c1 scsi-bus connected unconfigured unknown
617 c2 scsi-bus connected unconfigured unknown
636 example# \fBcfgadm -c disconnect cpci_slot4\fR
665 example# \fBcfgadm -c configure cpci_slot4\fR
697 example# \fBcfgadm -s cols=ap_id:info\fR
701 iou#0-pci#0 Location: iou#0-pci#0
702 iou#0-pci#1 Location: iou#0-pci#1
703 iou#0-pci#1:iob.pci3 Location: iou#0-pci#1/iob.pci3
704 iou#0-pci#1:iob.pci4 Location: iou#0-pci#1/iob.pci4
705 iou#0-pci#2 Location: iou#0-pci#2
706 iou#0-pci#2:iob58071.pcie1 Location: iou#0-pci#2/iob58071.pcie1
707 iou#0-pci#2:iob58071.special Location: iou#0-pci#2/iob58071.special
708 iou#0-pci#3 Location: iou#0-pci#3
709 iou#0-pci#3:iobBADF.pcie1 Location: iou#0-pci#3/iobBADF.pcie1
710 iou#0-pci#3:iobBADF.pcie2 Location: iou#0-pci#3/iobBADF.pcie2
711 iou#0-pci#3:iobBADF.pcie3 Location: iou#0-pci#3/iobBADF.pcie3
712 iou#0-pci#3:iobBADF.pci1 Location: iou#0-pci#3/iobBADF.pci1
713 iou#0-pci#3:iobBADF.pci2 Location: iou#0-pci#3/iobBADF.pci2
720 In this example, the "iou#0-pci#[0-3]" represents the top-most hotpluggable
721 slots in the system. Since the "iou#<n>-pci#<n>" form does not match any of the
724 derived from the platform through the "slot-names" property.
729 \fBSlot iou#0-pci#0\fR
739 \fBSlot iou#0-pci#1\fR
746 expansion chassis in this case does not have or exports a \fIserial-id\fR.
752 \fBSlot iou#0-pci#2\fR
757 \fIserial-id\fR of 58071. Within that expansion chassis are two hotpluggable
766 \fBSlot iou#0-pci#3\fR
780 non-hotpluggable host slots:
785 example# \fBcfgadm -s cols=ap_id:info\fR
814 example# \fBcfgadm -s cols=ap_id:info\fR
829 "px_pci7.pcie0" and "px_pci11.pcie0". In this case, it uses "slot-id form (3)"
830 ( the default form) for the base \fIslot-path\fR component in the
831 \fIabsolute-slot-path\fR because the framework could not obtain enough
836 Interpreting right-to-left, attachment point "px_pci7.pcie0" represents a PCI
845 \fIserial-id\fR and with three hotpluggable PCI Express slots.
855 example# \fBcfgadm -s cols=ap_id:info\fR
881 Because the length of the \fIabsolute-slot-path\fR form of
883 limit, and the leaf \fIslot-path\fR component is globally unique, "ap_id form
884 (2)" is used, where the leaf \fIslot-path\fR component in the
885 \fIabsolute-slot-path\fR is used as the final \fIApId\fR.
891 information to uniquely identify the leaf \fIslot-id\fR on its own (for
892 instance, missing the \fIserial-id\fR):
897 example# \fBcfgadm -s cols=ap_id:info\fR
915 \fIserial-id\fR 4567812345678. Nested under the PCI Express slot "pcie3" of
917 part expansion chassis without a \fIserial-id\fR and with two hotpluggable PCI
922 Because the length of the \fIabsolute-slot-path\fR form of
924 length limit, and the leaf \fIslot-path\fR component is not globally unique,
925 "ap_id form (3)" is used. "ap_id form (2)" is where \fIslot-id\fR form (3)
926 (default form) of the leaf \fIslot-path\fR component in the
927 \fIabsolute-slot-path\fR is used as the final \fIApId\fR.
931 The default form or "slot-id form (3)" of the leaf component