SVR5 and SCO OpenServer 5
DeregisterClient(D3pccard)
DeregisterClient --
deregister client
Synopsis
#include <sys/types.h>
#include <sys/lcs.h>
#include <sys/lss.h>
int CardServices (DeregisterClient, ClientHandle_t *pClient,
int n1, int n2,
int *n3, rm_key_t key);
Description
DeregisterClient( )
removes the client
from the list of registered clients maintained by
CardServices( ).
Arguments
pClient-
Pointer to a
ClientHandle(D4pccard)
structure.
n1-
NULL
n2-
0
n3-
NULL
key-
Resource manager
key.
Return values
BAD_ARG_LENGTH-
n2 is not equal to zero (0).
BAD_HANDLE-
Client handle is invalid.
BUSY-
MTD client background task in progress.
IN_USE-
Resources have not been released by this client.
SUCCESS-
Client deregistered successfully.
Usage
DeregisterClient( )
is called as part of the client removal code.
CardServices( )
does not permit the Client
to deregister itself unless the Client has already returned
the system resources it had been using.
When a Memory Technology Driver
(MTD) Client
uses the
DeregisterClient( )
service,
CardServices( )
blocks its access to memory,
negating the Client's previous
RegisterMTD(D3pccard)
call.
CardServices( )
installs a default MTD for the memory region
and then, if any other MTD Clients remain registered,
CardServices( )
informs them that the abandoned memory region needs access support.
CardServices( )
notifies any remaining MTD Client
of this through a CARD_INSERTION event notification.
CardServices( )
continues to issue callbacks until
DeregisterClient( )
returns SUCCESS.
Context and synchronization
Interrupt
context
Hardware applicability
All
Version applicability
pccard:
1, 2, 3
References
ClientHandle(D4pccard),
RegisterClient(D3pccard)
config(D2pccard),
halt(D2pccard),
_unload(D2pccard)
19 June 2005
© 2005 The SCO Group, Inc. All rights reserved.
OpenServer 6 and UnixWare (SVR5) HDK - June 2005