PC Card Driver Structures
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/28/2008
The following table shows the PC Card driver structures.
| Programming element | Description |
|---|---|
This structure contains PC Card configuration information. |
|
This structure contains tuple information passed to the CardGetTupleData function. |
|
This structure contains event mask configurations passed to the CardGetEventMask and CardSetEventMask functions. |
|
Thisstructure contains additional information for particular callback events and is passed as the third member to the client's callback function. |
|
This structure contains driver characteristics passed to the CardRegisterClient function.All members are input-only. |
|
This structure returns data. It is used by the CardGetStatus function. |
|
This structure contains tuple information passed to the CardGetFirstTuple, CardGetNextTuple, and CardGetTupleData functions. |
|
This structure contains window address information. |
|
This data type maps a window within system memory. It is used by the CardRequestWindow function. The window can be used to access the PC Card memory or I/O space. The CardRequestWindow function returns a 32-bit handle to the mapped window with this data type. |
|
This structure contains desired memory or I/O window characteristics passed to the CardRequestWindow function. |