SVR5 and SCO OpenServer 5

SetEventMask(D3pccard)

SetEventMask -- change event mask for the client

Synopsis

   #include <sys/types.h>
   #include <sys/lcs.h>
   #include <sys/lss.h>
   
   int CardServices (SetEventMask, ClientHandle_t *pClientHandle,
                     int n1, int SetEventMaskLen,
                     GetSetEventMask_t *pSetEventMask,
   	   	  rm_key_t key);

Description

SetEventMask( ) changes the event mask for the Client that had previously been returned by the GetEventMask(D3pccard) service. The event mask tells CardServices which events the Client is interested in.

Arguments

pClientHandle: Pointer to a ClientHandle(D4pccard) structure.
n1: NULL
SetEventMaskLen: Length of the GetSetEventMask(D4pccard) structure. Must be set to 6.
pSetEventMask: Pointer to the GetSetEventMask(D4pccard) structure.
key: Resource manager key.

Return values

BAD_ARG_LENGTH: SetEventMaskLen not equal to 6.
BAD_HANDLE: *pClientHandle does not point to correct client.
BAD_SOCKET: Socket invalid or had not been previously requested by RequestSocketMask(D3pccard).
NO_CARD: No card inserted.
SUCCESS: Standing event notification request was changed successfully.

Usage

The type of event mask to be changed in indicated in the C struct GetSetEventMask_t : usAttributes. usAttributes is bitmapped. If bit 0 is reset to 0, the change is for the global event mask; if bit 0 is set to 1, the change is for the specified socket only.

The notification for particular events is given in the bit mapped usEventMask member of the GetSetEventMask(D4pccard). See the Personal Computer Memory Card International Association (PCMCIA) CardServices Specification bit table for EventMask in Section 5, p. 154. The EventMask table corresponds to the struct member usEventMask in this implementation.

The card function is passed in the C struct GetSetEventMask_t: usSocket. usSocket is two bytes long. The more significant byte indicates the function. The function of single function cards is mapped to zero. The functions of multi-function cards are enumerated from zero on up to the number of functions available less one, in typical C language fashion. As one might suspect, the low byte in usSocket indicates logical socket.

Context and synchronization

Blockable, initialization, or user context

Hardware applicability

All

Version applicability

pccard: 1, 2, 3

References

ClientHandle(D4pccard), GetSetEventMask(D4pccard)