csx_AccessConfigurationRegister man page on SmartOS

Man page or keyword search:  
man Server   16655 pages
apropos Keyword Search (all sections)
Output format
SmartOS logo
[printable version]

CSX_ACCESSCONFIGURATIONREGISTER(9F)	   CSX_ACCESSCONFIGURATIONREGISTER(9F)

NAME
       csx_AccessConfigurationRegister - read or write a PC Card Configuration
       Register

SYNOPSIS
       #include <sys/pccard.h>

       int32_t csx_AccessConfigurationRegister(client_handle_t ch,
	    access_config_reg_t *acr);

INTERFACE LEVEL
       Solaris DDI Specific (Solaris DDI)

PARAMETERS
       ch
	      Client handle returned from csx_RegisterClient(9F).

       acr
	      Pointer to an access_config_reg_t structure.

DESCRIPTION
       This function allows a client to read or write a	 PCCard	 Configuration
       Register.

STRUCTURE MEMBERS
       The structure members of access_config_reg_t are:

	 uint32_t     Socket;	  /* socket number*/
	 uint32_t     Action;	  /* register access operation*/
	 uint32_t     Offset;	  /* config register offset*/
	 uint32_t     Value;	  /* value read or written*/

       The fields are defined as follows:

       Socket
		 Not used in Solaris, but for portability with other Card Ser‐
		 vices implementations, it should be set to the logical socket
		 number.

       Action
		 May  be set to CONFIG_REG_READ or CONFIG_REG_WRITE. All other
		 values in the Action field are reserved for  future  use.  If
		 the  Action field is set to CONFIG_REG_WRITE, the Value field
		 is written to the specified configuration register. Card Ser‐
		 vices	does not read the configuration register after a write
		 operation. For that reason, the Value field is	 only  updated
		 by a CONFIG_REG_READ request.

       Offset
		 Specifies  the byte offset for the desired configuration reg‐
		 ister from the PC Card configuration register base  specified
		 in csx_RequestConfiguration(9F).

       Value
		 Contains the value read from the PC Card Configuration Regis‐
		 ter for a read operation. For a write	operation,  the	 Value
		 field contains the value to write to the configuration regis‐
		 ter. As noted above, on return	 from  a  write	 request,  the
		 Value	field  is the value written to the PC Card and not any
		 changed value that may have resulted from the	write  request
		 (that is, no read after write is performed).

       A  client  must	be very careful when writing to the COR (Configuration
       Option Register) at offset 0. This has the potential to change the type
       of  interrupt request generated by the PC Card or place the card in the
       reset state. Either request may	have  undefined	 results.  The	client
       should  read  the register to determine the appropriate setting for the
       interrupt mode (Bit 6) before writing to the register.

       If a client wants to reset a PCCard, the csx_ResetFunction(9F) function
       should	be   used.   Unlike   csx_AccessConfigurationRegister(),   the
       csx_ResetFunction(9F) function generates a series  of  event  notifica‐
       tions  to  all  clients using the PC Card, so they can re-establish the
       appropriate card state after the reset operation is complete.

RETURN VALUES
       CS_SUCCESS
				  Successful operation.

       CS_BAD_ARGS
				  Specified  arguments	are  invalid.	Client
				  specifies  an Offset that is out of range or
				  neither CONFIG_REG_READ or  CONFIG_REG_WRITE
				  is set.

       CS_UNSUPPORTED_MODE
				  Client  has not called csx_RequestConfigura‐
				  tion(9F) before calling this function.

       CS_BAD_HANDLE
				  Client handle is invalid.

       CS_NO_CARD
				  No PC card in socket.

       CS_UNSUPPORTED_FUNCTION
				  No PCMCIA hardware installed.

CONTEXT
       This function may be called from user or kernel context.

SEE ALSO
       csx_ParseTuple(9F),    csx_RegisterClient(9F),	 csx_RequestConfigura‐
       tion(9F), csx_ResetFunction(9F)

       PCCard 95 Standard, PCMCIA/JEIDA

				 Jul 19, 19CSX_ACCESSCONFIGURATIONREGISTER(9F)
[top]

List of man pages available for SmartOS

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net