SVR5

_unload(D2mdi)

_unload -- prepare to unload an MDI driver

Syntax

See the _unload(D2) manual page for syntax, context, and general usage information about this entry point routine.

Usage

All MDI drivers must have an _unload( ) entry point routine, even for DDI 7 drivers. This routine must clear out all asynchronous callbacks and free all resources that are allocated in the _load(D2mdi) entry point routine. This means you must do the following:

Issue the kmem_free(D3) or physreq_free(D3) function to free any kernel memory allocated in the _load( ) routine.
Issue the physmap_free(D3) function to free all virtual address mappings for physical addresses allocated in the _load( ) routine.
Disable interrupts on the adapter with the cm_intr_detach(D3) function.
Use the untimeout(D3) function to cancel any calls to itimeout(D3).
Use the unbufcall(D3str) function to cancel any calls to bufcall(D3str).

The _unload( ) routine will not be called when the driver is in the open state. Therefore, the _unload( ) routine does not have to deallocate resources that were freed by the close( ) routine.

NOTE: Do not assume that all previous resource allocations were successful. It is important to check that resources were actually allocated before attempting to free them.

Version applicability

mdi: 2, 2.1 running with ddi: 7, 7mp, 8, 8mp.

References

_unload(D2), _unload(D2str)