Lines Matching defs:hcf_action
517 *.MODULE int hcf_action( IFBP ifbp, hcf_16 action )
541 * Except for hcf_action with HCF_ACT_INT_FORCE_ON or HCF_ACT_INT_OFF as parameter or hcf_connect with an I/O
542 * address (i.e. not HCF_DISCONNECT), all hcf-function calls MUST be preceeded by a call of hcf_action with
544 * Note that hcf_connect defaults to NIC interrupt disabled mode, i.e. as if hcf_action( HCF_ACT_INT_OFF )
548 * hcf_action supports the following mode changing action-code pairs that are antonyms
552 * Additionally hcf_action can start the following actions in the NIC:
580 * An MSF based on a interrupt strategy must call hcf_action with INT_ON in its initialization logic.
701 hcf_action( IFBP ifbp, hcf_16 action )
795 // rc = hcf_action( ifbp, HCF_ACT_INT_OFF ); /*bogus, IFB_IntOffCnt == 0xFFFF, so if you carefully look
836 } // hcf_action
918 * does not enable the Interrupt Generation mechanism. This is done by hcf_action.
1058 * Note: hcf_connect defaults to NIC interrupt disabled mode, i.e. as if hcf_action( HCF_ACT_INT_OFF )
1071 * This implies that all settings which are done via hcf_action and hcf_put_info (e.g. CFG_MB_ASSERT, CFG_REG_MB,
2041 (void)hcf_action( ifbp, HCF_ACT_TALLIES );
2479 (void)hcf_action( ifbp, HCF_ACT_RX_ACK ); //only 1 shot to get the data, so free the resources in the NIC
2841 * messages, irrespective whether a hcf_rcv_msg or hcf_action(HCF_ACT_RX) is performed in between.
2879 * hcf_action to disable the card interrupts and, after all work is completed, with a call to hcf_action to
2921 * - hcf_action with HCF_ACT_RX is called or
2923 * It can be reasoned that hcf_action( INT_ON ) should not be given before the MSF has completely processed
2945 * Note that as side-effect of the hcf_action call, the remainder of Rx related info is re-initialized as
3019 * This acknowledgement can not be done via hcf_action( HCF_ACT_RX_ACK ) because this also clears
3068 (void)hcf_action( ifbp, HCF_ACT_RX_ACK ); /* 2*/