*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->FreeBSD man pages -> pass (4)              
Title
Content
Arch
Section
 

PASS(4)

Contents


NAME    [Toc]    [Back]

     pass -- CAM application passthrough driver

SYNOPSIS    [Toc]    [Back]

     device pass

DESCRIPTION    [Toc]    [Back]

     The pass driver provides a way for userland applications to issue CAM
     CCBs to the kernel.

     Since the pass driver allows direct access to the CAM subsystem, system
     administrators should exercise caution when granting access to this
     driver.  If used improperly, this driver can allow userland applications
     to crash a machine or cause data loss.

     The pass driver attaches to every SCSI device found in the system.  Since
     it attaches to every device, it provides a generic means of accessing
     SCSI devices, and allows the user to access devices which have no "standard"
 peripheral driver associated with them.

KERNEL CONFIGURATION    [Toc]    [Back]

     It is only necessary to configure one pass device in the kernel; pass
     devices are automatically allocated as SCSI devices are found.

IOCTLS    [Toc]    [Back]

     CAMIOCOMMAND     This ioctl takes most kinds of CAM CCBs and passes them
		      through to the CAM transport layer for action.  Note
		      that some CCB types are not allowed through the
		      passthrough device, and must be sent through the xpt(4)
		      device instead.  Some examples of xpt-only CCBs are
		      XPT_SCAN_BUS, XPT_DEV_MATCH, XPT_RESET_BUS,
		      XPT_SCAN_LUN, XPT_ENG_INQ, and XPT_ENG_EXEC.  These CCB
		      types have various attributes that make it illogical or
		      impossible to service them through the passthrough
		      interface.

     CAMGETPASSTHRU   This ioctl takes an XPT_GDEVLIST CCB, and returns the
		      passthrough device corresponding to the device in question.
  Although this ioctl is available through the pass
		      driver, it is of limited use, since the caller must
		      already know that the device in question is a
		      passthrough device if they're issuing this ioctl.  It is
		      probably more useful to issue this ioctl through the
		      xpt(4) device.

FILES    [Toc]    [Back]

     /dev/passn  Character device nodes for the pass driver.  There should be
		 one of these for each device accessed through the CAM subsystem.

DIAGNOSTICS    [Toc]    [Back]

     None.

SEE ALSO    [Toc]    [Back]

      
      
     cam(3), cam_cdbparse(3), xpt(4), camcontrol(8)

HISTORY    [Toc]    [Back]

     The CAM passthrough driver first appeared in FreeBSD 3.0.

AUTHORS    [Toc]    [Back]

     Kenneth Merry <ken@FreeBSD.org>

BUGS    [Toc]    [Back]

     It might be nice to have a way to asynchronously send CCBs through the
     passthrough driver.  This would probably require some sort of read/write
     interface or an asynchronous ioctl interface.


FreeBSD 5.2.1		       October 10, 1998 		 FreeBSD 5.2.1
[ Back ]
 Similar pages
Name OS Title
smapi FreeBSD System Management Application Program Interface driver
MrmFetchWidgetOverride HP-UX Fetches any indexed (UIL named) application widget. It overrides the arguments specified for this application
MrmFetchWidgetOverride IRIX Fetches any indexed (UIL named) application widget. It overrides the arguments specified for this application
DtActionCallbackProc HP-UX notify application that the status of an application has changed
el FreeBSD Ethernet driver for 3Com Etherlink 3C501 device driver
ispcvt FreeBSD verify if current video driver is pcvt driver
tels HP-UX STREAMS Telnet slave (pseudo-terminal) driver, STREAMS Telnet master driver (used by telnetd only), respective
telm HP-UX STREAMS Telnet slave (pseudo-terminal) driver, STREAMS Telnet master driver (used by telnetd only), respective
exit IRIX End the application
exit IRIX End the application
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service