nutscan_add_device_to_device(3) [debian man page]

NUTSCAN_ADD_DEVICE_T(3) 					    NUT Manual						   NUTSCAN_ADD_DEVICE_T(3)

NAME

       nutscan_add_device_to_device - Concatenate two devices structure.

SYNOPSIS

       #include <nut-scan.h>

       nutscan_device_t * nutscan_add_device_to_device(nutscan_device_t * first, nutscan_device_t * second);

DESCRIPTION

       The nutscan_device_t contains the following variables:

	   nutscan_device_type_t   type;
	   char *	   driver;
	   char *	   port;
	   nutscan_options_t	   opt;
	   struct nutscan_device * prev;
	   struct nutscan_device * next;

       This is a double linked list of device. Each device is described by its type, its driver name, its port and any number of optional data.

       The nutscan_add_device_to_device() concatenates first and second devices to a unique device. No new device is created, the two linked list
       are simply linked to each other. So first and second devices are likely to be modified by this function.

RETURN VALUE

       The nutscan_add_device_to_device() functions returns a pointer to a device containg both passed devices. Note that it's not a new device,
       so it is either first or second which is returned.

SEE ALSO

       nutscan_scan_usb(3), nutscan_scan_xml_http(3), nutscan_scan_nut(3), nutscan_scan_avahi(3), nutscan_scan_ipmi(3), nutscan_scan_snmp(3),
       nutscan_display_ups_conf(3), nutscan_display_parsable(3), nutscan_new_device(3), nutscan_free_device(3), nutscan_add_option_to_device(3)

Network UPS Tools						    05/22/2012						   NUTSCAN_ADD_DEVICE_T(3)

DEVICE(9)                                                  BSD Kernel Developer's Manual                                                 DEVICE(9)

NAME

     device -- an abstract representation of a device

SYNOPSIS

     typedef struct device *device_t;

DESCRIPTION

     The device object represents a piece of hardware attached to the system such as an expansion card, the bus which that card is plugged into,
     disk drives attached to the expansion card etc.  The system defines one device, root_bus and all other devices are created dynamically during
     autoconfiguration.  Normally devices representing top-level busses in the system (ISA, PCI etc.) will be attached directly to root_bus and
     other devices will be added as children of their relevant bus.

     The devices in a system form a tree.  All devices except root_bus have a parent (see device_get_parent(9)).  In addition, any device can have
     children attached to it (see device_add_child(9), device_add_child_ordered(9), device_find_child(9), device_get_children(9), and
     device_delete_child(9)).

     A device which has been successfully probed and attached to the system will also have a driver (see device_get_driver(9) and driver(9)) and a
     devclass (see device_get_devclass(9) and devclass(9)).  Various other attributes of the device include a unit number (see
     device_get_unit(9)), verbose description (normally supplied by the driver, see device_set_desc(9) and device_get_desc(9)), a set of bus-spe-
     cific variables (see device_get_ivars(9)) and a set of driver-specific variables (see device_get_softc(9)).

     Devices can be in one of several states:

     DS_NOTPRESENT  the device has not been probed for existence or the probe failed

     DS_ALIVE       the device probe succeeded but not yet attached

     DS_ATTACHED    the device has been successfully attached

     DS_BUSY        the device is currently open

     The current state of the device can be determined by calling device_get_state(9).

SEE ALSO

     devclass(9), driver(9)

AUTHORS

     This manual page was written by Doug Rabson.

BSD                                                                June 16, 1998                                                               BSD