mpt_config(9) [suse man page]

MPT_CONFIG(9)						       Message-based devices						     MPT_CONFIG(9)

NAME

       mpt_config - Generic function to issue config message

SYNOPSIS

       int mpt_config(MPT_ADAPTER * ioc, CONFIGPARMS * pCfg);

ARGUMENTS

       ioc
	   Pointer to an adapter structure

       pCfg
	   Pointer to a configuration structure. Struct contains action, page address, direction, physical address and pointer to a configuration
	   page header Page header is updated.

DESCRIPTION

       Returns 0 for success -EPERM if not allowed due to ISR context -EAGAIN if no msg frames currently available -EFAULT for non-successful
       reply or no reply (timeout)

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010							     MPT_CONFIG(9)

csx_MapLogSocket(9F)					   Kernel Functions for Drivers 				      csx_MapLogSocket(9F)

NAME

       csx_MapLogSocket - return the physical socket number associated with the client handle

SYNOPSIS

       #include <sys/pccard.h>

       int32_t csx_MapLogSocket(client_handle_t ch, map_log_socket_t *ls);

INTERFACE LEVEL

       Solaris DDI Specific (Solaris DDI)

PARAMETERS

       ch	Client handle returned from csx_RegisterClient(9F).

       ls	Pointer to a map_log_socket_t structure.

DESCRIPTION

       This function returns the physical socket number associated with the client handle.

STRUCTURE MEMBERS

       The structure members of map_log_socket_t are:

       uint32_t     LogSocket;	    /* logical socket number */
       uint32_t     PhyAdapter;     /* physical adapter number */
       uint32_t     PhySocket;	    /* physical socket number */

       The fields are defined as follows:

       LogSocket       Not used by this implementation of Card Services and can be set to any arbitrary value.

       PhyAdapter      Returns the physical adapter number, which is always 0 in the Solaris implementation of Card Services.

       PhySocket       Returns	the physical socket number associated with the client handle. The physical socket number is typically used as part
		       of an error or message string or if the client creates minor nodes based on the physical socket number.

RETURN VALUES

       CS_SUCCESS		       Successful operation.

       CS_BAD_HANDLE		       Client handle is invalid.

       CS_UNSUPPORTED_FUNCTION	       No PCMCIA hardware installed.

CONTEXT

       This function may be called from user or kernel context.

SEE ALSO

       csx_RegisterClient(9F)

       PC Card 95 Standard, PCMCIA/JEIDA

SunOS 5.10							    19 Jul 1996 					      csx_MapLogSocket(9F)