xref: /titanic_50/usr/src/man/man9f/csx_MapLogSocket.9f (revision e65fcc69bb33b3f4525b0c2c9732ece17c90b196)
te
Copyright (c) 1996, Sun Microsystems, Inc. All Rights Reserved
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
csx_MapLogSocket 9F "19 Jul 1996" "SunOS 5.11" "Kernel Functions for Drivers"
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