Copyright (c) 1997, Sun Microsystems, Inc. All Rights Reserved
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.
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.
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]
socal@sbus-slot,0
The Fibre Channel Host Bus Adapter is an SBus card which implements two full duplex Fibre Channel interfaces. Each Fibre Channel interface can connect to a Fibre Channel Arbitrated Loop (FC-AL).
The socal device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
ELF Kernel Module
See attributes(5) for descriptions of the following attributes:
| ATTRIBUTE TYPE ATTRIBUTE VALUE |
| Architecture SPARC |
sbus(4), sf(7D), ssd(7D)
Writing Device Drivers
ANSI X3.230-1994, Fibre Channel Physical and Signalling Interface (FC-PH)
ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)
The messages described below may appear on system console in addition to being logged.
On the console, these messages are preceded by:
socal%d: port %a
where %d is the instance number of the socal controller and %a is the port on the host adapter. Fibre Channel Loop is ONLINE
The Fibre Channel loop is now online.
The Fibre Channel loop is now offline.
Move soc+ card to another slot.
Driver did not attach, devices will be inaccessible.
Driver did not attach, devices will be inaccessible.
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible.
Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.