init(D2pccard)

init -- initialize a loadable kernel module

Syntax

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

Usage

init( ) is called as an entry point routine for static (non-loadable) DDI 7 drivers and all SCO OpenServer 5 ODDI drivers. For DDI 8 drivers and loadable DDI 7 drivers, init( ) is not called as an entry point routine. Instead, device initialization is coded in the _load(D2pccard) entry point for DDI 7 loadable drivers and in the CFG_ADD subfunction to the config(D2pccard) subfunction for DDI 8 drivers. For maximum flexibility, code the PC Card device initialization functionality into a separate subroutine that can be called from the appropriate entry point to initialize the device.

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.
Call the RequestConfiguration(D3pccard) service to configure the card and socket according to memory allocated and system resources granted.
Call the appropriate function to attach/register interrupts:
- For DDI 7 drivers, call the cm_intr_attach(D3) function.
- For ODDI 5 drivers, populate the driver_info(D4oddi) structure and call the idistributed(D3oddi) function.

Version applicability

pccard: 2 with ddi: 7, 7.1

Differences between versions

The init( ) entry point routine is not used for static (non-loadable) DDI 7 drivers. Code the driver initialization and device configuration functionality into the init(D2pccard) routine for static drivers. ( ) DDI 8 drivers only implement driver initialization functionality in the _load(D2pccard) entry point routine. Device configuration is implemented in the CFG_ADD subfunction to the config(D2pccard) entry point routine.

References

init(D2), init(D2mdi), init(D2oddi), init(D2sdi)