1 '\" te 2 .\" Copyright (c) 2001 Sun Microsystems, Inc. All Rights Reserved 3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. 4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. 5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] 6 .TH DR 7D "Sep 29, 2003" 7 .SH NAME 8 dr, drmach, ngdr, ngdrmach \- Sun Enterprise 10000 dynamic reconfiguration 9 driver 10 .SH SYNOPSIS 11 .LP 12 .nf 13 \fBdr\fR 14 .fi 15 16 .LP 17 .nf 18 \fBdrmach\fR 19 .fi 20 21 .LP 22 .nf 23 \fBngdr\fR 24 .fi 25 26 .LP 27 .nf 28 \fBngdrmach\fR 29 .fi 30 31 .SH DESCRIPTION 32 .sp 33 .LP 34 The dynamic reconfiguration (DR) driver consists of a platform-independent 35 driver and a platform-specific module. The DR driver uses standard features of 36 the Solaris operating environment whenever possible to control DR operations 37 and calls the platform specific module as needed. The DR driver creates minor 38 nodes in the file system that serve as attachment points for DR operations. 39 .sp 40 .LP 41 The DR driver provides a pseudo-driver interface to sequence attach and detach 42 operations on system boards using file system entry points referred to as 43 "attachment points." The attachment point form depends on the platform. 44 .SS "Sun Enterprise 10000 Server" 45 .sp 46 .LP 47 On the Sun Enterprise 10000 server, the DR driver consists of a 48 platform-independent driver (\fBngdr\fR) and a platform-specific module 49 (\fBngdrmach\fR). 50 .sp 51 .LP 52 The domain configuration server (DCS) accepts DR requests from the system 53 services processor (SSP) and uses the \fBlibcfgadm\fR(3LIB) interface to 54 initiate the DR operation. After the operation is performed, the results are 55 returned to the SSP. For more information about the DCS on the Sun Enterprise 56 10000, refer to the \fBdcs\fR(1M) man page and the \fISun Enterprise 10000 57 Dynamic Reconfiguration User Guide\fR. 58 .sp 59 .LP 60 The DR driver creates physical attachment points for system board slots that 61 takes the following form: 62 .sp 63 .in +2 64 .nf 65 /devices/pseudo/ngdr@0:SB\fIx\fR 66 .fi 67 .in -2 68 69 .sp 70 .LP 71 Where \fIx\fR represents the slot number (0 to 15) for a particular board. 72 .sp 73 .LP 74 The \fBcfgadm_sbd\fR(1M) plugin creates dynamic attachment points that refer to 75 components on system boards, including CPUs, memory, or I/O devices. Refer to 76 the \fBcfgadm_sbd\fR(1M) man page for more details. 77 .SH SEE ALSO 78 .sp 79 .LP 80 \fBcfgadm_sbd\fR(1M), \fBioctl\fR(2), \fBlibcfgadm(3LIB)\fR 81 .sp 82 .LP 83 \fISun Enterprise 10000 Dynamic Reconfiguration User Guide\fR