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

  man pages->FreeBSD man pages -> DEVICE_PROBE (9)              
Title
Content
Arch
Section
 

DEVICE_PROBE(9)

Contents


NAME    [Toc]    [Back]

     DEVICE_PROBE -- probe for device existence

SYNOPSIS    [Toc]    [Back]

     #include <sys/param.h>
     #include <sys/bus.h>

     int
     DEVICE_PROBE(device_t dev);

DESCRIPTION    [Toc]    [Back]

     This device method should probe to see if the device is present.  It
     should return 0 if the device exists, ENXIO if it cannot be found.  If
     some other error happens during the probe (such as a memory allocation
     failure), an appropriate error code should be returned.  For cases where
     more than one driver matches a device, a priority value can be returned.
     In this case, success codes are values less than or equal to zero with
     the highest value representing the best match.  Failure codes are represented
 by positive values and the regular UNIX error codes should be used
     for the purpose.

     If a driver returns a success code which is less than zero, it must not
     assume that it will be the same driver which is attached to the device.
     In particular, it must not assume that any values stored in the softc
     structure will be available for its attach method and any resources allocated
 during probe must be released and re-allocated if the attach method
     is called.  If a success code of zero is returned, the driver can assume
     that it will be the one attached.

     Devices which implement busses should use this method to probe for the
     existence of devices attached to the bus and add them as children.  If
     this is combined with the use of bus_generic_attach(9) the child devices
     will be automatically probed and attached.

RETURN VALUES    [Toc]    [Back]

     A value equal to or less than zero indicates success, greater than zero
     indicates an error (errno). For values equal to or less than zero: zero
     indicates highest priority, no further probing is done; for a value less
     than zero, the lower the value the lower the priority, e.g. -100 indicates
 a lower priority than -50.

SEE ALSO    [Toc]    [Back]

      
      
     device(9), DEVICE_DETACH(9), DEVICE_IDENTIFY(9), DEVICE_SHUTDOWN(9)

AUTHORS    [Toc]    [Back]

     This man page was written by Doug Rabson.


FreeBSD 5.2.1			 June 16, 1998			 FreeBSD 5.2.1
[ Back ]
 Similar pages
Name OS Title
probenis Tru64 Probes for existence of NIS server
mopprobe OpenBSD MOP Probe Utility
scsiha IRIX probe and control scsi buses
scsicontrol IRIX probe and control scsi devices
autochanger HP-UX SCSI interfaces for medium changer device and magnetooptical autochanger surface device
devctl FreeBSD device event reporting and device control interface
device_add_child_ordered FreeBSD add a new device as a child of an existing device
filename_to_drivername IRIX determine the device name for the device file
filename_to_devname IRIX determine the device name for the device file
device_add_child FreeBSD add a new device as a child of an existing device
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service