_load(D2pccard)

_load -- initialize a loadable kernel module

Syntax

See _load(D2) for syntax and general usage information about this entry point routine.

Usage

The _load( ) entry point performs driver initialization for all loadable drivers (see ``Dynamically-loadable kernel modules (DLKM)'' in HDK Technical Reference) and, for DDI 7 drivers, also performs device configuration.

The initialization code for a PC Card client-enabled driver must do the following:

Call the GetCardServicesInfo(D3pccard) service to verify that the CardServices( ) routine is present. If CardServices( ) is not present, return an error code to the entry point routine that called it.
Populate the ClientHandle(D4pccard), CallbackEntry(D4pccard), and RegisterClient(D4pccard) structures with information about this driver and device.
Call the RegisterClient( ) service to notify the CardServices( ) routine that it is present, define the events in which it has interest, and to attach the client_callback(D2pccard) interrupt handling routine.
Call the RequestSocketMask(D3pccard) function to be notified of status changes in any particular socket.
If there are certain event notifications from CardServices( ) that should be screened out, call the SetEventMask(D3pccard) to identify these events. Use the GetEventMask(D3pccard) function to see which events are currently screened out.

The configuration code for a PC Card client-enabled driver must do the following:

Call the GetConfigurationInfo(D3pccard) service to get information about the socket and the card such as manufacturer, function code, and IRQ attributes.
If no card is present or the card is otherwise inaccessible, return an error code to CardServices( ).
Call the GetFirstTuple(D3pccard) and GetTupleData(D3pccard) services to examine the tuples in the CISinfo(D4pccard) CIS (Card Information Structure) for get more specific data.
Call the RequestWindow(D3pccard) service to request a portion of system memory. ( ) Call the MapMemPage(D3pccard) service to associate a memory area on the card with the system memory obtained with RequestWindow( ).
Call the RequestDMA(D3pccard), RequestIO(D3pccard), and/or RequestIRQ(D3pccard) services as needed.
For DDI 7 drivers, call the cm_intr_attach(D3) function to attach interrupts for the cards controlled by this driver. For DDI 8 drivers, cm_intr_attach( ) is called in the CFG_ADD subfunction to the config(D2pccard) entry point routine.
Call the RequestConfiguration(D3pccard) service to configure the card and socket according to memory allocated and system resources granted.

Version applicability

pccard: 2, 3

Differences between versions

The _load( ) entry point routine is not supported on SCO OpenServer 5 systems. All driver initialization and device configuration is implemented in the init(D2pccard) entry point routine.

References

_load(D2), _load(D2mdi), _load(D2sdi),